ZigBee neue Version 1.5.x
-
Funktioniert! Vielen Dank. Nun habe ich gleich mal meine 2 neuen Geräte angelernt!
Vielen vielen Dank!
Mein Issue kann damit zu...
MfG
eMd -
@asgothian sagte in ZigBee neue Version 1.5.x:
https://github.com/asgothian/ioBroker.zigbee/tarball/LatestHerdsman
YES, Kopplung geht wieder. Habs gerade erst drauf, daher keine weiteren Erkenntnisse. Ich berichte morgen weiter (Frau will ins Bett^^).
Dann starte ich morgen auch mit der FB (ZYCT-202)
Danke dir ganz herzlich @Asgothian -
@asgothian sagte in ZigBee neue Version 1.5.x:
@kueppert sagte in ZigBee neue Version 1.5.x:
ZYCT-202
Das kann ich mir nicht mehr anschauen - der Link geht ins leere. Bitte versuch folgendes:
- remote pairen
- die IEEE Addresse der Remote (ohne 0x) in den State zigbee.0.debugmessages eintragen
- knöpfe drücken und schauen ob es Einträge im Log gibt.
A.
and here we go:
Button EInschalten:
zigbee.0 2021-06-08 08:52:01.212 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Stop' zigbee.0 2021-06-08 08:52:01.211 warn ELEVATED publishToState: value generated 'true' from device 00158d0004ff6060 for 'On' zigbee.0 2021-06-08 08:52:01.210 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Off' zigbee.0 2021-06-08 08:52:01.210 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Up' zigbee.0 2021-06-08 08:52:01.209 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Down' zigbee.0 2021-06-08 08:52:01.208 warn ELEVATED publishToState: message received {"action":"on","action_group":24677}' from device 00158d0004ff6060 type 'ZYCT-202' zigbee.0 2021-06-08 08:52:01.206 warn ELEVATED publishToState: value generated '107' from device 00158d0004ff6060 for 'Link quality' zigbee.0 2021-06-08 08:52:01.192 warn ELEVATED publishToState: message received '{"linkquality":107}' from device 00158d0004ff6060 type 'ZYCT-202'Button Ausschalten:
zigbee.0 2021-06-08 08:53:54.677 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Stop' zigbee.0 2021-06-08 08:53:54.676 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'On' zigbee.0 2021-06-08 08:53:54.675 warn ELEVATED publishToState: value generated 'true' from device 00158d0004ff6060 for 'Off' zigbee.0 2021-06-08 08:53:54.674 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Up' zigbee.0 2021-06-08 08:53:54.670 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Down' zigbee.0 2021-06-08 08:53:54.669 warn ELEVATED publishToState: message received '{"action":"off","action_group":24677}' from device 00158d0004ff6060 type 'ZYCT-202' zigbee.0 2021-06-08 08:53:54.665 warn ELEVATED publishToState: value generated '115' from device 00158d0004ff6060 for 'Link quality' zigbee.0 2021-06-08 08:53:54.662 warn ELEVATED publishToState: message received '{"linkquality":115}' from device 00158d0004ff6060 type 'ZYCT-202'Button Hochdimmen:
zigbee.0 2021-06-08 08:54:44.226 warn ELEVATED publishToState: value generated 'true' from device 00158d0004ff6060 for 'Stop' zigbee.0 2021-06-08 08:54:44.226 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'On' zigbee.0 2021-06-08 08:54:44.225 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Off' zigbee.0 2021-06-08 08:54:44.225 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Up' zigbee.0 2021-06-08 08:54:44.225 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Down' zigbee.0 2021-06-08 08:54:44.224 warn ELEVATED publishToState: message received '{"action":"stop","action_group":24677}' from device 00158d0004ff6060 type 'ZYCT-202' zigbee.0 2021-06-08 08:54:44.223 warn ELEVATED publishToState: value generated '115' from device 00158d0004ff6060 for 'Link quality' zigbee.0 2021-06-08 08:54:44.222 warn ELEVATED publishToState: message received '{"linkquality":115}' from device 00158d0004ff6060 type 'ZYCT-202'Button Runterdimmen:
zigbee.0 2021-06-08 08:57:36.945 warn ELEVATED publishToState: value generated 'true' from device 00158d0004ff6060 for 'Stop' zigbee.0 2021-06-08 08:57:36.945 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'On' zigbee.0 2021-06-08 08:57:36.945 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Off' zigbee.0 2021-06-08 08:57:36.944 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Up' zigbee.0 2021-06-08 08:57:36.944 warn ELEVATED publishToState: value generated 'false' from device 00158d0004ff6060 for 'Down' zigbee.0 2021-06-08 08:57:36.944 warn ELEVATED publishToState: message received '{"action":"stop","action_group":24677}' from device 00158d0004ff6060 type 'ZYCT-202' zigbee.0 2021-06-08 08:57:36.942 warn ELEVATED publishToState: value generated '113' from device 00158d0004ff6060 for 'Link quality' zigbee.0 2021-06-08 08:57:36.941 warn ELEVATED publishToState: message received '{"linkquality":113}' from device 00158d0004ff6060 type 'ZYCT-202'Die beiden Lampengruppen-Buttons sind ohne Funktion im LOG/bei den Objekten.
-
@emd sagte in ZigBee neue Version 1.5.x:
Funktioniert! Vielen Dank. Nun habe ich gleich mal meine 2 neuen Geräte angelernt!
Vielen vielen Dank!
Mein Issue kann damit zu...
@kueppert sagte in ZigBee neue Version 1.5.x:
YES, Kopplung geht wieder. Habs gerade erst drauf, daher keine weiteren Erkenntnisse. Ich berichte morgen weiter (Frau will ins Bett^^).
Dann starte ich morgen auch mit der FB (ZYCT-202) Danke dir ganz herzlich @AsgothianVorsicht - die Anpassung wird noch über einige Zeit nicht in den latest Stand übernommen, weil es aktuell noch zu viele gefährliche Anpassungen im Herdsman zu geben scheint.
-
@asgothian @artek
Ich verwende einen Adapter mit CC2530 / CC2592, angeschlossen per USB.
Seit dem Update von 1.5.5 auf 1.5.6 hängt sich der Adapter min. einmal pro Tag auf.
In der Regel ist er in den Instanzen zwar grün, jedoch lassen sich keine Geräte mehr ansprechen. Im Log erscheint die Meldung:zigbee.0 (1764) Send command to 0x000... failed with no error code (SRSP - AF - dataRequest after 6000ms)
Hin und wieder funktioniert es wieder, wenn ich den iobroker neu starte ( iobroker stop und start ), in der Regel muß ich den Raspi aber komplett neu booten.
Wie kann ich denn auf Version 1.5.5. downgraden? Im Expertenmodus bekomme ich nur die 1.5.0 als Option.
-
@gosund geh auf 1.4.1 und dann wieder auf 1.5.6
-
@arteck
Danke für die schnelle Antwort. Muß ich danach wieder alle Gerät neu pairen?
Und wie mache ich das Downgrade am besten? Konsole oder Expertenmodus? -
@gosund nein musst du nicht.. und nimm den expertenmodus
-
@artek
Ok, ganz so einfach hat es dann doch nicht geklappt. Schlußendlich mußte ich den Adapter komplett löschen über die Konsole, dann die 1.4.1 installiert, danach das Update auf die 1.5.6 und dann das ZigBee Backup wieder eingespielt. Zumindest erkennt er jetzt wieder alle Geräte, jedoch fehlen bei den Objekten wieder die Rolle und Funktion.
Kann ich das irgendwie auch sichern und wiederherstellen? Ist ziemlich mühsam bei 16+ Geräten alles wieder von Hand einzufügen...Ob es etwas gebracht hat sehe ich wohl in den kommenden 24 Stunden.
-
@gosund hättest den Adapter nicht löschen müssen.. zumindest nicht aus der GUI raus
hintenrum hätte auch gereicht und dir blieben alle Objekte erhalten
-
@arteck
Zu früh gefreut. Der 1.5.6 Adapter kommt nicht mehr hoch:zigbee.0
2021-06-09 16:15:12.631 info Try to reconnect. 1 attempts left
zigbee.0
2021-06-09 16:15:02.627 error Error herdsman start
zigbee.0
2021-06-09 16:15:02.626 error Failed to start Zigbee
zigbee.0
2021-06-09 16:15:02.624 error Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"
zigbee.0
2021-06-09 16:14:43.017 info Installed Version: iobroker.zigbee@1.5.6
zigbee.0
2021-06-09 16:14:42.721 info Starting Zigbee npm ...
zigbee.0
2021-06-09 16:14:42.627 info starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.12
zigbee.0
2021-06-09 16:14:37.116 error Cannot read property 'getEntries' of null
zigbee.0
2021-06-09 16:14:37.115 error TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:220:55) at Function.all (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:240:16) at Controller.getDevices (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:303:31) at ZigbeeController.getClients (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:228:49) at DeviceAvailability.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceAvailability.js:222:43) at ZigbeeController.callExtensionMethod (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:214:42) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:385:20) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:696:41) at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:97:5)
zigbee.0
2021-06-09 16:14:37.113 error unhandled promise rejection: Cannot read property 'getEntries' of null
zigbee.0
2021-06-09 16:14:37.112 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). -
@artek
Was hat es eigentlich mit der PAN Id nach dem Update auf sich?
Ich hatte diese unverändert auf 6754. Nach den ersten Problemen mit der 1.5.6 und dem Einspielen des Backups behauptete der Adapter im Log, die PAN wäre 6755. Nachdem ich umgestellt hatte, ging es -zumindest für ein paar Stunden.
Nach der neuerlichen Aktion mit Downgrade auf 1.4.1 und jetzt wieder Update auf 1.5.6 behauptet der Adapter, die PAN Id wäre ist die 6756 -
@gosund
Hast du zufällig die verschiedenen nvbackup.json Dateien von den Versionen, in denen erkennbar ist das die panID hochgezählt wird ? Ich gehe davon aus das da etwas in der Konfiguration im Herdsman passiert - Wir brauchen dafür aber die Möglichkeit das nachzustellen.Ich kann verstehen wenn Du das mit deinem "live" Zigbee Netz nicht tun willst. In diesem Fall müsstest Du erst einmal auf die 1.4.1 zurück gehen. Ich hoffe immer noch darauf eine zigbee-herdsman version zu finden die
- mit der 1.5.6 läuft
- das Problem nicht hat.
Sobald ich da etwas gefunden habe werde ich einen Link zur Testinstallation bereitstellen.
A.
-
@asgothian
Nach Stromausfall kommt zigbee nicht mehr hoch:zigbee.0 2021-06-09 19:29:22.325 warn (3443) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l zigbee.0 2021-06-09 19:29:22.311 error (3443) Cannot read property 'getEntries' of null zigbee.0 2021-06-09 19:29:22.310 error (3443) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct zigbee.0 2021-06-09 19:29:22.306 error (3443) unhandled promise rejection: Cannot read property 'getEntries' of null zigbee.0 2021-06-09 19:29:22.305 error (3443) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-06-09 19:29:22.304 warn (3443) Terminated (UNCAUGHT_EXCEPTION): Without reason zigbee.0 2021-06-09 19:29:22.302 info (3443) terminating zigbee.0 2021-06-09 19:29:22.300 error (3443) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j zigbee.0 2021-06-09 19:29:22.296 info (3443) Zigbee: disabling joining new devices. zigbee.0 2021-06-09 19:29:22.289 info (3443) cleaned everything up... zigbee.0 2021-06-09 19:29:22.279 error (3443) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' zigbee.0 2021-06-09 19:29:22.278 error (3443) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive zigbee.0 2021-06-09 19:29:22.277 error (3443) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218 zigbee.0 2021-06-09 19:29:22.275 error (3443) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-06-09 19:29:01.519 warn (3443) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false" zigbee.0 2021-06-09 19:29:01.509 error (3443) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive zigbee.0 2021-06-09 19:29:01.508 error (3443) Failed to start Zigbee zigbee.0 2021-06-09 19:29:01.326 info (3443) Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-06-09 19:29:01.283 info (3443) Starting Zigbee npm ... zigbee.0 2021-06-09 19:29:01.281 info (3443) Try to reconnect. 1 attempts left zigbee.0 2021-06-09 19:28:51.283 warn (3443) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false" zigbee.0 2021-06-09 19:28:51.281 error (3443) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive zigbee.0 2021-06-09 19:28:51.279 error (3443) Failed to start Zigbee zigbee.0 2021-06-09 19:28:51.106 info (3443) Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-06-09 19:28:51.101 warn (3443) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false" zigbee.0 2021-06-09 19:28:50.914 info (3443) Starting Zigbee npm ... zigbee.0 2021-06-09 19:28:50.821 info (3443) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11 zigbee.0 2021-06-09 19:28:17.833 warn (3367) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l zigbee.0 2021-06-09 19:28:17.822 error (3367) Cannot read property 'getEntries' of null zigbee.0 2021-06-09 19:28:17.821 error (3367) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct zigbee.0 2021-06-09 19:28:17.817 error (3367) unhandled promise rejection: Cannot read property 'getEntries' of null zigbee.0 2021-06-09 19:28:17.816 error (3367) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-06-09 19:28:17.815 warn (3367) Terminated (UNCAUGHT_EXCEPTION): Without reason zigbee.0 2021-06-09 19:28:17.813 info (3367) terminating zigbee.0 2021-06-09 19:28:17.808 error (3367) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j zigbee.0 2021-06-09 19:28:17.804 info (3367) Zigbee: disabling joining new devices. zigbee.0 2021-06-09 19:28:17.797 info (3367) cleaned everything up... zigbee.0 2021-06-09 19:28:17.783 error (3367) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' zigbee.0 2021-06-09 19:28:17.782 error (3367) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive zigbee.0 2021-06-09 19:28:17.781 error (3367) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218 zigbee.0 2021-06-09 19:28:17.779 error (3367) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-06-09 19:27:57.012 warn (3367) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false" zigbee.0 2021-06-09 19:27:57.008 error (3367) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive zigbee.0 2021-06-09 19:27:57.007 error (3367) Failed to start Zigbee zigbee.0 2021-06-09 19:27:56.797 info (3367) Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-06-09 19:27:56.777 info (3367) Starting Zigbee npm ... zigbee.0 2021-06-09 19:27:56.776 info (3367) Try to reconnect. 1 attempts left zigbee.0 2021-06-09 19:27:46.778 warn (3367) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false" zigbee.0 2021-06-09 19:27:46.775 error (3367) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive zigbee.0 2021-06-09 19:27:46.773 error (3367) Failed to start Zigbee zigbee.0 2021-06-09 19:27:46.630 info (3367) Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-06-09 19:27:46.626 warn (3367) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false" zigbee.0 2021-06-09 19:27:46.394 info (3367) Starting Zigbee npm ... zigbee.0 2021-06-09 19:27:46.294 info (3367) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11 zigbee.0 2021-06-09 19:27:13.360 warn (3289) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l zigbee.0 2021-06-09 19:27:13.349 error (3289) Cannot read property 'getEntries' of null zigbee.0 2021-06-09 19:27:13.348 error (3289) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct zigbee.0 2021-06-09 19:27:13.342 error (3289) unhandled promise rejection: Cannot read property 'getEntries' of null zigbee.0 2021-06-09 19:27:13.341 error (3289) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-06-09 19:27:13.340 warn (3289) Terminated (UNCAUGHT_EXCEPTION): Without reason zigbee.0 2021-06-09 19:27:13.338 info (3289) terminating zigbee.0 2021-06-09 19:27:13.336 error (3289) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j zigbee.0 2021-06-09 19:27:13.332 info (3289) Zigbee: disabling joining new devices. zigbee.0 2021-06-09 19:27:13.326 info (3289) cleaned everything up... -
@ente34 sagte in ZigBee neue Version 1.5.x:
Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'
Entweder fehlt am Anfang des Logs noch einiges oder der Zigbee Stick ist seit dem Stromausfall defekt:
Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'Nebenbei hast du mindestens 2 unterschiedliche Zigbee Versionen in deinem Log.
- Welche version hattest du vor dem Stromausfall aktiv (und am laufen?)
- Warum hast du gedacht das nach einem Stromausfall ein Update / Downgrade des Zigbee Adapters irgend etwas bewirkt ?
A.
-
@asgothian
Habe versuchweise einen Downgrade durchgeführt.
Bin jetzt wieder bei 1.5.6Nach reboot mit deaktiviertem Zigbee und dann nachdem alles hochgelaufen ist zigbee aktiviert:
zigbee.0 2021-06-09 19:41:24.425 warn (1903) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false" zigbee.0 2021-06-09 19:41:24.423 error (1903) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive zigbee.0 2021-06-09 19:41:24.421 error (1903) Failed to start Zigbee zigbee.0 2021-06-09 19:41:24.264 info (1903) Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-06-09 19:41:24.258 warn (1903) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false" zigbee.0 2021-06-09 19:41:24.053 info (1903) Starting Zigbee npm ... zigbee.0 2021-06-09 19:41:23.960 info (1903) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11 host.raspi-iobroker 2021-06-09 19:41:21.617 info instance system.adapter.zigbee.0 started with pid 1903 host.raspi-iobroker 2021-06-09 19:40:51.545 info Restart adapter system.adapter.zigbee.0 because enabled host.raspi-iobroker 2021-06-09 19:40:51.544 error instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) zigbee.0 2021-06-09 19:40:50.950 warn (1827) Read-only state "zigbee.0.info.pairingMessage" has been written without ack-flag with value "Error: Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.l zigbee.0 2021-06-09 19:40:50.939 error (1827) Cannot read property 'getEntries' of null zigbee.0 2021-06-09 19:40:50.938 error (1827) TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/device.js:216:55) at Funct zigbee.0 2021-06-09 19:40:50.931 error (1827) unhandled promise rejection: Cannot read property 'getEntries' of null zigbee.0 2021-06-09 19:40:50.928 error (1827) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-06-09 19:40:50.926 warn (1827) Terminated (UNCAUGHT_EXCEPTION): Without reason zigbee.0 2021-06-09 19:40:50.924 info (1827) terminating zigbee.0 2021-06-09 19:40:50.922 error (1827) Failed to stop zigbee (TypeError: Cannot read property 'getEntries' of null at Function.loadFromDatabaseIfNecessary (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/group.j zigbee.0 2021-06-09 19:40:50.918 info (1827) Zigbee: disabling joining new devices. zigbee.0 2021-06-09 19:40:50.912 info (1827) cleaned everything up... zigbee.0 2021-06-09 19:40:50.901 error (1827) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' zigbee.0 2021-06-09 19:40:50.900 error (1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive zigbee.0 2021-06-09 19:40:50.899 error (1827) unhandled promise rejection: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218 zigbee.0 2021-06-09 19:40:50.897 error (1827) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.0 2021-06-09 19:40:30.083 warn (1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false" zigbee.0 2021-06-09 19:40:30.078 error (1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive zigbee.0 2021-06-09 19:40:30.077 error (1827) Failed to start Zigbee zigbee.0 2021-06-09 19:40:29.922 info (1827) Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-06-09 19:40:29.893 info (1827) Starting Zigbee npm ... zigbee.0 2021-06-09 19:40:29.892 info (1827) Try to reconnect. 1 attempts left zigbee.0 2021-06-09 19:40:19.893 warn (1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false" zigbee.0 2021-06-09 19:40:19.891 error (1827) Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00' at Drive zigbee.0 2021-06-09 19:40:19.890 error (1827) Failed to start Zigbee zigbee.0 2021-06-09 19:40:19.728 info (1827) Installed Version: iobroker.zigbee@1.5.6 zigbee.0 2021-06-09 19:40:19.724 warn (1827) Read-only state "zigbee.0.info.connection" has been written without ack-flag with value "false" zigbee.0 2021-06-09 19:40:19.492 info (1827) Starting Zigbee npm ... zigbee.0 2021-06-09 19:40:19.377 info (1827) starting. Version 1.4.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.1, js-controller: 3.3.11 host.raspi-iobroker 2021-06-09 19:40:16.846 info instance system.adapter.zigbee.0 started with pid 1827 host.raspi-iobroker 2021-06-09 19:40:16.799 info "system.adapter.zigbee.0" enabled -
@ente34 sagte in ZigBee neue Version 1.5.x:
@asgothian
Habe versuchweise einen Downgrade durchgeführt.
Bin jetzt wieder bei 1.5.6
Um dem Problem auf den Grund zu gehen musst du heraus bekommen warum der serielle Port nicht mehr verfügbar ist. Das Log sagt eindeutig das symlink nicht existiert.
Insbesondere bei Stromausfällen / RaspberryPi Abstürzen / Proxxmox Updates die plötzlich einen laufenden Zigbee Adapter zerlegen ist zu 95% ein Problem mit der Verbindung zum Koordinator die Ursache.
A.
Nachtrag: Oh Wunder, auch in diesem Log findet sich bei jedem Startversuch die gleiche Meldung:
Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2218746-if00'Der Stick wird also immer noch nicht erkannt.
-
@asgothian
Habe einen neuen link 'serial1'pi@raspi-iobroker:~ $ ls -l /dev/serial1 lrwxrwxrwx 1 root root 7 Jun 9 19:36 /dev/serial1 -> ttyAMA0 pi@raspi-iobroker:~ $ -
@asgothian
Erst mal vielen Dank für den schnellen Support! -
@asgothian
@artekSchlechte Nachrichten: Das komplette löschen, installieren und neu Anlernen hat nichts gebracht.
Wie die letzten Tage auch hat sich der Adapter wieder innerhalb eines Tages aufgehängt. Ich mußte den Pi wieder komplett rebooten, damit es wieder geht.Hilfe, ich weiß mir absolut nicht mehr zu helfen. Was kann ich noch versuchen?
