NEWS
Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0
-
als COM Id habe ich hinterlegt "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00"
total 0 drwxr-xr-x 2 root root 60 May 31 13:08 . drwxr-xr-x 4 root root 80 May 31 13:08 .. lrwxrwxrwx 1 root root 13 May 31 13:08 usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00 -> ../../ttyACM0Hier der Log aus der Console
2024-05-31 14:36:03.302 - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-05-31 14:36:03.340 - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23 2024-05-31 14:36:02.563 - info: host.raspberry4 stopInstance system.adapter.zigbee.0 (force=false, process=true) 2024-05-31 14:36:02.571 - info: zigbee.0 (3717) Got terminate signal TERMINATE_YOURSELF 2024-05-31 14:36:02.602 - info: host.raspberry4 stopInstance system.adapter.zigbee.0 send kill signal 2024-05-31 14:36:02.575 - info: zigbee.0 (3717) cleaned everything up... 2024-05-31 14:36:02.582 - info: zigbee.0 (3717) Zigbee: disabling joining new devices. 2024-05-31 14:36:02.634 - warn: zigbee.0 (3717) Failed to stop zigbee during startup 2024-05-31 14:36:02.635 - info: zigbee.0 (3717) terminating 2024-05-31 14:36:02.636 - info: zigbee.0 (3717) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-05-31 14:36:03.076 - info: zigbee.0 (3717) terminating 2024-05-31 14:36:03.302 - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-05-31 14:36:03.340 - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23 2024-05-31 14:36:05.672 - info: host.raspberry4 instance system.adapter.zigbee.0 started with pid 3768 2024-05-31 14:36:10.832 - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19 2024-05-31 14:36:10.939 - info: zigbee.0 (3768) delete old Backup files. keep only last 10 2024-05-31 14:36:10.942 - info: zigbee.0 (3768) Starting Zigbee npm ... 2024-05-31 14:36:11.303 - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3 2024-05-31 14:36:10.832 - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19 2024-05-31 14:36:10.939 - info: zigbee.0 (3768) delete old Backup files. keep only last 10 2024-05-31 14:36:10.942 - info: zigbee.0 (3768) Starting Zigbee npm ... 2024-05-31 14:36:11.303 - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3 2024-05-31 14:36:15.301 - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information" 2024-05-31 14:36:15.302 - error: zigbee.0 (3768) Failed to start Zigbee 2024-05-31 14:36:15.303 - error: zigbee.0 (3768) Error herdsman start 2024-05-31 14:36:15.301 - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information" 2024-05-31 14:36:15.302 - error: zigbee.0 (3768) Failed to start Zigbee 2024-05-31 14:36:15.303 - error: zigbee.0 (3768) Error herdsman start@jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:
2024-05-31 14:36:15.301 - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
Da ist die PanID, die extended PanID oder der Transportschlüssel falsch. Früher standen die Abweichungen mal im Log. Ist wohl irgendwann unter den Tisch gefallen.
-
@jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:
2024-05-31 14:36:15.301 - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
Da ist die PanID, die extended PanID oder der Transportschlüssel falsch. Früher standen die Abweichungen mal im Log. Ist wohl irgendwann unter den Tisch gefallen.
Hier noch mal der Log mit debug Info:
2024-05-31 14:39:51.043 - info: host.raspberry4 stopInstance system.adapter.zigbee.0 (force=false, process=true) 2024-05-31 14:39:51.056 - info: zigbee.0 (3869) Got terminate signal TERMINATE_YOURSELF 2024-05-31 14:39:51.061 - info: zigbee.0 (3869) cleaned everything up... 2024-05-31 14:39:51.079 - info: zigbee.0 (3869) Zigbee: disabling joining new devices. 2024-05-31 14:39:51.134 - warn: zigbee.0 (3869) Failed to stop zigbee during startup 2024-05-31 14:39:51.134 - info: zigbee.0 (3869) terminating 2024-05-31 14:39:51.136 - debug: zigbee.0 (3869) Plugin sentry destroyed 2024-05-31 14:39:51.136 - info: zigbee.0 (3869) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-05-31 14:39:51.160 - info: host.raspberry4 stopInstance system.adapter.zigbee.0 send kill signal 2024-05-31 14:39:51.563 - info: zigbee.0 (3869) terminating 2024-05-31 14:39:51.736 - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-05-31 14:39:54.222 - info: host.raspberry4 instance system.adapter.zigbee.0 started with pid 3897 2024-05-31 14:39:58.744 - debug: zigbee.0 (3897) Redis Objects: Use Redis connection: 127.0.0.1:9001 2024-05-31 14:39:58.800 - debug: zigbee.0 (3897) Objects client ready ... initialize now 2024-05-31 14:39:58.804 - debug: zigbee.0 (3897) Objects create System PubSub Client 2024-05-31 14:39:58.806 - debug: zigbee.0 (3897) Objects create User PubSub Client 2024-05-31 14:39:58.887 - debug: zigbee.0 (3897) Objects client initialize lua scripts 2024-05-31 14:39:58.900 - debug: zigbee.0 (3897) Objects connected to redis: 127.0.0.1:9001 2024-05-31 14:39:58.949 - debug: zigbee.0 (3897) Redis States: Use Redis connection: 127.0.0.1:9000 2024-05-31 14:39:58.972 - debug: zigbee.0 (3897) States create System PubSub Client 2024-05-31 14:39:58.974 - debug: zigbee.0 (3897) States create User PubSub Client 2024-05-31 14:39:59.056 - debug: zigbee.0 (3897) States connected to redis: 127.0.0.1:9000 2024-05-31 14:39:59.107 - debug: zigbee.0 (3897) Plugin sentry Initialize Plugin (enabled=true) 2024-05-31 14:39:59.625 - info: zigbee.0 (3897) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19 2024-05-31 14:39:59.659 - debug: zigbee.0 (3897) Using zigbee-herdsman with settings: {"network":{"panID":6754,"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"extenedPanID":[208,221,220,221,221,210,222,173]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00","adapter":"ezsp"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false},"legacy":false} 2024-05-31 14:39:59.722 - info: zigbee.0 (3897) delete old Backup files. keep only last 10 2024-05-31 14:39:59.724 - info: zigbee.0 (3897) Starting Zigbee npm ... 2024-05-31 14:39:59.778 - debug: zigbee.0 (3897) Starting zigbee-herdsman... 2024-05-31 14:40:00.089 - info: zigbee.0 (3897) Installed Version: iobroker.zigbee@1.10.3 2024-05-31 14:40:00.488 - debug: zigbee.0 (3897) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2024_05_31-14_39_59.tar.gz success 2024-05-31 14:39:58.744 - debug: zigbee.0 (3897) Redis Objects: Use Redis connection: 127.0.0.1:9001 2024-05-31 14:39:58.800 - debug: zigbee.0 (3897) Objects client ready ... initialize now 2024-05-31 14:39:58.804 - debug: zigbee.0 (3897) Objects create System PubSub Client 2024-05-31 14:39:58.806 - debug: zigbee.0 (3897) Objects create User PubSub Client 2024-05-31 14:39:58.887 - debug: zigbee.0 (3897) Objects client initialize lua scripts 2024-05-31 14:39:58.900 - debug: zigbee.0 (3897) Objects connected to redis: 127.0.0.1:9001 2024-05-31 14:39:58.949 - debug: zigbee.0 (3897) Redis States: Use Redis connection: 127.0.0.1:9000 2024-05-31 14:39:58.972 - debug: zigbee.0 (3897) States create System PubSub Client 2024-05-31 14:39:58.974 - debug: zigbee.0 (3897) States create User PubSub Client 2024-05-31 14:39:59.056 - debug: zigbee.0 (3897) States connected to redis: 127.0.0.1:9000 2024-05-31 14:39:59.107 - debug: zigbee.0 (3897) Plugin sentry Initialize Plugin (enabled=true) 2024-05-31 14:39:59.625 - info: zigbee.0 (3897) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19 2024-05-31 14:39:59.659 - debug: zigbee.0 (3897) Using zigbee-herdsman with settings: {"network":{"panID":6754,"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"extenedPanID":[208,221,220,221,221,210,222,173]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00","adapter":"ezsp"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false},"legacy":false} 2024-05-31 14:39:59.722 - info: zigbee.0 (3897) delete old Backup files. keep only last 10 2024-05-31 14:39:59.724 - info: zigbee.0 (3897) Starting Zigbee npm ... 2024-05-31 14:39:59.778 - debug: zigbee.0 (3897) Starting zigbee-herdsman... 2024-05-31 14:40:00.089 - info: zigbee.0 (3897) Installed Version: iobroker.zigbee@1.10.3 2024-05-31 14:40:00.488 - debug: zigbee.0 (3897) Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2024_05_31-14_39_59.tar.gz success 2024-05-31 14:40:04.040 - error: zigbee.0 (3897) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information" 2024-05-31 14:40:04.042 - error: zigbee.0 (3897) Failed to start Zigbee 2024-05-31 14:40:04.043 - error: zigbee.0 (3897) Error herdsman start 2024-05-31 14:40:04.040 - error: zigbee.0 (3897) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information" 2024-05-31 14:40:04.042 - error: zigbee.0 (3897) Failed to start Zigbee 2024-05-31 14:40:04.043 - error: zigbee.0 (3897) Error herdsman start -
@jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:
2024-05-31 14:36:15.301 - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
Da ist die PanID, die extended PanID oder der Transportschlüssel falsch. Früher standen die Abweichungen mal im Log. Ist wohl irgendwann unter den Tisch gefallen.
-
das hatte ich ja auch vermutet. Nur wie finde ich raus welche die Richtigen sind?
@jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:
Nur wie finde ich raus welche die Richtigen sind?
Keine Ahnung. Wie gesagt, früher stands mal im Log drin.
-
als COM Id habe ich hinterlegt "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00"
total 0 drwxr-xr-x 2 root root 60 May 31 13:08 . drwxr-xr-x 4 root root 80 May 31 13:08 .. lrwxrwxrwx 1 root root 13 May 31 13:08 usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00 -> ../../ttyACM0Hier der Log aus der Console
2024-05-31 14:36:03.302 - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-05-31 14:36:03.340 - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23 2024-05-31 14:36:02.563 - info: host.raspberry4 stopInstance system.adapter.zigbee.0 (force=false, process=true) 2024-05-31 14:36:02.571 - info: zigbee.0 (3717) Got terminate signal TERMINATE_YOURSELF 2024-05-31 14:36:02.602 - info: host.raspberry4 stopInstance system.adapter.zigbee.0 send kill signal 2024-05-31 14:36:02.575 - info: zigbee.0 (3717) cleaned everything up... 2024-05-31 14:36:02.582 - info: zigbee.0 (3717) Zigbee: disabling joining new devices. 2024-05-31 14:36:02.634 - warn: zigbee.0 (3717) Failed to stop zigbee during startup 2024-05-31 14:36:02.635 - info: zigbee.0 (3717) terminating 2024-05-31 14:36:02.636 - info: zigbee.0 (3717) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-05-31 14:36:03.076 - info: zigbee.0 (3717) terminating 2024-05-31 14:36:03.302 - info: host.raspberry4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-05-31 14:36:03.340 - info: admin.0 (2912) <== Disconnect system.user.admin from ::ffff:192.168.0.23 2024-05-31 14:36:05.672 - info: host.raspberry4 instance system.adapter.zigbee.0 started with pid 3768 2024-05-31 14:36:10.832 - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19 2024-05-31 14:36:10.939 - info: zigbee.0 (3768) delete old Backup files. keep only last 10 2024-05-31 14:36:10.942 - info: zigbee.0 (3768) Starting Zigbee npm ... 2024-05-31 14:36:11.303 - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3 2024-05-31 14:36:10.832 - info: zigbee.0 (3768) starting. Version 1.10.3 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.14.0, js-controller: 5.0.19 2024-05-31 14:36:10.939 - info: zigbee.0 (3768) delete old Backup files. keep only last 10 2024-05-31 14:36:10.942 - info: zigbee.0 (3768) Starting Zigbee npm ... 2024-05-31 14:36:11.303 - info: zigbee.0 (3768) Installed Version: iobroker.zigbee@1.10.3 2024-05-31 14:36:15.301 - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information" 2024-05-31 14:36:15.302 - error: zigbee.0 (3768) Failed to start Zigbee 2024-05-31 14:36:15.303 - error: zigbee.0 (3768) Error herdsman start 2024-05-31 14:36:15.301 - error: zigbee.0 (3768) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information" 2024-05-31 14:36:15.302 - error: zigbee.0 (3768) Failed to start Zigbee 2024-05-31 14:36:15.303 - error: zigbee.0 (3768) Error herdsman start@jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:
als COM Id habe ich hinterlegt "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00"
fehlt da nicht der Port?
umgestiegen von Proxmox auf Unraid
-
@jan-lange sagte in Hilfe beim Zigbee Controller mit Sonoff Zigbee 3.0:
als COM Id habe ich hinterlegt "/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00"
fehlt da nicht der Port?
Nein.
USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00 -
Nein.
USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124092219-if00@thomas-braun ok, dann wäre vllt noch möglich
Es ist zu achten dass am Ende kein leer Zeichen mitgenommen wirdumgestiegen von Proxmox auf Unraid
-
@thomas-braun ok, dann wäre vllt noch möglich
Es ist zu achten dass am Ende kein leer Zeichen mitgenommen wirdJa. Hier ist aber vermutlich das nvram/backup zu löschen.
-
Ja. Hier ist aber vermutlich das nvram/backup zu löschen.
-
@thomas-braun jep, hatte ich auch im parallel Thread geschrieben
@crunchip
Also ich habe mal die Backup gelöscht wie der User in parallel Thread: Allerdings bringt das bei mir nichts.rm: cannot remove '/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json': No such file or directoryIn dem Ordner zigbee_0 liegt jedoch eine andere Backup Datei macht es Sinn diese mal zu löschen?
dir /opt/iobroker/iobroker-data/zigbee_0/ backup_2024_06_03-11_08_00.tar.gz shepherd.dbHabe auch mal versucht die Default Werte zu nutzen. Bringt leider auch nichts.
-
@crunchip
Also ich habe mal die Backup gelöscht wie der User in parallel Thread: Allerdings bringt das bei mir nichts.rm: cannot remove '/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json': No such file or directoryIn dem Ordner zigbee_0 liegt jedoch eine andere Backup Datei macht es Sinn diese mal zu löschen?
dir /opt/iobroker/iobroker-data/zigbee_0/ backup_2024_06_03-11_08_00.tar.gz shepherd.dbHabe auch mal versucht die Default Werte zu nutzen. Bringt leider auch nichts.
Habs jetzt noch mal versucht und wenn ich den Typ ebenfalls auf den init Wert stehen lass, dann bekommt er die Verbindung aufgebaut. Aber auch wirklich nur dann und wie in dem anderen Post nur mit dem Standard Werten.
Habe inzwischen auch mal ein Conbee testen können. Da klappt alles problemlos.
Support us
701
Online32.6k
Users82.1k
Topics1.3m
Posts