[gelöst] Sonoff Zigbee 3.0 Dongle "Failure to connect"

[aupex]

Hallo,
Ich wollte meinen cc2531 nachdem er immer öfter ausgefallen ist durch einen Sonoff Dongle ersetzen.
Erst habe ich es per Backup und neu installieren probiert, damit ich nicht neu anlernen muss. -> hat wie befürchtet nicht funktioniert. Danach habe ich versucht den Zigbeeadapter komplett neu aufzusetzten, allerdings Connectet der Iobroker nicht zum Dongle. Meine Einstellungen und ein Log hänge ich mal an. Wahrscheinlich übersehe ich einfach irgendeine Kleinigkeit, oder stehe komplett auf der Leitung.

Gruss

Log:

2024-07-10 17:08:48.647  - warn: zigbee.0 (2447) Got terminate signal. Checking desired PID: 0 vs own PID 2447
2024-07-10 17:08:48.665  - info: host.iobroker instance system.adapter.zigbee.0 started with pid 2472
2024-07-10 17:08:48.655  - info: zigbee.0 (2447) cleaned everything up...
2024-07-10 17:08:48.713  - info: zigbee.0 (2447) Zigbee: disabling joining new devices.
2024-07-10 17:08:48.985  - warn: zigbee.0 (2447) Failed to stop zigbee during startup
2024-07-10 17:08:48.986  - info: zigbee.0 (2447) terminating
2024-07-10 17:08:48.987  - info: zigbee.0 (2447) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-10 17:08:49.033  - warn: zigbee.0 (2447) Got terminate signal. Checking desired PID: 2472 vs own PID 2447
2024-07-10 17:08:49.081  - info: zigbee.0 (2447) debug devices set to []
2024-07-10 17:08:49.156  - info: zigbee.0 (2447) terminating
2024-07-10 17:08:49.642  - info: host.iobroker instance system.adapter.zigbee.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2024-07-10 17:08:49.643  - info: host.iobroker Do not restart adapter system.adapter.zigbee.0 because desired by instance
2024-07-10 17:08:48.647  - warn: zigbee.0 (2447) Got terminate signal. Checking desired PID: 0 vs own PID 2447
2024-07-10 17:08:48.665  - info: host.iobroker instance system.adapter.zigbee.0 started with pid 2472
2024-07-10 17:08:48.655  - info: zigbee.0 (2447) cleaned everything up...
2024-07-10 17:08:48.713  - info: zigbee.0 (2447) Zigbee: disabling joining new devices.
2024-07-10 17:08:48.985  - warn: zigbee.0 (2447) Failed to stop zigbee during startup
2024-07-10 17:08:48.986  - info: zigbee.0 (2447) terminating
2024-07-10 17:08:48.987  - info: zigbee.0 (2447) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-10 17:08:49.033  - warn: zigbee.0 (2447) Got terminate signal. Checking desired PID: 2472 vs own PID 2447
2024-07-10 17:08:49.081  - info: zigbee.0 (2447) debug devices set to []
2024-07-10 17:08:49.156  - info: zigbee.0 (2447) terminating
2024-07-10 17:08:49.642  - info: host.iobroker instance system.adapter.zigbee.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2024-07-10 17:08:49.643  - info: host.iobroker Do not restart adapter system.adapter.zigbee.0 because desired by instance
2024-07-10 17:08:54.736  - info: zigbee.0 (2472) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.4, js-controller: 5.0.19
2024-07-10 17:08:54.856  - info: zigbee.0 (2472) delete old Backup files. keep only last 10
2024-07-10 17:08:54.859  - info: zigbee.0 (2472) Starting Zigbee  npm ...
2024-07-10 17:08:55.285  - info: zigbee.0 (2472) Installed Version: iobroker.zigbee@1.10.3
2024-07-10 17:08:54.736  - info: zigbee.0 (2472) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.4, js-controller: 5.0.19
2024-07-10 17:08:54.856  - info: zigbee.0 (2472) delete old Backup files. keep only last 10
2024-07-10 17:08:54.859  - info: zigbee.0 (2472) Starting Zigbee  npm ...
2024-07-10 17:08:55.285  - info: zigbee.0 (2472) Installed Version: iobroker.zigbee@1.10.3
2024-07-10 17:08:59.388  - error: zigbee.0 (2472) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-07-10 17:08:59.389  - error: zigbee.0 (2472) Failed to start Zigbee
2024-07-10 17:08:59.390  - error: zigbee.0 (2472) Error herdsman start
2024-07-10 17:08:59.388  - error: zigbee.0 (2472) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-07-10 17:08:59.389  - error: zigbee.0 (2472) Failed to start Zigbee
2024-07-10 17:08:59.390  - error: zigbee.0 (2472) Error herdsman start
2024-07-10 17:09:09.396  - info: zigbee.0 (2472) Try to reconnect. 1 attempts left
2024-07-10 17:09:09.398  - info: zigbee.0 (2472) Starting Zigbee  npm ...
2024-07-10 17:09:09.414  - info: zigbee.0 (2472) Installed Version: iobroker.zigbee@1.10.3
2024-07-10 17:09:09.396  - info: zigbee.0 (2472) Try to reconnect. 1 attempts left
2024-07-10 17:09:09.398  - info: zigbee.0 (2472) Starting Zigbee  npm ...
2024-07-10 17:09:09.414  - info: zigbee.0 (2472) Installed Version: iobroker.zigbee@1.10.3
2024-07-10 17:09:39.785  - error: zigbee.0 (2472) Starting zigbee-herdsman problem : "Failure to connect"
2024-07-10 17:09:39.788  - error: zigbee.0 (2472) Failed to start Zigbee
2024-07-10 17:09:39.788  - error: zigbee.0 (2472) Error herdsman start
2024-07-10 17:09:39.828  - info: admin.0 (846) <== Disconnect system.user.admin from ::ffff:192.168.2.106
2024-07-10 17:09:39.785  - error: zigbee.0 (2472) Starting zigbee-herdsman problem : "Failure to connect"
2024-07-10 17:09:39.788  - error: zigbee.0 (2472) Failed to start Zigbee
2024-07-10 17:09:39.788  - error: zigbee.0 (2472) Error herdsman start

Konfiguration:

Edit:
Die "Standartwerte" bei Pid sind dessen geschuldet, dass ich versucht habe den Stick ohne neu anzulernen müssen gewechselt habe.

[Asgothian]

@aupex sagte in Sonoff Zigbee 3.0 Dongle "Failure to connect":

Edit:
Die "Standartwerte" bei Pid sind dessen geschuldet, dass ich versucht habe den Stick ohne neu anzulernen müssen gewechselt habe.

Bitte folgendem Ablauf folgen:

• zigbee Adapter starten so das du an die Konfiguration heran kommst
• die ExtPanID anpassen. DDDDDDDDDDDDDDDD ist keine gute Idee, da dann die ExtPanID Hardwarespezifisch ist, und in der Zukunft ein Tausch des Koordinators ggf. schwierig wird.
• Zigbee Adapter anhalten
• die Dateien unter /opt/iobroker/iobroker-data/zigbee_0 löschen
• Zigbee-Adapter starten

A.

[arteck]

@aupex sagte in Sonoff Zigbee 3.0 Dongle "Failure to connect":

Hallo,
Ich wollte meinen cc2531 nachdem er immer öfter ausgefallen ist durch einen Sonoff Dongle ersetzen.

du hättest einfach NUR der alten raus den neuen rein.. 5 min Warten fertig...

[Asgothian]

@arteck sagte in Sonoff Zigbee 3.0 Dongle "Failure to connect":

@aupex sagte in Sonoff Zigbee 3.0 Dongle "Failure to connect":

Hallo,

Ich wollte meinen cc2531 nachdem er immer öfter ausgefallen ist durch einen Sonoff Dongle ersetzen.

du hättest einfach NUR der alten raus den neuen rein.. 5 min Warten fertig...

Wenn er den richtigen sonoff dongle erwischt hat. (-p Variante, nicht -e Variante). Das log oben deutet darauf hin das er einen -e hat. (EZSP Firmware und dann die Meldung “configuration mismatch”)

A.

[aupex]

@asgothian
Habe es so gemacht, wie du geschrieben hast. Funktioniert leider nicht. Siehe log:

2024-07-11 14:55:04.610  - error: zigbee.0 (7238) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
2024-07-11 14:55:04.874  - info: zigbee.0 (7238) List of port: [{"path":"/dev/ttyACM0","manufacturer":"ITEAD","serialNumber":"20231214181142","pnpId":"usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20231214181142-if00","vendorId":"1a86","productId":"55d4"},{"path":"/dev/ttyAMA0"}]
2024-07-11 14:55:33.447  - info: admin.0 (846) <== Disconnect system.user.admin from ::ffff:192.168.2.106
2024-07-11 14:55:33.660  - warn: zigbee.0 (7238) Got terminate signal. Checking desired PID: 0 vs own PID 7238
2024-07-11 14:55:33.695  - info: host.iobroker instance system.adapter.zigbee.0 started with pid 7429
2024-07-11 14:55:33.664  - info: zigbee.0 (7238) cleaned everything up...
2024-07-11 14:55:33.677  - info: zigbee.0 (7238) Zigbee: disabling joining new devices.
2024-07-11 14:55:33.895  - warn: zigbee.0 (7238) Failed to stop zigbee during startup
2024-07-11 14:55:33.897  - info: zigbee.0 (7238) terminating
2024-07-11 14:55:33.900  - info: zigbee.0 (7238) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-11 14:55:33.923  - warn: zigbee.0 (7238) Got terminate signal. Checking desired PID: 7429 vs own PID 7238
2024-07-11 14:55:34.165  - info: zigbee.0 (7238) terminating
2024-07-11 14:55:34.556  - info: host.iobroker instance system.adapter.zigbee.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2024-07-11 14:55:34.556  - info: host.iobroker Do not restart adapter system.adapter.zigbee.0 because desired by instance
2024-07-11 14:55:33.447  - info: admin.0 (846) <== Disconnect system.user.admin from ::ffff:192.168.2.106
2024-07-11 14:55:33.660  - warn: zigbee.0 (7238) Got terminate signal. Checking desired PID: 0 vs own PID 7238
2024-07-11 14:55:33.695  - info: host.iobroker instance system.adapter.zigbee.0 started with pid 7429
2024-07-11 14:55:33.664  - info: zigbee.0 (7238) cleaned everything up...
2024-07-11 14:55:33.677  - info: zigbee.0 (7238) Zigbee: disabling joining new devices.
2024-07-11 14:55:33.895  - warn: zigbee.0 (7238) Failed to stop zigbee during startup
2024-07-11 14:55:33.897  - info: zigbee.0 (7238) terminating
2024-07-11 14:55:33.900  - info: zigbee.0 (7238) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-11 14:55:33.923  - warn: zigbee.0 (7238) Got terminate signal. Checking desired PID: 7429 vs own PID 7238
2024-07-11 14:55:34.165  - info: zigbee.0 (7238) terminating
2024-07-11 14:55:34.556  - info: host.iobroker instance system.adapter.zigbee.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2024-07-11 14:55:34.556  - info: host.iobroker Do not restart adapter system.adapter.zigbee.0 because desired by instance
2024-07-11 14:55:39.834  - info: zigbee.0 (7429) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.4, js-controller: 5.0.19
2024-07-11 14:55:39.953  - info: zigbee.0 (7429) Starting Zigbee  npm ...
2024-07-11 14:55:40.439  - info: zigbee.0 (7429) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 14:55:39.834  - info: zigbee.0 (7429) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.4, js-controller: 5.0.19
2024-07-11 14:55:39.953  - info: zigbee.0 (7429) Starting Zigbee  npm ...
2024-07-11 14:55:40.439  - info: zigbee.0 (7429) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 14:55:44.622  - error: zigbee.0 (7429) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-07-11 14:55:44.624  - error: zigbee.0 (7429) Failed to start Zigbee
2024-07-11 14:55:44.624  - error: zigbee.0 (7429) Error herdsman start
2024-07-11 14:55:44.622  - error: zigbee.0 (7429) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-07-11 14:55:44.624  - error: zigbee.0 (7429) Failed to start Zigbee
2024-07-11 14:55:44.624  - error: zigbee.0 (7429) Error herdsman start
2024-07-11 14:55:54.630  - info: zigbee.0 (7429) Try to reconnect. 1 attempts left
2024-07-11 14:55:54.631  - info: zigbee.0 (7429) Starting Zigbee  npm ...
2024-07-11 14:55:54.645  - info: zigbee.0 (7429) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 14:55:54.630  - info: zigbee.0 (7429) Try to reconnect. 1 attempts left
2024-07-11 14:55:54.631  - info: zigbee.0 (7429) Starting Zigbee  npm ...
2024-07-11 14:55:54.645  - info: zigbee.0 (7429) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 14:56:25.061  - error: zigbee.0 (7429) Starting zigbee-herdsman problem : "Failure to connect"
2024-07-11 14:56:25.063  - error: zigbee.0 (7429) Failed to start Zigbee
2024-07-11 14:56:25.064  - error: zigbee.0 (7429) Error herdsman start
2024-07-11 14:56:25.061  - error: zigbee.0 (7429) Starting zigbee-herdsman problem : "Failure to connect"
2024-07-11 14:56:25.063  - error: zigbee.0 (7429) Failed to start Zigbee
2024-07-11 14:56:25.064  - error: zigbee.0 (7429) Error herdsman start

[Asgothian]

@aupex sagte in Sonoff Zigbee 3.0 Dongle "Failure to connect":

@asgothian
Habe es so gemacht, wie du geschrieben hast. Funktioniert leider nicht. Siehe log:

2024-07-11 14:55:04.610  - error: zigbee.0 (7238) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
2024-07-11 14:55:04.874  - info: zigbee.0 (7238) List of port: [{"path":"/dev/ttyACM0","manufacturer":"ITEAD","serialNumber":"20231214181142","pnpId":"usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20231214181142-if00","vendorId":"1a86","productId":"55d4"},{"path":"/dev/ttyAMA0"}]
2024-07-11 14:55:33.447  - info: admin.0 (846) <== Disconnect system.user.admin from ::ffff:192.168.2.106
2024-07-11 14:55:33.660  - warn: zigbee.0 (7238) Got terminate signal. Checking desired PID: 0 vs own PID 7238
2024-07-11 14:55:33.695  - info: host.iobroker instance system.adapter.zigbee.0 started with pid 7429
2024-07-11 14:55:33.664  - info: zigbee.0 (7238) cleaned everything up...
2024-07-11 14:55:33.677  - info: zigbee.0 (7238) Zigbee: disabling joining new devices.
2024-07-11 14:55:33.895  - warn: zigbee.0 (7238) Failed to stop zigbee during startup
2024-07-11 14:55:33.897  - info: zigbee.0 (7238) terminating
2024-07-11 14:55:33.900  - info: zigbee.0 (7238) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-11 14:55:33.923  - warn: zigbee.0 (7238) Got terminate signal. Checking desired PID: 7429 vs own PID 7238
2024-07-11 14:55:34.165  - info: zigbee.0 (7238) terminating
2024-07-11 14:55:34.556  - info: host.iobroker instance system.adapter.zigbee.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2024-07-11 14:55:34.556  - info: host.iobroker Do not restart adapter system.adapter.zigbee.0 because desired by instance
2024-07-11 14:55:33.447  - info: admin.0 (846) <== Disconnect system.user.admin from ::ffff:192.168.2.106
2024-07-11 14:55:33.660  - warn: zigbee.0 (7238) Got terminate signal. Checking desired PID: 0 vs own PID 7238
2024-07-11 14:55:33.695  - info: host.iobroker instance system.adapter.zigbee.0 started with pid 7429
2024-07-11 14:55:33.664  - info: zigbee.0 (7238) cleaned everything up...
2024-07-11 14:55:33.677  - info: zigbee.0 (7238) Zigbee: disabling joining new devices.
2024-07-11 14:55:33.895  - warn: zigbee.0 (7238) Failed to stop zigbee during startup
2024-07-11 14:55:33.897  - info: zigbee.0 (7238) terminating
2024-07-11 14:55:33.900  - info: zigbee.0 (7238) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-11 14:55:33.923  - warn: zigbee.0 (7238) Got terminate signal. Checking desired PID: 7429 vs own PID 7238
2024-07-11 14:55:34.165  - info: zigbee.0 (7238) terminating
2024-07-11 14:55:34.556  - info: host.iobroker instance system.adapter.zigbee.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2024-07-11 14:55:34.556  - info: host.iobroker Do not restart adapter system.adapter.zigbee.0 because desired by instance
2024-07-11 14:55:39.834  - info: zigbee.0 (7429) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.4, js-controller: 5.0.19
2024-07-11 14:55:39.953  - info: zigbee.0 (7429) Starting Zigbee  npm ...
2024-07-11 14:55:40.439  - info: zigbee.0 (7429) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 14:55:39.834  - info: zigbee.0 (7429) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.4, js-controller: 5.0.19
2024-07-11 14:55:39.953  - info: zigbee.0 (7429) Starting Zigbee  npm ...
2024-07-11 14:55:40.439  - info: zigbee.0 (7429) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 14:55:44.622  - error: zigbee.0 (7429) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-07-11 14:55:44.624  - error: zigbee.0 (7429) Failed to start Zigbee
2024-07-11 14:55:44.624  - error: zigbee.0 (7429) Error herdsman start
2024-07-11 14:55:44.622  - error: zigbee.0 (7429) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-07-11 14:55:44.624  - error: zigbee.0 (7429) Failed to start Zigbee
2024-07-11 14:55:44.624  - error: zigbee.0 (7429) Error herdsman start
2024-07-11 14:55:54.630  - info: zigbee.0 (7429) Try to reconnect. 1 attempts left
2024-07-11 14:55:54.631  - info: zigbee.0 (7429) Starting Zigbee  npm ...
2024-07-11 14:55:54.645  - info: zigbee.0 (7429) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 14:55:54.630  - info: zigbee.0 (7429) Try to reconnect. 1 attempts left
2024-07-11 14:55:54.631  - info: zigbee.0 (7429) Starting Zigbee  npm ...
2024-07-11 14:55:54.645  - info: zigbee.0 (7429) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 14:56:25.061  - error: zigbee.0 (7429) Starting zigbee-herdsman problem : "Failure to connect"
2024-07-11 14:56:25.063  - error: zigbee.0 (7429) Failed to start Zigbee
2024-07-11 14:56:25.064  - error: zigbee.0 (7429) Error herdsman start
2024-07-11 14:56:25.061  - error: zigbee.0 (7429) Starting zigbee-herdsman problem : "Failure to connect"
2024-07-11 14:56:25.063  - error: zigbee.0 (7429) Failed to start Zigbee
2024-07-11 14:56:25.064  - error: zigbee.0 (7429) Error herdsman start

Mir fehlen da Log Meldungen von vor 14:55:04 - die erste Fehlermeldung ist bereits ein Problem welches darauf hin deutet das der Adapter davor nicht sauber war. Bitte Posten.

Hast du sicher gestellt das der Adapter angehalten war und nicht mehr lief bevor du die Daten im Verzeichnis gelöscht hast ? Wenn nein dann schreibt der Adapter die am Ende.

A.

[aupex]

@asgothian
Das war das komplette Log, das mir angezeigt wurde. Würde es helfen ein Log nach einem reboot zu posten?
Kann man es irgendwie nach Adaptern filtern oder soll ich es komplett einstellen?

2024-07-11 17:37:21.275  - info: host.iobroker stopInstance system.adapter.zigbee.0 (force=false, process=true)
2024-07-11 17:37:21.286  - info: zigbee.0 (1176) Got terminate signal TERMINATE_YOURSELF
2024-07-11 17:37:21.289  - info: zigbee.0 (1176) cleaned everything up...
2024-07-11 17:37:21.296  - info: zigbee.0 (1176) Zigbee: disabling joining new devices.
2024-07-11 17:37:21.374  - warn: zigbee.0 (1176) Failed to stop zigbee during startup
2024-07-11 17:37:21.375  - info: zigbee.0 (1176) terminating
2024-07-11 17:37:21.377  - info: zigbee.0 (1176) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-11 17:37:21.508  - info: host.iobroker stopInstance system.adapter.zigbee.0 send kill signal
2024-07-11 17:37:21.791  - info: zigbee.0 (1176) terminating
2024-07-11 17:37:22.021  - info: host.iobroker instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-07-11 17:37:21.275  - info: host.iobroker stopInstance system.adapter.zigbee.0 (force=false, process=true)
2024-07-11 17:37:21.286  - info: zigbee.0 (1176) Got terminate signal TERMINATE_YOURSELF
2024-07-11 17:37:21.289  - info: zigbee.0 (1176) cleaned everything up...
2024-07-11 17:37:21.296  - info: zigbee.0 (1176) Zigbee: disabling joining new devices.
2024-07-11 17:37:21.374  - warn: zigbee.0 (1176) Failed to stop zigbee during startup
2024-07-11 17:37:21.375  - info: zigbee.0 (1176) terminating
2024-07-11 17:37:21.377  - info: zigbee.0 (1176) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-11 17:37:21.508  - info: host.iobroker stopInstance system.adapter.zigbee.0 send kill signal
2024-07-11 17:37:21.791  - info: zigbee.0 (1176) terminating
2024-07-11 17:37:22.021  - info: host.iobroker instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-07-11 17:37:24.625  - info: host.iobroker instance system.adapter.zigbee.0 started with pid 2133
2024-07-11 17:37:30.742  - info: zigbee.0 (2133) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.4, js-controller: 5.0.19
2024-07-11 17:37:30.862  - info: zigbee.0 (2133) Starting Zigbee  npm ...
2024-07-11 17:37:31.292  - info: zigbee.0 (2133) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 17:37:30.742  - info: zigbee.0 (2133) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.4, js-controller: 5.0.19
2024-07-11 17:37:30.862  - info: zigbee.0 (2133) Starting Zigbee  npm ...
2024-07-11 17:37:31.292  - info: zigbee.0 (2133) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 17:37:35.470  - error: zigbee.0 (2133) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-07-11 17:37:35.471  - error: zigbee.0 (2133) Failed to start Zigbee
2024-07-11 17:37:35.472  - error: zigbee.0 (2133) Error herdsman start
2024-07-11 17:37:35.470  - error: zigbee.0 (2133) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2024-07-11 17:37:35.471  - error: zigbee.0 (2133) Failed to start Zigbee
2024-07-11 17:37:35.472  - error: zigbee.0 (2133) Error herdsman start
2024-07-11 17:37:45.477  - info: zigbee.0 (2133) Try to reconnect. 1 attempts left
2024-07-11 17:37:45.478  - info: zigbee.0 (2133) Starting Zigbee  npm ...
2024-07-11 17:37:45.492  - info: zigbee.0 (2133) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 17:37:45.477  - info: zigbee.0 (2133) Try to reconnect. 1 attempts left
2024-07-11 17:37:45.478  - info: zigbee.0 (2133) Starting Zigbee  npm ...
2024-07-11 17:37:45.492  - info: zigbee.0 (2133) Installed Version: iobroker.zigbee@1.10.3
2024-07-11 17:38:15.923  - error: zigbee.0 (2133) Starting zigbee-herdsman problem : "Failure to connect"
2024-07-11 17:38:15.924  - error: zigbee.0 (2133) Failed to start Zigbee
2024-07-11 17:38:15.926  - error: zigbee.0 (2133) Error herdsman start
2024-07-11 17:38:15.923  - error: zigbee.0 (2133) Starting zigbee-herdsman problem : "Failure to connect"
2024-07-11 17:38:15.924  - error: zigbee.0 (2133) Failed to start Zigbee
2024-07-11 17:38:15.926  - error: zigbee.0 (2133) Error herdsman start

Das ist jetzt nach einem Adapter-neustart

[arteck]

@asgothian

usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20231214181142-if00

ist ein P

@aupex
also nochmal ganz langsam

auf der console

iob stop
rm -R /opt/iobroker/iobroker-data/zigbee_0
iob start

geht es jetzt

[stefande]

@arteck sagte in Sonoff Zigbee 3.0 Dongle "Failure to connect":

@asgothian

usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20231214181142-if00

ist ein P

NEIN der V2 ist ein E !!!

[aupex]

@arteck
Ich probiere es später gleich aus. Btw es ist ein "e". Habe ich versäumt zu schreiben.

[Thomas Braun]

@aupex

Die Sonoff Zigbee Dongles gibt es in zwei Varianten, die jeweils einen anderen 'Treiber' benötigen. Entweder den 'Z-Stack' oder den 'EZSP'-Stack (oder so ähnlich...) Musst du evtl. mal umstellen.

[aupex]

@thomas-braun
Hallo,
Es ist ein "e" weshalb ich ezsp/efr32 eingestellt habe.

[Thomas Braun]

@aupex

So aus Interesse:

Wie meldet der sich in

lsusb

denn?

[aupex]

@thomas-braun

pi@iobroker:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1a86:55d4 QinHeng Electronics SONOFF Zigbee 3.0 USB Dongle Plus V2
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Thomas Braun]

@aupex

Danke! Damit kann ich einen Check in

iob diag

einbauen und eine entsprechende Empfehlung geben.

[aupex]

@arteck said in Sonoff Zigbee 3.0 Dongle "Failure to connect":

rm -R /opt/iobroker/iobroker-data/zigbee_0

VIELEN DANK.
Jetzt wird der Adapter grün. Habe vorher nur den Adapter gestoppt, nicht aber den IObroker.
Da ich sowieso neu anlernen muss, wollte ich einen anderen Kanal auswählen, weshalb ich einen Kanalscan machen wollte. Dieser wurde mit folgendem Log beendet:

2024-07-12 15:26:40.922  - info: zigbee.0 (7854) Zigbee started
2024-07-12 15:26:41.389  - info: zigbee.0 (7854) debug devices set to []
2024-07-12 15:26:40.873  - info: zigbee.0 (7854) Coordinator firmware version: {"type":"EZSP v12","meta":{"product":12,"majorrel":"7","minorrel":"3","maintrel":"1 ","revision":"7.3.1.0 build 176"}}
2024-07-12 15:26:40.876  - info: zigbee.0 (7854) Unable to disable LED, unsupported function.
2024-07-12 15:26:40.904  - info: zigbee.0 (7854)   --> transmitPower : normal
2024-07-12 15:26:40.920  - info: zigbee.0 (7854) Currently no devices.
2024-07-12 15:26:40.922  - info: zigbee.0 (7854) Zigbee started
2024-07-12 15:26:41.389  - info: zigbee.0 (7854) debug devices set to []
2024-07-12 15:26:45.712  - error: zigbee.0 (7854) 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().
2024-07-12 15:26:45.713  - error: zigbee.0 (7854) unhandled promise rejection: Cannot read properties of undefined (reading 'waitFor')
2024-07-12 15:26:46.028  - error: zigbee.0 (7854) TypeError: Cannot read properties of undefined (reading 'waitFor')
    at ZigbeeController.getChannelsEnergy (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1010:54)
    at Commands.getChannels (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:513:52)
    at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:84:34)
    at Zigbee.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:16:48)
    at Zigbee.emit (node:events:529:35)
    at Zigbee.emit (node:domain:489:12)
    at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11114:34)
    at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:379:37)
    at processImmediate (node:internal/timers:476:21)
2024-07-12 15:26:46.029  - error: zigbee.0 (7854) Cannot read properties of undefined (reading 'waitFor')
2024-07-12 15:26:46.041  - info: zigbee.0 (7854) cleaned everything up...
2024-07-12 15:26:46.045  - info: zigbee.0 (7854) Zigbee: disabling joining new devices.
2024-07-12 15:26:46.390  - info: zigbee.0 (7854) terminating
2024-07-12 15:26:46.393  - warn: zigbee.0 (7854) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-07-12 15:26:46.543  - info: zigbee.0 (7854) terminating
2024-07-12 15:26:47.027  - error: host.iobroker Caught by controller[1]: zh:controller: Failed to disable join on stop: TypeError: Cannot read properties of undefined (reading 'permitJoin')
2024-07-12 15:26:47.028  - error: host.iobroker Caught by controller[2]: zhc:lixee: Was not able to detect the Linky linky_mode. Default to historique
2024-07-12 15:26:47.029  - error: host.iobroker Caught by controller[3]: zhc:lixee: Was not able to detect the Linky energy_phase. Default to single_phase
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[4]: zhc:lixee: Not able to detect the current tarif. Not filtering any expose...
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[5]: 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(). The promise rejected with the reason:
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[6]: TypeError: Cannot read properties of undefined (reading 'waitFor')
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[6]:     at ZigbeeController.getChannelsEnergy (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1010:54)
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[6]:     at Commands.getChannels (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:513:52)
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[6]:     at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:84:34)
2024-07-12 15:26:47.031  - error: host.iobroker Caught by controller[6]:     at Zigbee.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:16:48)
2024-07-12 15:26:47.031  - error: host.iobroker Caught by controller[6]:     at Zigbee.emit (node:events:529:35)
2024-07-12 15:26:47.031  - error: host.iobroker Caught by controller[6]:     at Zigbee.emit (node:domain:489:12)
2024-07-12 15:26:47.031  - error: host.iobroker Caught by controller[6]:     at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11114:34)
2024-07-12 15:26:47.031  - error: host.iobroker Caught by controller[6]:     at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:379:37)
2024-07-12 15:26:47.032  - error: host.iobroker Caught by controller[6]:     at processImmediate (node:internal/timers:476:21)
2024-07-12 15:26:47.032  - error: host.iobroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2024-07-12 15:26:47.032  - info: host.iobroker Restart adapter system.adapter.zigbee.0 because enabled
2024-07-12 15:26:45.712  - error: zigbee.0 (7854) 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().
2024-07-12 15:26:45.713  - error: zigbee.0 (7854) unhandled promise rejection: Cannot read properties of undefined (reading 'waitFor')
2024-07-12 15:26:46.028  - error: zigbee.0 (7854) TypeError: Cannot read properties of undefined (reading 'waitFor')
    at ZigbeeController.getChannelsEnergy (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1010:54)
    at Commands.getChannels (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:513:52)
    at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:84:34)
    at Zigbee.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:16:48)
    at Zigbee.emit (node:events:529:35)
    at Zigbee.emit (node:domain:489:12)
    at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11114:34)
    at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:379:37)
    at processImmediate (node:internal/timers:476:21)
2024-07-12 15:26:46.029  - error: zigbee.0 (7854) Cannot read properties of undefined (reading 'waitFor')
2024-07-12 15:26:46.041  - info: zigbee.0 (7854) cleaned everything up...
2024-07-12 15:26:46.045  - info: zigbee.0 (7854) Zigbee: disabling joining new devices.
2024-07-12 15:26:46.390  - info: zigbee.0 (7854) terminating
2024-07-12 15:26:46.393  - warn: zigbee.0 (7854) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-07-12 15:26:46.543  - info: zigbee.0 (7854) terminating
2024-07-12 15:26:47.027  - error: host.iobroker Caught by controller[1]: zh:controller: Failed to disable join on stop: TypeError: Cannot read properties of undefined (reading 'permitJoin')
2024-07-12 15:26:47.028  - error: host.iobroker Caught by controller[2]: zhc:lixee: Was not able to detect the Linky linky_mode. Default to historique
2024-07-12 15:26:47.029  - error: host.iobroker Caught by controller[3]: zhc:lixee: Was not able to detect the Linky energy_phase. Default to single_phase
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[4]: zhc:lixee: Not able to detect the current tarif. Not filtering any expose...
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[5]: 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(). The promise rejected with the reason:
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[6]: TypeError: Cannot read properties of undefined (reading 'waitFor')
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[6]:     at ZigbeeController.getChannelsEnergy (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:1010:54)
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[6]:     at Commands.getChannels (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:513:52)
2024-07-12 15:26:47.030  - error: host.iobroker Caught by controller[6]:     at Commands.onMessage (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:84:34)
2024-07-12 15:26:47.031  - error: host.iobroker Caught by controller[6]:     at Zigbee.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/lib/commands.js:16:48)
2024-07-12 15:26:47.031  - error: host.iobroker Caught by controller[6]:     at Zigbee.emit (node:events:529:35)
2024-07-12 15:26:47.031  - error: host.iobroker Caught by controller[6]:     at Zigbee.emit (node:domain:489:12)
2024-07-12 15:26:47.031  - error: host.iobroker Caught by controller[6]:     at change (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:11114:34)
2024-07-12 15:26:47.031  - error: host.iobroker Caught by controller[6]:     at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:379:37)
2024-07-12 15:26:47.032  - error: host.iobroker Caught by controller[6]:     at processImmediate (node:internal/timers:476:21)
2024-07-12 15:26:47.032  - error: host.iobroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2024-07-12 15:26:47.032  - info: host.iobroker Restart adapter system.adapter.zigbee.0 because enabled
2024-07-12 15:27:17.214  - info: host.iobroker instance system.adapter.zigbee.0 started with pid 7870
2024-07-12 15:27:23.232  - info: zigbee.0 (7870) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.4, js-controller: 5.0.19
2024-07-12 15:27:23.352  - info: zigbee.0 (7870) Starting Zigbee  npm ...
2024-07-12 15:27:23.793  - info: zigbee.0 (7870) Installed Version: iobroker.zigbee@1.10.3
2024-07-12 15:27:23.232  - info: zigbee.0 (7870) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.4, js-controller: 5.0.19
2024-07-12 15:27:23.352  - info: zigbee.0 (7870) Starting Zigbee  npm ...
2024-07-12 15:27:23.793  - info: zigbee.0 (7870) Installed Version: iobroker.zigbee@1.10.3
2024-07-12 15:27:29.017  - info: zigbee.0 (7870) Coordinator firmware version: {"type":"EZSP v12","meta":{"product":12,"majorrel":"7","minorrel":"3","maintrel":"1 ","revision":"7.3.1.0 build 176"}}
2024-07-12 15:27:29.019  - info: zigbee.0 (7870) Unable to disable LED, unsupported function.
2024-07-12 15:27:29.046  - info: zigbee.0 (7870)   --> transmitPower : normal
2024-07-12 15:27:29.062  - info: zigbee.0 (7870) Currently no devices.
2024-07-12 15:27:29.064  - info: zigbee.0 (7870) Zigbee started
2024-07-12 15:27:29.433  - info: zigbee.0 (7870) debug devices set to []
2024-07-12 15:27:29.017  - info: zigbee.0 (7870) Coordinator firmware version: {"type":"EZSP v12","meta":{"product":12,"majorrel":"7","minorrel":"3","maintrel":"1 ","revision":"7.3.1.0 build 176"}}
2024-07-12 15:27:29.019  - info: zigbee.0 (7870) Unable to disable LED, unsupported function.
2024-07-12 15:27:29.046  - info: zigbee.0 (7870)   --> transmitPower : normal
2024-07-12 15:27:29.062  - info: zigbee.0 (7870) Currently no devices.
2024-07-12 15:27:29.064  - info: zigbee.0 (7870) Zigbee started
2024-07-12 15:27:29.433  - info: zigbee.0 (7870) debug devices set to []

[aupex]

@thomas-braun

======================= SUMMARY =======================
                        v.2024-05-22


 Static hostname: iobroker
       Icon name: computer
Operating System: Debian GNU/Linux 12 (bookworm)
          Kernel: Linux 6.1.21-v8+
    Architecture: arm64

Installation:           native
Kernel:                 aarch64
Userland:               32 bit
Timezone:               Europe/Berlin (CEST, +0200)
User-ID:                1000
Display-Server:         false
Boot Target:            multi-user.target

Pending OS-Updates:     0
Pending iob updates:    0

Nodejs-Installation:
/usr/bin/nodejs         v18.20.4
/usr/bin/node           v18.20.4
/usr/bin/npm            10.7.0
/usr/bin/npx            10.7.0
/usr/bin/corepack       0.28.0

Recommended versions are nodejs 18.20.4 and npm 10.7.0
Your nodejs installation is correct

MEMORY:
               total        used        free      shared  buff/cache   available
Mem:            4.0G        1.3G        2.1G        1.2M        709M        2.7G
Swap:           209M          0B        209M
Total:          4.2G        1.3G        2.3G

Active iob-Instances:   18
Active repo(s): stable

ioBroker Core:          js-controller           5.0.19
                        admin                   6.17.14

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin and web instance:
+ system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

Objects:                10178
States:                 7878

Size of iob-Database:

48M     /opt/iobroker/iobroker-data/objects.jsonl
7.8M    /opt/iobroker/iobroker-data/states.jsonl



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

[aupex]

Die Fehler sind irgendwie alle verschwunden und es läuft jetzt reibungslos.

Vielen Dank für eure Hilfe.

[Thomas Braun]

@aupex

Dann bring jetzt nodejs auf die Version 20:

iob nodejs-update 20