NEWS
Zigbee.0: You need save and run adapter before pairing!
Installation
51
Beiträge
8
Kommentatoren
5.2k
Aufrufe
7
Watching
-
25-03-18 21:09:53.074 - ^[[32minfo^[[39m: admin.0 (21591) <== Disconnect system.user.admin from ::ffff:192.168.2.66 2025-03-18 21:09:57.788 - ^[[32minfo^[[39m: admin.0 (21591) ==> Connected system.user.admin from ::ffff:192.168.2.66 2025-03-18 21:10:52.747 - ^[[32minfo^[[39m: host.raspi5 stopInstance system.adapter.zigbee.0 (force=false, process=true) 2025-03-18 21:10:52.751 - ^[[32minfo^[[39m: zigbee.0 (51917) Got terminate signal TERMINATE_YOURSELF 2025-03-18 21:10:52.793 - ^[[32minfo^[[39m: host.raspi5 stopInstance system.adapter.zigbee.0 send kill signal 2025-03-18 21:10:52.752 - ^[[32minfo^[[39m: zigbee.0 (51917) cleaned everything up... 2025-03-18 21:10:52.760 - ^[[32minfo^[[39m: zigbee.0 (51917) Zigbee: disabling joining new devices. 2025-03-18 21:10:52.808 - ^[[33mwarn^[[39m: zigbee.0 (51917) Failed to stop zigbee during startup 2025-03-18 21:10:52.809 - ^[[32minfo^[[39m: zigbee.0 (51917) terminating 2025-03-18 21:10:52.810 - ^[[32minfo^[[39m: zigbee.0 (51917) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-03-18 21:10:52.822 - ^[[32minfo^[[39m: zigbee.0 (51917) debug devices set to [] 2025-03-18 21:10:52.888 - ^[[35msilly^[[39m: fritzdect.0 (22085) Objects system redis pmessage system.config/cfg.o.system.config:{"_id":"system.config","type":"config","common":{"name":{"en":"Syst> 2025-03-18 21:10:53.253 - ^[[32minfo^[[39m: zigbee.0 (51917) terminating 2025-03-18 21:10:53.334 - ^[[32minfo^[[39m: host.raspi5 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-03-18 21:10:56.515 - ^[[32minfo^[[39m: host.raspi5 instance system.adapter.zigbee.0 in version "1.10.14" started with pid 52284 2025-03-18 21:10:59.384 - ^[[32minfo^[[39m: zigbee.0 (52284) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-03-18 21:10:59.446 - ^[[32minfo^[[39m: zigbee.0 (52284) delete old Backup files. keep only last 10 2025-03-18 21:10:59.447 - ^[[32minfo^[[39m: zigbee.0 (52284) Starting Zigbee npm ... 2025-03-18 21:10:59.691 - ^[[32minfo^[[39m: zigbee.0 (52284) Installed Version: iobroker.zigbee@1.10.14 2025-03-18 21:12:31.357 - ^[[32minfo^[[39m: admin.0 (21591) <== Disconnect system.user.admin from ::ffff:192.168.2.66 2025-03-18 21:13:39.190 - ^[[32minfo^[[39m: admin.0 (21591) ==> Connected system.user.admin from ::ffff:192.168.2.66@nilli deine Logs zeigen das du den Adapter beendest bevor irgend ein Fehler auftritt.
Der erste Start des Adapters nach Konfiguration kann bis zu 5 Minuten dauern, wenn das erste Mal ein Funk Netz aufgebaut wird.
Bitte folgendes machen:
- Adapter anhalten
- 60 Sekunden warten
- log löschen
- Adapter starten
- 5 Minuten warten - entweder der Adapter wird grün oder es gibt Fehlermeldungen im Log.
- das log herunter laden, auf die zigbee-relevanten Zeilen reduzieren und als Text hier posten.
A.
-
25-03-18 21:09:53.074 - ^[[32minfo^[[39m: admin.0 (21591) <== Disconnect system.user.admin from ::ffff:192.168.2.66 2025-03-18 21:09:57.788 - ^[[32minfo^[[39m: admin.0 (21591) ==> Connected system.user.admin from ::ffff:192.168.2.66 2025-03-18 21:10:52.747 - ^[[32minfo^[[39m: host.raspi5 stopInstance system.adapter.zigbee.0 (force=false, process=true) 2025-03-18 21:10:52.751 - ^[[32minfo^[[39m: zigbee.0 (51917) Got terminate signal TERMINATE_YOURSELF 2025-03-18 21:10:52.793 - ^[[32minfo^[[39m: host.raspi5 stopInstance system.adapter.zigbee.0 send kill signal 2025-03-18 21:10:52.752 - ^[[32minfo^[[39m: zigbee.0 (51917) cleaned everything up... 2025-03-18 21:10:52.760 - ^[[32minfo^[[39m: zigbee.0 (51917) Zigbee: disabling joining new devices. 2025-03-18 21:10:52.808 - ^[[33mwarn^[[39m: zigbee.0 (51917) Failed to stop zigbee during startup 2025-03-18 21:10:52.809 - ^[[32minfo^[[39m: zigbee.0 (51917) terminating 2025-03-18 21:10:52.810 - ^[[32minfo^[[39m: zigbee.0 (51917) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-03-18 21:10:52.822 - ^[[32minfo^[[39m: zigbee.0 (51917) debug devices set to [] 2025-03-18 21:10:52.888 - ^[[35msilly^[[39m: fritzdect.0 (22085) Objects system redis pmessage system.config/cfg.o.system.config:{"_id":"system.config","type":"config","common":{"name":{"en":"Syst> 2025-03-18 21:10:53.253 - ^[[32minfo^[[39m: zigbee.0 (51917) terminating 2025-03-18 21:10:53.334 - ^[[32minfo^[[39m: host.raspi5 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-03-18 21:10:56.515 - ^[[32minfo^[[39m: host.raspi5 instance system.adapter.zigbee.0 in version "1.10.14" started with pid 52284 2025-03-18 21:10:59.384 - ^[[32minfo^[[39m: zigbee.0 (52284) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-03-18 21:10:59.446 - ^[[32minfo^[[39m: zigbee.0 (52284) delete old Backup files. keep only last 10 2025-03-18 21:10:59.447 - ^[[32minfo^[[39m: zigbee.0 (52284) Starting Zigbee npm ... 2025-03-18 21:10:59.691 - ^[[32minfo^[[39m: zigbee.0 (52284) Installed Version: iobroker.zigbee@1.10.14 2025-03-18 21:12:31.357 - ^[[32minfo^[[39m: admin.0 (21591) <== Disconnect system.user.admin from ::ffff:192.168.2.66 2025-03-18 21:13:39.190 - ^[[32minfo^[[39m: admin.0 (21591) ==> Connected system.user.admin from ::ffff:192.168.2.66Ich hab heute den gleichen fehler mit dem Zigbee Adapter, hat mir den ganzen Log voll geknallt mit Error und warnungen bin mir nicht ganz sicher hatte aber kurz vorher den Admin Adapter upgedatet. auf die 7.6.3 ob es damit im zusammenhang steht weiß ich nicht hab den Zigbee Adapter runter geworfen denke ich werde wieder alles auf die Philips Hue Bridge anmelden
-
@nilli deine Logs zeigen das du den Adapter beendest bevor irgend ein Fehler auftritt.
Der erste Start des Adapters nach Konfiguration kann bis zu 5 Minuten dauern, wenn das erste Mal ein Funk Netz aufgebaut wird.
Bitte folgendes machen:
- Adapter anhalten
- 60 Sekunden warten
- log löschen
- Adapter starten
- 5 Minuten warten - entweder der Adapter wird grün oder es gibt Fehlermeldungen im Log.
- das log herunter laden, auf die zigbee-relevanten Zeilen reduzieren und als Text hier posten.
A.
Danke für die Tips ! Leider ohne Erfolg. Adapter wird nicht grün und im Log findet sich bis jetzt 22:21 Uhr auch nichts weiter :-(
2025-03-18 22:04:38.280 - ^[[32minfo^[[39m: host.raspi5 "system.adapter.zigbee.0" disabled 2025-03-18 22:04:38.280 - ^[[32minfo^[[39m: host.raspi5 stopInstance system.adapter.zigbee.0 (force=false, process=true) 2025-03-18 22:04:38.284 - ^[[32minfo^[[39m: zigbee.0 (54373) Got terminate signal TERMINATE_YOURSELF 2025-03-18 22:04:38.325 - ^[[32minfo^[[39m: host.raspi5 stopInstance system.adapter.zigbee.0 send kill signal 2025-03-18 22:04:38.286 - ^[[32minfo^[[39m: zigbee.0 (54373) cleaned everything up... 2025-03-18 22:04:38.295 - ^[[32minfo^[[39m: zigbee.0 (54373) Zigbee: disabling joining new devices. 2025-03-18 22:04:38.346 - ^[[33mwarn^[[39m: zigbee.0 (54373) Failed to stop zigbee during startup 2025-03-18 22:04:38.346 - ^[[32minfo^[[39m: zigbee.0 (54373) terminating 2025-03-18 22:04:38.347 - ^[[32minfo^[[39m: zigbee.0 (54373) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-03-18 22:04:38.359 - ^[[32minfo^[[39m: zigbee.0 (54373) debug devices set to [] 2025-03-18 22:04:38.787 - ^[[32minfo^[[39m: zigbee.0 (54373) terminating 2025-03-18 22:04:38.870 - ^[[32minfo^[[39m: host.raspi5 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-03-18 22:06:47.993 - ^[[32minfo^[[39m: host.raspi5 "system.adapter.zigbee.0" enabled 2025-03-18 22:06:48.221 - ^[[32minfo^[[39m: host.raspi5 instance system.adapter.zigbee.0 in version "1.10.14" started with pid 54685 2025-03-18 22:06:49.859 - ^[[32minfo^[[39m: zigbee.0 (54685) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-03-18 22:06:49.892 - ^[[32minfo^[[39m: zigbee.0 (54685) delete old Backup files. keep only last 10 2025-03-18 22:06:49.893 - ^[[32minfo^[[39m: zigbee.0 (54685) Starting Zigbee npm ... 2025-03-18 22:06:50.020 - ^[[32minfo^[[39m: zigbee.0 (54685) Installed Version: iobroker.zigbee@1.10.14Was könnte ich noch zur Diagnose prüfen ? :thinking_face:
-
Ich hab heute den gleichen fehler mit dem Zigbee Adapter, hat mir den ganzen Log voll geknallt mit Error und warnungen bin mir nicht ganz sicher hatte aber kurz vorher den Admin Adapter upgedatet. auf die 7.6.3 ob es damit im zusammenhang steht weiß ich nicht hab den Zigbee Adapter runter geworfen denke ich werde wieder alles auf die Philips Hue Bridge anmelden
-
Danke für die Tips ! Leider ohne Erfolg. Adapter wird nicht grün und im Log findet sich bis jetzt 22:21 Uhr auch nichts weiter :-(
2025-03-18 22:04:38.280 - ^[[32minfo^[[39m: host.raspi5 "system.adapter.zigbee.0" disabled 2025-03-18 22:04:38.280 - ^[[32minfo^[[39m: host.raspi5 stopInstance system.adapter.zigbee.0 (force=false, process=true) 2025-03-18 22:04:38.284 - ^[[32minfo^[[39m: zigbee.0 (54373) Got terminate signal TERMINATE_YOURSELF 2025-03-18 22:04:38.325 - ^[[32minfo^[[39m: host.raspi5 stopInstance system.adapter.zigbee.0 send kill signal 2025-03-18 22:04:38.286 - ^[[32minfo^[[39m: zigbee.0 (54373) cleaned everything up... 2025-03-18 22:04:38.295 - ^[[32minfo^[[39m: zigbee.0 (54373) Zigbee: disabling joining new devices. 2025-03-18 22:04:38.346 - ^[[33mwarn^[[39m: zigbee.0 (54373) Failed to stop zigbee during startup 2025-03-18 22:04:38.346 - ^[[32minfo^[[39m: zigbee.0 (54373) terminating 2025-03-18 22:04:38.347 - ^[[32minfo^[[39m: zigbee.0 (54373) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-03-18 22:04:38.359 - ^[[32minfo^[[39m: zigbee.0 (54373) debug devices set to [] 2025-03-18 22:04:38.787 - ^[[32minfo^[[39m: zigbee.0 (54373) terminating 2025-03-18 22:04:38.870 - ^[[32minfo^[[39m: host.raspi5 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-03-18 22:06:47.993 - ^[[32minfo^[[39m: host.raspi5 "system.adapter.zigbee.0" enabled 2025-03-18 22:06:48.221 - ^[[32minfo^[[39m: host.raspi5 instance system.adapter.zigbee.0 in version "1.10.14" started with pid 54685 2025-03-18 22:06:49.859 - ^[[32minfo^[[39m: zigbee.0 (54685) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-03-18 22:06:49.892 - ^[[32minfo^[[39m: zigbee.0 (54685) delete old Backup files. keep only last 10 2025-03-18 22:06:49.893 - ^[[32minfo^[[39m: zigbee.0 (54685) Starting Zigbee npm ... 2025-03-18 22:06:50.020 - ^[[32minfo^[[39m: zigbee.0 (54685) Installed Version: iobroker.zigbee@1.10.14Was könnte ich noch zur Diagnose prüfen ? :thinking_face:
@nilli sagte in Zigbee.0: You need save and run adapter before pairing!:
Was könnte ich noch zur Diagnose prüfen ?
Bist du sicher das du da die Fehlermeldungen nicht heraus gefiltert hast ? Es muss Fehlermeldungen geben wenn der Adapter sich beendet.
Widerhol bitte den Test oben, stell aber vor dem Start den Zigbee-Adapter auf debug, nicht auf Info.
A.
-
@nilli sagte in Zigbee.0: You need save and run adapter before pairing!:
Was könnte ich noch zur Diagnose prüfen ?
Bist du sicher das du da die Fehlermeldungen nicht heraus gefiltert hast ? Es muss Fehlermeldungen geben wenn der Adapter sich beendet.
Widerhol bitte den Test oben, stell aber vor dem Start den Zigbee-Adapter auf debug, nicht auf Info.
A.
@asgothian said in Zigbee.0: You need save and run adapter before pairing!:
Protokoll auf debug gestellt :+1: . Es finden sich aber keine weiteren Einträge nach dem neustart.
2025-03-18 22:39:47.464 - ^[[32minfo^[[39m: admin.0 (21591) ==> Connected system.user.admin from ::ffff:192.168.2.66 2025-03-18 22:39:51.669 - ^[[32minfo^[[39m: admin.0 (21591) <== Disconnect system.user.admin from ::ffff:192.168.2.66 2025-03-18 22:39:58.499 - ^[[32minfo^[[39m: host.raspi5 "system.adapter.zigbee.0" disabled 2025-03-18 22:39:58.500 - ^[[32minfo^[[39m: host.raspi5 stopInstance system.adapter.zigbee.0 (force=false, process=true) 2025-03-18 22:39:58.503 - ^[[32minfo^[[39m: zigbee.0 (54685) Got terminate signal TERMINATE_YOURSELF 2025-03-18 22:39:58.545 - ^[[32minfo^[[39m: host.raspi5 stopInstance system.adapter.zigbee.0 send kill signal 2025-03-18 22:39:58.504 - ^[[32minfo^[[39m: zigbee.0 (54685) cleaned everything up... 2025-03-18 22:39:58.508 - ^[[32minfo^[[39m: zigbee.0 (54685) Zigbee: disabling joining new devices. 2025-03-18 22:39:58.545 - ^[[33mwarn^[[39m: zigbee.0 (54685) Failed to stop zigbee during startup 2025-03-18 22:39:58.546 - ^[[32minfo^[[39m: zigbee.0 (54685) terminating 2025-03-18 22:39:58.546 - ^[[32minfo^[[39m: zigbee.0 (54685) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-03-18 22:39:58.554 - ^[[32minfo^[[39m: zigbee.0 (54685) debug devices set to [] 2025-03-18 22:39:58.626 - ^[[35msilly^[[39m: fritzdect.0 (22085) Objects system redis pmessage system.config/cfg.o.system.config:{"_id":"system.config","type":"config","common":{"name":{"en":"System configuration","de":"Syst> 2025-03-18 22:39:59.004 - ^[[32minfo^[[39m: zigbee.0 (54685) terminating 2025-03-18 22:39:59.067 - ^[[32minfo^[[39m: host.raspi5 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-03-18 22:41:21.551 - ^[[32minfo^[[39m: host.raspi5 "system.adapter.zigbee.0" enabled 2025-03-18 22:41:21.770 - ^[[35msilly^[[39m: fritzdect.0 (22085) Objects system redis pmessage system.config/cfg.o.system.config:{"_id":"system.config","type":"config","common":{"name":{"en":"System configuration","de":"Syst> 2025-03-18 22:41:21.840 - ^[[32minfo^[[39m: host.raspi5 instance system.adapter.zigbee.0 in version "1.10.14" started with pid 56000 2025-03-18 22:41:23.450 - ^[[32minfo^[[39m: zigbee.0 (56000) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-03-18 22:41:23.487 - ^[[32minfo^[[39m: zigbee.0 (56000) delete old Backup files. keep only last 10 2025-03-18 22:41:23.489 - ^[[32minfo^[[39m: zigbee.0 (56000) Starting Zigbee npm ... 2025-03-18 22:41:23.624 - ^[[32minfo^[[39m: zigbee.0 (56000) Installed Version: iobroker.zigbee@1.10.14 2025-03-18 22:43:55.876 - ^[[34mdebug^[[39m: fritzdect.0 (22085) polling! fritzdect is alive with 300 s 2025-03-18 22:43:55.876 - ^[[34mdebug^[[39m: fritzdect.0 (22085) __________________________ -
@nilli Da ist etwas systematisch auf Deinem System nicht in Ordnung. Bist du sicher das du die 5 Minuten gewartet hast bevor Du das Log geladen hast ? Im Log selber ist davon wenig zu sehen.
Ansonsten bitte :
- Zigbee-Adapter deinstallieren
- sicherstellen das im NPM baum sowohl der zigbee-herdsman als auch die zigbee-herdsman-converters nicht mehr vorhanden sind
- dann den Zigbee Adapter neu installieren
- Dann den Zigbee-Adapter starten (so wie oben) und das Log posten.
A.
-
@asgothian said in Zigbee.0: You need save and run adapter before pairing!:
sicherstellen das im NPM baum sowohl der zigbee-herdsman als auch die zigbee-herdsman-converters nicht mehr vorhanden sind
Danke für die Hilfe ! Wie überprüfe ich das ?
-
@asgothian said in Zigbee.0: You need save and run adapter before pairing!:
sicherstellen das im NPM baum sowohl der zigbee-herdsman als auch die zigbee-herdsman-converters nicht mehr vorhanden sind
Danke für die Hilfe ! Wie überprüfe ich das ?
@nilli Im ioBroker Verzeichnis:
npm list -a | grep -e zigbeedarf keine Ausgabe liefern.Du kannst vor der de-installation verifizieren das der Befehl funktioniert - er müsste etwas ähnliches wie dieses liefern:
iobroker.zigbee@2.0.4 /Users/ae/LocalDocuments/GitHub/ioBroker.zigbee ├─┬ zigbee-herdsman-converters@23.6.0 │ └── zigbee-herdsman@3.3.2 deduped └─┬ zigbee-herdsman@3.3.2Wichtig - das ist von meinem Entwicklungssystem, Versionsnummern und Pfade werden bei Dir anders sein.
A.
-
@nilli Im ioBroker Verzeichnis:
npm list -a | grep -e zigbeedarf keine Ausgabe liefern.Du kannst vor der de-installation verifizieren das der Befehl funktioniert - er müsste etwas ähnliches wie dieses liefern:
iobroker.zigbee@2.0.4 /Users/ae/LocalDocuments/GitHub/ioBroker.zigbee ├─┬ zigbee-herdsman-converters@23.6.0 │ └── zigbee-herdsman@3.3.2 deduped └─┬ zigbee-herdsman@3.3.2Wichtig - das ist von meinem Entwicklungssystem, Versionsnummern und Pfade werden bei Dir anders sein.
A.
nils@raspi5:/opt/iobroker $ npm list -a | grep -e zigbee └─┬ iobroker.zigbee@1.10.14 ├─┬ zigbee-herdsman-converters@20.58.0 │ └── zigbee-herdsman@2.1.9 deduped └─┬ zigbee-herdsman@2.1.9Adapter deinstalliert
Inhalt von Ordner /opt/iobroker/iobroker-data/zigbee_0 gelöschtnils@raspi5:/opt/iobroker $ npm list -a | grep -e zigbee nils@raspi5:/opt/iobroker $Adapter neu instaliert und konfiguruert mit :
/dev/ttyUSB0
Typ : TI Z-Stack/CCxxxx
Baud : 115200
Erweiterte PAN ID: abcdabcdabcdabcd
Pan ID : 6754
Kanal 11
Transportschlüssel : 01030507090B0D0F00020406080A0C0DLeider immer noch das gleiche Verhalten :anguished:
Merkwürdig : Ordner /opt/iobroker/iobroker-data/zigbee_0 weiterhin leer ... :thinking_face:
2025-03-19 10:23:59.374 - debug: fritzdect.0 (22085) With 087610147624got the following to parse{"devicestats":{"voltage":"","power":"","energy":""}} 2025-03-19 10:27:53.294 - info: host.raspi5 iobroker del zigbee 2025-03-19 10:27:54.886 - info: host.raspi5 iobroker Delete adapter "zigbee" 2025-03-19 10:27:54.895 - info: host.raspi5 iobroker host.raspi5 Counted 1 instances of zigbee 2025-03-19 10:27:54.911 - info: host.raspi5 iobroker host.raspi5 Counted 1 meta of zigbee 2025-03-19 10:27:54.913 - info: host.raspi5 iobroker host.raspi5 Counted 1 adapter for zigbee 2025-03-19 10:27:54.921 - info: host.raspi5 iobroker host.raspi5 Counted 2 channels of zigbee 2025-03-19 10:27:54.925 - info: host.raspi5 iobroker host.raspi5 Counted 8 states of zigbee 2025-03-19 10:27:54.929 - info: host.raspi5 iobroker host.raspi5 Counted 15 states of system.adapter.zigbee 2025-03-19 10:27:54.932 - info: host.raspi5 iobroker host.raspi5 Counted 8 states (io.zigbee.*) from states 2025-03-19 10:27:54.937 - info: host.raspi5 iobroker host.raspi5 Counted 16 states (system.adapter.zigbee.*) from states 2025-03-19 10:27:55.225 - info: host.raspi5 iobroker host.raspi5 Counted 1 objects of zigbee 2025-03-19 10:27:56.805 - info: host.raspi5 iobroker host.raspi5 file zigbee.admin deleted 2025-03-19 10:27:56.808 - info: host.raspi5 iobroker host.raspi5 object zigbee deleted 2025-03-19 10:27:56.812 - info: host.raspi5 iobroker host.raspi5 object zigbee.admin deletedhost.raspi5 Deleting 30 object(s). 2025-03-19 10:27:56.867 - info: host.raspi5 object deleted system.adapter.zigbee.0 2025-03-19 10:27:56.867 - info: host.raspi5 stopInstance system.adapter.zigbee.0 (force=false, process=true) 2025-03-19 10:27:56.870 - info: zigbee.0 (82664) Got terminate signal TERMINATE_YOURSELF 2025-03-19 10:27:56.869 - info: host.raspi5 iobroker host.raspi5 Deleting 24 state(s). 2025-03-19 10:27:56.871 - info: zigbee.0 (82664) cleaned everything up... 2025-03-19 10:27:56.872 - info: zigbee.0 (82664) Zigbee: disabling joining new devices. 2025-03-19 10:27:56.873 - warn: zigbee.0 (82664) Failed to stop zigbee during startup 2025-03-19 10:27:56.873 - info: zigbee.0 (82664) terminating 2025-03-19 10:27:56.874 - info: zigbee.0 (82664) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-03-19 10:27:56.912 - info: host.raspi5 stopInstance system.adapter.zigbee.0 send kill signal 2025-03-19 10:27:57.371 - info: zigbee.0 (82664) terminating 2025-03-19 10:27:57.405 - info: host.raspi5 instance system.adapter.zigbee.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2025-03-19 10:27:57.405 - info: host.raspi5 Do not restart adapter system.adapter.zigbee.0 because desired by instance 2025-03-19 10:28:01.292 - info: host.raspi5 iobroker 2025-03-19 10:28:01.293 - info: host.raspi5 iobroker removed 22 packages in 4s200 packages are looking for funding run `npm fund` for details 2025-03-19 10:28:02.320 - info: host.raspi5 iobroker exit 0 2025-03-19 10:28:55.926 - debug: fritzdect.0 (22085) polling! fritzdect is alive with 300 s 2025-03-19 10:28:59.038 - debug: fritzdect.0 (22085) With 087610147624got the following to parse{"devicestats":{"voltage":"","power":"","energy":""}} 2025-03-19 10:29:29.781 - info: host.raspi5 iobroker add zigbee --host raspi5 2025-03-19 10:29:31.948 - info: host.raspi5 iobroker NPM version: 10.8.2 2025-03-19 10:29:31.950 - info: host.raspi5 iobroker Installing iobroker.zigbee@1.10.14... (System call) 2025-03-19 10:29:49.217 - info: host.raspi5 iobroker 2025-03-19 10:29:49.217 - info: host.raspi5 iobroker added 22 packages in 17s202 packages are looking for funding run `npm fund` for details 2025-03-19 10:29:49.278 - info: host.raspi5 iobroker host.raspi5 install adapter zigbee 2025-03-19 10:29:49.444 - info: host.raspi5 iobroker upload [333] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/adapter-settings.js adapter-settings.js application/javascript 2025-03-19 10:29:51.617 - info: host.raspi5 iobroker upload [300] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/Eurotronic_Spirit_04.png img/Eurotronic_Spirit_04.png image/png 2025-03-19 10:29:52.013 - info: host.raspi5 iobroker upload [250] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/cc2538_router_v1.png img/cc2538_router_v1.png image/png 2025-03-19 10:29:52.535 - info: host.raspi5 iobroker upload [200] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/hue-smart-button.png img/hue-smart-button.png image/png 2025-03-19 10:29:52.938 - info: host.raspi5 iobroker upload [150] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/lifecontrol_lamp.png img/lifecontrol_lamp.png image/png 2025-03-19 10:29:53.361 - info: host.raspi5 iobroker upload [100] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_fuzo_outdoor_wall_light.png img/philips_fuzo_outdoor_wall_light.png image/png 2025-03-19 10:29:53.424 - info: host.raspi5 iobroker upload [90] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_argenta_4.png img/philips_hue_argenta_4.png image/png 2025-03-19 10:29:53.452 - info: host.raspi5 iobroker upload [80] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_gu10_ambiance.png img/philips_hue_gu10_ambiance.png image/png 2025-03-19 10:29:53.487 - info: host.raspi5 iobroker upload [70] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_lwv001.png img/philips_hue_lwv001.png image/png 2025-03-19 10:29:53.515 - info: host.raspi5 iobroker upload [60] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/previous_track.png img/previous_track.png image/png 2025-03-19 10:29:53.542 - info: host.raspi5 iobroker upload [50] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/sensor_philipshue.png img/sensor_philipshue.png image/png 2025-03-19 10:29:53.570 - info: host.raspi5 iobroker upload [40] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/smartthings_motion.png img/smartthings_motion.png image/png 2025-03-19 10:29:53.602 - info: host.raspi5 iobroker upload [30] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/ts0203.png img/ts0203.png image/png 2025-03-19 10:29:53.811 - info: host.raspi5 iobroker upload [20] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/tuya_tyzs1l.png img/tuya_tyzs1l.png image/png 2025-03-19 10:29:53.818 - info: host.raspi5 iobroker upload [19] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/unavailable.png img/unavailable.png image/png 2025-03-19 10:29:53.825 - info: host.raspi5 iobroker upload [18] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/unknown.png img/unknown.png image/png 2025-03-19 10:29:53.832 - info: host.raspi5 iobroker upload [17] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/wemo.png img/wemo.png image/png 2025-03-19 10:29:53.839 - info: host.raspi5 iobroker upload [16] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/xiaomi_plug_eu.png img/xiaomi_plug_eu.png image/png 2025-03-19 10:29:53.846 - info: host.raspi5 iobroker upload [15] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/xiaomi_wireless_switch.png img/xiaomi_wireless_switch.png image/png 2025-03-19 10:29:53.857 - info: host.raspi5 iobroker upload [14] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_e27.png img/zbt_e27.png image/png 2025-03-19 10:29:53.863 - info: host.raspi5 iobroker upload [13] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_e27_rgbw.png img/zbt_e27_rgbw.png image/png 2025-03-19 10:29:53.869 - info: host.raspi5 iobroker upload [12] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_led_panel.png img/zbt_led_panel.png image/png 2025-03-19 10:29:53.875 - info: host.raspi5 iobroker upload [11] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_smart_switch.png img/zbt_smart_switch.png image/png 2025-03-19 10:29:53.882 - info: host.raspi5 iobroker upload [10] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zemismart_sw2.png img/zemismart_sw2.png image/png 2025-03-19 10:29:53.888 - info: host.raspi5 iobroker upload [9] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/index.html index.html text/html 2025-03-19 10:29:53.900 - info: host.raspi5 iobroker upload [8] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/index_m.html index_m.html text/html 2025-03-19 10:29:53.913 - info: host.raspi5 iobroker upload [7] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/moment.min.js moment.min.js application/javascript 2025-03-19 10:29:53.924 - info: host.raspi5 iobroker upload [6] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/shuffle.min.js shuffle.min.js application/javascript 2025-03-19 10:29:53.934 - info: host.raspi5 iobroker upload [5] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/tab_m.html tab_m.html text/html 2025-03-19 10:29:53.946 - info: host.raspi5 iobroker upload [4] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/vis-network.min.css vis-network.min.css text/css 2025-03-19 10:29:53.960 - info: host.raspi5 iobroker upload [3] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/vis-network.min.js vis-network.min.js application/javascript 2025-03-19 10:29:53.979 - info: host.raspi5 iobroker upload [2] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/words.js words.js application/javascript 2025-03-19 10:29:53.992 - info: host.raspi5 iobroker upload [1] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/zigbee.png zigbee.png image/png 2025-03-19 10:29:54.000 - info: host.raspi5 iobroker upload [0] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/zigbee.svg zigbee.svg image/svg+xml 2025-03-19 10:29:54.038 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee created/updated 2025-03-19 10:29:54.039 - info: host.raspi5 iobroker Updating objects from io-package.json for adapter "zigbee" with version "1.10.14" 2025-03-19 10:29:54.067 - info: host.raspi5 iobroker host.raspi5 create instance zigbee 2025-03-19 10:29:54.071 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.alive created 2025-03-19 10:29:54.074 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.connected created 2025-03-19 10:29:54.077 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.compactMode created 2025-03-19 10:29:54.080 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.cpu created 2025-03-19 10:29:54.083 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.cputime created 2025-03-19 10:29:54.087 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.memHeapUsed created 2025-03-19 10:29:54.090 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.memHeapTotal created 2025-03-19 10:29:54.093 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.memRss created 2025-03-19 10:29:54.096 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.uptime created 2025-03-19 10:29:54.099 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.inputCount created 2025-03-19 10:29:54.102 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.outputCount created 2025-03-19 10:29:54.105 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.eventLoopLag created 2025-03-19 10:29:54.108 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.sigKill created 2025-03-19 10:29:54.112 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0.logLevel created 2025-03-19 10:29:54.115 - info: host.raspi5 iobroker host.raspi5 object zigbee.0.exclude created 2025-03-19 10:29:54.118 - info: host.raspi5 iobroker host.raspi5 object zigbee.0.exclude.all created 2025-03-19 10:29:54.120 - info: host.raspi5 iobroker host.raspi5 object zigbee.0.info created 2025-03-19 10:29:54.123 - info: host.raspi5 iobroker host.raspi5 object zigbee.0.info.connection created 2025-03-19 10:29:54.126 - info: host.raspi5 iobroker host.raspi5 object zigbee.0.info.pairingMode created 2025-03-19 10:29:54.129 - info: host.raspi5 iobroker host.raspi5 object zigbee.0.info.pairingCountdown created 2025-03-19 10:29:54.133 - info: host.raspi5 iobroker host.raspi5 object zigbee.0.info.pairingMessage created 2025-03-19 10:29:54.136 - info: host.raspi5 iobroker host.raspi5 object zigbee.0.info.groups created 2025-03-19 10:29:54.139 - info: host.raspi5 iobroker host.raspi5 object zigbee.0.info.undefinedDevices created 2025-03-19 10:29:54.143 - info: host.raspi5 iobroker host.raspi5 object zigbee.0.info.debugmessages created 2025-03-19 10:29:54.146 - info: host.raspi5 iobroker host.raspi5 Set default value of zigbee.0.exclude.all: [] 2025-03-19 10:29:54.149 - info: host.raspi5 iobroker host.raspi5 Set default value of zigbee.0.info.connection: false 2025-03-19 10:29:54.152 - info: host.raspi5 iobroker host.raspi5 Set default value of zigbee.0.info.pairingMode: false 2025-03-19 10:29:54.154 - info: host.raspi5 iobroker host.raspi5 Set default value of zigbee.0.info.pairingCountdown: 0 2025-03-19 10:29:54.156 - info: host.raspi5 iobroker host.raspi5 Set default value of zigbee.0.info.pairingMessage: 2025-03-19 10:29:54.159 - info: host.raspi5 iobroker host.raspi5 Set default value of zigbee.0.info.groups: 2025-03-19 10:29:54.161 - info: host.raspi5 iobroker host.raspi5 Set default value of zigbee.0.info.undefinedDevices: 2025-03-19 10:29:54.163 - info: host.raspi5 iobroker host.raspi5 Set default value of zigbee.0.info.debugmessages: 2025-03-19 10:29:54.170 - info: host.raspi5 iobroker host.raspi5 object system.adapter.zigbee.0 created 2025-03-19 10:29:55.180 - info: host.raspi5 iobroker exit 0 2025-03-19 10:29:56.875 - info: admin.0 (21591) ==> Connected system.user.admin from ::ffff:192.168.2.66 2025-03-19 10:29:57.472 - info: host.raspi5 instance system.adapter.zigbee.0 in version "1.10.14" started with pid 83159 2025-03-19 10:30:00.684 - info: zigbee.0 (83159) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-03-19 10:30:00.706 - error: zigbee.0 (83159) Serial port not selected! Go to settings page. 2025-03-19 10:30:00.709 - info: zigbee.0 (83159) Starting Zigbee npm ... 2025-03-19 10:30:01.111 - info: zigbee.0 (83159) Installed Version: iobroker.zigbee@1.10.14 2025-03-19 10:31:32.746 - info: host.raspi5 stopInstance system.adapter.zigbee.0 (force=false, process=true) 2025-03-19 10:31:32.750 - info: zigbee.0 (83159) Got terminate signal TERMINATE_YOURSELF 2025-03-19 10:31:32.751 - info: zigbee.0 (83159) cleaned everything up... 2025-03-19 10:31:32.753 - info: zigbee.0 (83159) Zigbee: disabling joining new devices. 2025-03-19 10:31:32.754 - warn: zigbee.0 (83159) Failed to stop zigbee during startup 2025-03-19 10:31:32.754 - info: zigbee.0 (83159) terminating 2025-03-19 10:31:32.755 - info: zigbee.0 (83159) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-03-19 10:31:32.793 - info: host.raspi5 stopInstance system.adapter.zigbee.0 send kill signal 2025-03-19 10:31:33.252 - info: zigbee.0 (83159) terminating 2025-03-19 10:31:33.285 - info: host.raspi5 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-03-19 10:31:36.506 - info: host.raspi5 instance system.adapter.zigbee.0 in version "1.10.14" started with pid 83248 2025-03-19 10:31:36.575 - info: admin.0 (21591) <== Disconnect system.user.admin from ::ffff:192.168.2.66 2025-03-19 10:31:38.535 - info: zigbee.0 (83248) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-03-19 10:31:38.549 - info: zigbee.0 (83248) Starting Zigbee npm ... 2025-03-19 10:31:38.803 - info: zigbee.0 (83248) Installed Version: iobroker.zigbee@1.10.14 2025-03-19 10:33:55.927 - debug: fritzdect.0 (22085) polling! fritzdect is alive with 300 s 2025-03-19 10:33:55.927 - debug: fritzdect.0 (22085) __________________________ 2025-03-19 10:33:55.927 - debug: fritzdect.0 (22085) updating Devices / Groups 2025-03-19 10:33:56.951 - debug: fritzdect.0 (22085) devices 2025-03-19 10:33:56.951 - debug: fritzdect.0 (22085) update Devices 1 2025-03-19 10:38:56.993 - debug: fritzdect.0 (22085) _____________________________________________ 2025-03-19 10:38:56.993 - debug: fritzdect.0 (22085) updating Device FRITZ!DECT 200 #1 -
Wie kann ich die obigen (doppelten) posts löschen ?
Was mir noch merkwürdig erscheint, ist dass im Instanzeneinstellungsmenue des Zigbee-Adapters ein klick auf den Pfeil hinter dem COM-Anschlussnamen keine Auswahl ergibt. Sollten dort nicht alle verfügbaren Adapter angezeigt werden ?
Irgendwie habe ich das Gefühl das der Anschluss nicht richtig für den Adapter konfiguriert ist.
Kann man sich die Adapterkonfiguration direkt im terminal anschauen ?
-
Wie kann ich die obigen (doppelten) posts löschen ?
Was mir noch merkwürdig erscheint, ist dass im Instanzeneinstellungsmenue des Zigbee-Adapters ein klick auf den Pfeil hinter dem COM-Anschlussnamen keine Auswahl ergibt. Sollten dort nicht alle verfügbaren Adapter angezeigt werden ?
Irgendwie habe ich das Gefühl das der Anschluss nicht richtig für den Adapter konfiguriert ist.
Kann man sich die Adapterkonfiguration direkt im terminal anschauen ?
@nilli Nein. Um da näher dran zu kommen müsstest Du die 2.1.0 RC3 von meinem Github installieren. Anbei ein Link und ein Hinweis in wie weit diese Version besonders ist.
Interessant für Deine Situation ist das du direkt versuchen kannst den Herdsman zu starten und zu stoppen, ohne immer die Ansicht zu wechseln. Relevante Log-Meldunge bekommst du auch direkt in der Oberfläche angezeigt
Wichtig - alle Breaking changes aus dem Wechsel von 1.10 zu 2.0.1 gelten auch (siehe hier)
Link: https://github.com/asgothian/ioBroker.zigbee/tarball/2.1.0
Was hier neu ist:
- der Adatper startet nicht mehr ‘durch’, sprich der Adapter startet das Zigbee-Subsystem nur dann wenn der entsprechende Haken gesetzt ist. Per default ist der nicht gesetzt. (Im Bild rot umrandet)
- der Adapter bietet die Option den Herdsman testweise zu starten, und direkt im Admin die Meldungen des Starts zu sehen. So kann ohne Jongliererei geprüft werden ob die Parameter passen. Im Bild lila umrandet
- Der Knopf zum Reset ist aktuell noch nicht getestet - da bin ich noch dran. Das sollte aber im Laufe der Woche passieren
- Mit Start/Stop kann der Herdsman gestartet / angehalten werden
Das icon mit dem Trauerrand taucht immer dann auf wenn der Herdsman nicht läuft.
Zum testen sollte das ganze ausreichen.
-
Wie kann ich die obigen (doppelten) posts löschen ?
Was mir noch merkwürdig erscheint, ist dass im Instanzeneinstellungsmenue des Zigbee-Adapters ein klick auf den Pfeil hinter dem COM-Anschlussnamen keine Auswahl ergibt. Sollten dort nicht alle verfügbaren Adapter angezeigt werden ?
Irgendwie habe ich das Gefühl das der Anschluss nicht richtig für den Adapter konfiguriert ist.
Kann man sich die Adapterkonfiguration direkt im terminal anschauen ?
@nilli sagte in Zigbee.0: You need save and run adapter before pairing!:
Irgendwie habe ich das Gefühl das der Anschluss nicht richtig für den Adapter konfiguriert ist.
wenn du damit Converter meinst, bin ich schon länger dieser Meinung
-
@nilli sagte in Zigbee.0: You need save and run adapter before pairing!:
Irgendwie habe ich das Gefühl das der Anschluss nicht richtig für den Adapter konfiguriert ist.
wenn du damit Converter meinst, bin ich schon länger dieser Meinung
-
@nilli was sagt denn
lsusbundls /dev/serial/by-id? -
leider genau was es sollte , oder ?
nils@raspi5:/ $ lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 009: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub nils@raspi5:/ $ ls -l /dev/serial/by-id total 0 lrwxrwxrwx 1 root root 13 Mar 19 10:00 usb-SMLIGHT_SMLIGHT_SLZB-07p7_9c66d41ef372ed1189a81df3fdf7b791-if00-port0 -> ../../ttyUSB0 -
leider genau was es sollte , oder ?
nils@raspi5:/ $ lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 009: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub nils@raspi5:/ $ ls -l /dev/serial/by-id total 0 lrwxrwxrwx 1 root root 13 Mar 19 10:00 usb-SMLIGHT_SMLIGHT_SLZB-07p7_9c66d41ef372ed1189a81df3fdf7b791-if00-port0 -> ../../ttyUSB0@nilli sagte in Zigbee.0: You need save and run adapter before pairing!:
oder
was steht denn hier
ist leider abgeschnitten
-
@nilli sagte in Zigbee.0: You need save and run adapter before pairing!:
oder
was steht denn hier
ist leider abgeschnitten
Support us
668
Online32.5k
Benutzer81.6k
Themen1.3m
Beiträge