UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[roughestboy]

Hallo, seit kurzem habe ich obigen Fehler.
Log, wenn ich die Instanz stoppe und starte:

Spoiler

zigbee.0
2023-02-26 12:05:46.625 error Error herdsman start

zigbee.0
2023-02-26 12:05:46.623 error Failed to start Zigbee

zigbee.0
2023-02-26 12:05:46.622 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"

zigbee.0
2023-02-26 12:05:46.328 info Installed Version: iobroker.zigbee@1.7.6

zigbee.0
2023-02-26 12:05:46.275 info Starting Zigbee npm ...

zigbee.0
2023-02-26 12:05:46.273 info Try to reconnect. 1 attempts left

zigbee.0
2023-02-26 12:05:36.268 error Error herdsman start

zigbee.0
2023-02-26 12:05:36.267 error Failed to start Zigbee

zigbee.0
2023-02-26 12:05:36.266 error Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"

zigbee.0
2023-02-26 12:05:36.121 error Re-commissioning your network will require re-pairing of all devices!

zigbee.0
2023-02-26 12:05:36.121 error If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.

zigbee.0
2023-02-26 12:05:36.120 error Please update configuration to prevent further issues.

zigbee.0
2023-02-26 12:05:36.119 error - Channel List: configured=15, adapter=15

zigbee.0
2023-02-26 12:05:36.118 error - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d

zigbee.0
2023-02-26 12:05:36.118 error - Extended PAN ID: configured=00124b00194af3c5, adapter=00124b00194af3c5

zigbee.0
2023-02-26 12:05:36.117 error - PAN ID: configured=6754, adapter=6754

zigbee.0
2023-02-26 12:05:36.117 error Configuration is not consistent with adapter state/backup!

zigbee.0
2023-02-26 12:05:36.013 info Installed Version: iobroker.zigbee@1.7.6

zigbee.0
2023-02-26 12:05:35.472 info Starting Zigbee npm ...

zigbee.0
2023-02-26 12:05:35.469 info delete old Backup files. keep only last 10

zigbee.0
2023-02-26 12:05:35.350 info starting. Version 1.7.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.18.0, js-controller: 4.0.23

Anhand dem, was vor der obigen Meldung los ist, kann ich keinen Fehler erkennen, zumindest, was die 4 Einstellungen nach
error Configuration is not consistent with adapter state/backup!
betrifft. Ich würde jetzt sowas machen wollen, das sagt mir aber nichts:
"Please update configuration to prevent further issues."
und natürlich ein Recommissioning vermeiden wollen.
Was kann man da tun ?

[crunchip]

@roughestboy sagte in Zigbee: Resource temporarily unavailable Cannot lock port:

please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.

please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.

[roughestboy]

@crunchip und das bedeutet dann
Re-commissioning your network will require re-pairing of all devices!
ich muss alle Geräte neu pairen ?

[roughestboy]

@crunchip sagte in Zigbee: Resource temporarily unavailable Cannot lock port:

/opt/iobroker/iobroker-data/zigbee_0

Nun, habe ich mal nvbackup.json umbenannt.

Neues Log ab start der Instanz:

Spoiler

zigbee.0
2023-02-26 12:40:55.549 warn Terminated (UNCAUGHT_EXCEPTION): Without reason

zigbee.0
2023-02-26 12:40:55.546 info terminating

zigbee.0
2023-02-26 12:40:55.069 error Cannot read properties of undefined (reading 'mapped')

zigbee.0
2023-02-26 12:40:55.068 error TypeError: Cannot read properties of undefined (reading 'mapped') at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:501:36) at runNextTicks (node:internal/process/task_queues:61:5) at processImmediate (node:internal/timers:437:9)

zigbee.0
2023-02-26 12:40:55.066 error unhandled promise rejection: Cannot read properties of undefined (reading 'mapped')

zigbee.0
2023-02-26 12:40:55.065 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

zigbee.0
2023-02-26 12:40:55.047 info Zigbee: disabling joining new devices.

zigbee.0
2023-02-26 12:40:55.045 info cleaned everything up...

zigbee.0
2023-02-26 12:40:55.029 error Cannot read properties of undefined (reading 'mapped')

zigbee.0
2023-02-26 12:40:55.027 error TypeError: Cannot read properties of undefined (reading 'mapped') at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:501:36)

zigbee.0
2023-02-26 12:40:55.026 error unhandled promise rejection: Cannot read properties of undefined (reading 'mapped')

zigbee.0
2023-02-26 12:40:55.025 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

zigbee.0
2023-02-26 12:40:53.224 info debug devices set to []

zigbee.0
2023-02-26 12:40:53.148 info Zigbee started

zigbee.0
2023-02-26 12:40:53.147 info Currently no devices.

zigbee.0
2023-02-26 12:40:53.140 info --> transmitPower : high

zigbee.0
2023-02-26 12:40:53.121 info Unable to disable LED, unsupported function.

zigbee.0
2023-02-26 12:40:53.120 info Disable LED

zigbee.0
2023-02-26 12:40:53.115 info Coordinator firmware version: {"type":"zStack30x","meta":{"transportrev":2,"product":2,"majorrel":2,"minorrel":7,"maintrel":2,"revision":20200327}}

zigbee.0
2023-02-26 12:40:52.917 info Installed Version: iobroker.zigbee@1.7.6

zigbee.0
2023-02-26 12:40:52.279 info Starting Zigbee npm ...

zigbee.0
2023-02-26 12:40:52.276 info delete old Backup files. keep only last 10

zigbee.0
2023-02-26 12:40:52.167 info starting. Version 1.7.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.18.0, js-controller: 4.0.23

Nun gehts um "Unhandled promise rejection". Was kann ich jetzt tun ?

[Thomas Braun]

@roughestboy Zunächst würde ich mal deine Software auf Stand bringen. Betriebssystem, NodeJS, Adapter usw.

Welche Hardware zigbeet denn da herum? So'n oller CC2531?

Und dann bitte Auszüge aus dem LogFile in CodeTags setzen statt Spoiler.

[roughestboy]

@thomas-braun
Zigbee Adapter ist ein CC2538 von Arteck. Update folgt.

[Thomas Braun]

@roughestboy sagte in Zigbee: Resource temporarily unavailable Cannot lock port:

CC2538

Ich dachte da sei vielleicht der Firmware-Stack falsch. Aber 3.0.x passt da.

[roughestboy]

@thomas-braun

System ist up2date, js-controller 4.0.24. npm 8.19.2 und node.js 16.18.0 nahezu.

Log mit Start der Zigbee Instanz sieht nun so aus:

zigbee.0
2023-02-26 16:03:00.572	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

zigbee.0
2023-02-26 16:03:00.570	info	terminating

zigbee.0
2023-02-26 16:03:00.071	info	Zigbee: disabling joining new devices.

zigbee.0
2023-02-26 16:03:00.067	info	cleaned everything up...

zigbee.0
2023-02-26 16:03:00.040	error	Cannot read properties of undefined (reading 'mapped')

zigbee.0
2023-02-26 16:03:00.037	error	TypeError: Cannot read properties of undefined (reading 'mapped') at Zigbee.publishFromState (/opt/iobroker/node_modules/iobroker.zigbee/main.js:571:36)

zigbee.0
2023-02-26 16:03:00.035	error	unhandled promise rejection: Cannot read properties of undefined (reading 'mapped')

zigbee.0
2023-02-26 16:03:00.031	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

zigbee.0
2023-02-26 16:02:58.359	info	debug devices set to []

zigbee.0
2023-02-26 16:02:58.280	info	Zigbee started

zigbee.0
2023-02-26 16:02:58.278	info	Currently no devices.

zigbee.0
2023-02-26 16:02:58.263	info	--> transmitPower : high

zigbee.0
2023-02-26 16:02:58.245	info	Unable to disable LED, unsupported function.

zigbee.0
2023-02-26 16:02:58.244	info	Disable LED

zigbee.0
2023-02-26 16:02:58.237	info	Coordinator firmware version: {"type":"zStack30x","meta":{"transportrev":2,"product":2,"majorrel":2,"minorrel":7,"maintrel":2,"revision":20200327}}

zigbee.0
2023-02-26 16:02:57.965	info	Installed Version: iobroker.zigbee@1.8.10

zigbee.0
2023-02-26 16:02:57.340	info	Starting Zigbee npm ...

zigbee.0
2023-02-26 16:02:57.337	info	delete old Backup files. keep only last 10

zigbee.0
2023-02-26 16:02:57.212	info	starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.18.0, js-controller: 4.0.24

Kann es ein Hardware Prob sein ? Verkabelung habe ich neu gesteckt, allerdings siehen
lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 003: ID 0451:16c8 Texas Instruments, Inc. CC2538 USB CDC
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

und ls -l /dev/serial/by-id

lrwxrwxrwx 1 root root 13 26. Feb 15:44 usb-EnOcean_GmbH_EnOcean_USB_300_DB_FT3FUSTH-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 26. Feb 15:44 usb-Texas_Instruments_CC2538_USB_CDC-if00 -> ../../ttyACM0

nicht verkehrt aus.

[Thomas Braun]

@roughestboy sagte in Zigbee: Resource temporarily unavailable Cannot lock port:

nahezu

Dann mach es vollständig.

[roughestboy]

@thomas-braun
Ich habe jetzt ein völlig aktuelles System. Bzgl. dem Zigbee Prob bringt das nichts.
Testweise einen anderen USB Anschluss verwendet und eine 2. Instanz erzeugt, Instanz läuft trotzdem auf rot.

[crunchip]

@roughestboy wenn du die nvbackup.json wieder einfügst?

[Thomas Braun]

@roughestboy

Dann erzähl uns mal mehr zu deinem System.

Z.B. per Ausgabe von

iob diag

[roughestboy]

@crunchip
Ja, die alte nvbackup.json is ja auch noch da. Wenn ich die wieder einsetze, sehen die Fehlermeldungen anders aus, Instanz bleibt aber auf gelb:

zigbee.0
2023-02-26 18:00:06.605	error	Error herdsman start

zigbee.0
2023-02-26 18:00:06.604	error	Failed to start Zigbee

zigbee.0
2023-02-26 18:00:06.598	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"


zigbee.0
2023-02-26 18:00:06.199	info	Installed Version: iobroker.zigbee@1.8.10

zigbee.0
2023-02-26 18:00:06.131	info	Starting Zigbee npm ...

zigbee.0
2023-02-26 18:00:06.128	info	Try to reconnect. 1 attempts left

zigbee.0
2023-02-26 17:59:56.121	error	Error herdsman start

zigbee.0
2023-02-26 17:59:56.120	error	Failed to start Zigbee

zigbee.0
2023-02-26 17:59:56.117	error	Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'payload')"

zigbee.0
2023-02-26 17:59:46.937	info	Installed Version: iobroker.zigbee@1.8.10

zigbee.0
2023-02-26 17:59:46.246	info	Starting Zigbee npm ...

zigbee.0
2023-02-26 17:59:46.242	info	delete old Backup files. keep only last 10

zigbee.0
2023-02-26 17:59:46.102	info	starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.1, js-controller: 4.0.24

[roughestboy]

@thomas-braun

======================= SUMMARY =======================
                     v.2023-01-02


Operatingsystem:        Debian GNU/Linux 11 (bullseye)
Installation:           Native
Timezone:               Europe/Berlin
User-ID:                1000
X-Server:               false
Boot Target:            multi-user.target

Pending OS-Updates:     54

Nodejs-Installation:    /usr/bin/nodejs         v16.19.1
                        /usr/bin/node           v16.19.1
                        /usr/bin/npm            8.19.3
                        /usr/bin/npx            8.19.3

ioBroker Core:          js-controller           4.0.24
                        admin                   6.3.6

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: redis

Status admin:
+ system.adapter.admin.0                  : admin                 : pi4iobroker                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin

Pending iob updates:    0

Active repo(s): beta

Objects:                4090
States:                 2820

Size of iob-Database:

25M     /opt/iobroker/iobroker-data/objects.jsonl
552K    /opt/iobroker/iobroker-data/states.jsonl


=================== END OF SUMMARY ====================

[Thomas Braun]

@roughestboy

Pending OS-Updates: 54

Updaten...

[crunchip]

@roughestboy und wenn du den Stick mal kurz absteckst?

[roughestboy]

@crunchip ändert nichts.

[roughestboy]

@thomas-braun

Habe jetzt Pending OS-Updates auf Null. Zwischendurch Kabel zum Stick getauscht, den Stick gegen einen identischen gewechselt, und ein Backitup vom 2.2. eingespielt, da war das Problem noch nicht. Auch noch eine neue, 2te Instanz angelegt. Es bleibt immer bei einem 'zigbee-herdsman Problem,' "Cannot read properties of undefined (reading 'payload')" und "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'". Letztes log:

zigbee.0
	2023-03-04 11:48:47.327	error	Error herdsman start
zigbee.0
	2023-03-04 11:48:47.325	error	Failed to start Zigbee
zigbee.0
	2023-03-04 11:48:47.324	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
zigbee.0
	2023-03-04 11:48:47.127	info	Installed Version: iobroker.zigbee@1.8.10
zigbee.0
	2023-03-04 11:48:47.103	info	Starting Zigbee npm ...
zigbee.0
	2023-03-04 11:48:47.102	info	Try to reconnect. 1 attempts left
zigbee.0
	2023-03-04 11:48:37.083	error	Error herdsman start
zigbee.0
	2023-03-04 11:48:37.083	error	Failed to start Zigbee
zigbee.0
	2023-03-04 11:48:37.081	error	Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'payload')"
zigbee.0
	2023-03-04 11:48:28.346	info	Installed Version: iobroker.zigbee@1.8.10
zigbee.0
	2023-03-04 11:48:27.652	info	Starting Zigbee npm ...
zigbee.0
	2023-03-04 11:48:27.483	info	starting. Version 1.8.10 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.19.1, js-controller: 4.0.24

[roughestboy]

Frage: gibts in iobroker irgendetwas oder einen anderen Adapter, der sich den Zigbee Stick schnappt, in etwa sowas wie hier:
502 - Bad Gateway =>TypeError: Cannot read property 'payload' of undefined

[roughestboy]

So, um das hier noch abzuschließen. Habe mich wegen eines anderen 'Großprojekts' lange nicht kümmern können und erstmal ohne Zigbee leben müssen.
Nun ist raus, es war ein 'schlechtes' udev-Paket. Siehe auch
zigbee-conbee2-funktioniert-nach-update-nicht-mehr-udev
Für mich war es dann die Möglichkeit 2.