NEWS
Zigbee Adapter Wechsel Conbee 2
-
Trag schon mal
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00als Gerätelink im Adapter ein
erledigt:+1:
Achso,weiß nicht ob es möglicherweise zusammen hängen kann... habe seit einigen Tagen einen Restart Loop im Systeminfo Adapter.
systeminfo.0 2022-04-24 20:43:58.623 warn Terminated (UNCAUGHT_EXCEPTION): Without reason systeminfo.0 2022-04-24 20:43:58.621 info terminating systeminfo.0 2022-04-24 20:43:58.087 error Cannot read property 'getObjectList' of undefined systeminfo.0 2022-04-24 20:43:58.085 error TypeError: Cannot read property 'getObjectList' of undefined at Function.initAdapter (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:44:55) at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:118:37) at Adapter.emit (events.js:314:20) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8226:26 systeminfo.0 2022-04-24 20:43:58.082 error unhandled promise rejection: Cannot read property 'getObjectList' of undefined systeminfo.0 2022-04-24 20:43:58.081 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(). systeminfo.0 2022-04-24 20:43:58.039 info starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.systeminfo, node: v12.22.10, js-controller: 4.0.21 -
erledigt:+1:
Achso,weiß nicht ob es möglicherweise zusammen hängen kann... habe seit einigen Tagen einen Restart Loop im Systeminfo Adapter.
systeminfo.0 2022-04-24 20:43:58.623 warn Terminated (UNCAUGHT_EXCEPTION): Without reason systeminfo.0 2022-04-24 20:43:58.621 info terminating systeminfo.0 2022-04-24 20:43:58.087 error Cannot read property 'getObjectList' of undefined systeminfo.0 2022-04-24 20:43:58.085 error TypeError: Cannot read property 'getObjectList' of undefined at Function.initAdapter (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:44:55) at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js:118:37) at Adapter.emit (events.js:314:20) at /opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:8226:26 systeminfo.0 2022-04-24 20:43:58.082 error unhandled promise rejection: Cannot read property 'getObjectList' of undefined systeminfo.0 2022-04-24 20:43:58.081 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(). systeminfo.0 2022-04-24 20:43:58.039 info starting. Version 0.3.1 in /opt/iobroker/node_modules/iobroker.systeminfo, node: v12.22.10, js-controller: 4.0.21@dunadanlk
Nein.
Aber bring deine node-Installation auf Version 14. -
Moin zusammen. Wollte aus mehreren Gründen vom Deconz Adapter zum Zigbee Adapter wechseln. Habe bisher jetzt nicht so viele Zigbee Geräte sodass ich dachte, geht ja wohl recht fix. Jedoch habe ich mehrere Probleme... Die Zigbee instanz wird gar nicht erst grün... Sprich: Verbunden mit Gerät oder Dienst bleibt rot. In den Adaptereinstellungen ist /dev/ttyACM0 eingetragen und auf Conbee gewechselt. Beim Pairingversuch: You need to setup serial port and start the adapter before pairing! und "Error: Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/ttyACM0'". undefined"
Über Putty und SSH wird der Stick gefunden ( und lief vorher ja auch über Deconz) als Bus 001 Device 003: ID 1cf1:0030 Dresden Elektronik und als ID: lrwxrwxrwx 1 root root 13 Apr 24 14:17 usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00 -> ../../ttyACM0
Über den IOB log erhalte ich:
zigbee.02022-04-24 20:14:02.738 error Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/ttyACM0' zigbee.02022-04-24 20:14:02.738 error Error: Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/ttyACM0' at SerialPort.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28) at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14) at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12 zigbee.02022-04-24 20:14:02.737 error unhandled promise rejection: Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/ttyACM0' zigbee.02022-04-24 20:14:02.736 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). zigbee.02022-04-24 20:13:43.084 error Error herdsman start zigbee.02022-04-24 20:13:43.083 error Failed to start Zigbee zigbee.02022-04-24 20:13:43.082 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/ttyACM0'"Und: die Host gibt mir nach einiger Zeit den Hinweis: Restart loop detected 2022-04-24 20:14:03.445
Und ich komme nicht weiter xD Jetzt bin ich weder nennenswert Linux bewandert, noch habe ich andere Kenntnisse die hilfreich wären. Am einfachsten wäre wohl wieder zurück zum Deconz zu wechseln. Aber wurmen tut es mich doch xD Übersehe ich etwas? Habe sowohl gegooglet als auch hier gesucht^^... Dort angegebenene Lösungswege haben noch keinen Erfolg gebracht.
Grüße in die Runde
-
Bitte mach das folgende:
- zigbee adapter anhalten
- log löschen
- zigbee adapter starten
- 30 sekunden warten
- alle Log Meldungen des Zigbee Adapters als text posten.
A.
@asgothian 2022-04-24 21:12:32.005 - info: host.raspberrypi "system.adapter.zigbee.0" enabled
2022-04-24 21:12:32.152 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 10827
2022-04-24 21:12:35.646 - info: zigbee.0 (10827) starting. Version 1.6.16 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.1, js-controller: 4.0.21
2022-04-24 21:12:35.756 - info: zigbee.0 (10827) Starting Zigbee npm ...
2022-04-24 21:12:36.391 - error: zigbee.0 (10827) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00'"
2022-04-24 21:12:36.392 - error: zigbee.0 (10827) Failed to start Zigbee
2022-04-24 21:12:36.393 - error: zigbee.0 (10827) Error herdsman start
2022-04-24 21:12:36.396 - info: zigbee.0 (10827) Installed Version: iobroker.zigbee@1.6.16
2022-04-24 21:12:46.396 - info: zigbee.0 (10827) Try to reconnect. 1 attempts left
2022-04-24 21:12:46.397 - info: zigbee.0 (10827) Starting Zigbee npm ...
2022-04-24 21:12:46.419 - info: zigbee.0 (10827) Installed Version: iobroker.zigbee@1.6.16
2022-04-24 21:12:46.652 - error: zigbee.0 (10827) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00'"
2022-04-24 21:12:46.653 - error: zigbee.0 (10827) Failed to start Zigbee
2022-04-24 21:12:46.654 - error: zigbee.0 (10827) Error herdsman start
2022-04-24 21:13:06.266 - error: zigbee.0 (10827) 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().
2022-04-24 21:13:06.267 - error: zigbee.0 (10827) unhandled promise rejection: Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00'
2022-04-24 21:13:06.268 - error: zigbee.0 (10827) Error: Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00'
at SerialPort. (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
2022-04-24 21:13:06.268 - error: zigbee.0 (10827) Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00'
2022-04-24 21:13:06.283 - info: zigbee.0 (10827) cleaned everything up...
2022-04-24 21:13:06.286 - info: zigbee.0 (10827) Zigbee: disabling joining new devices.
2022-04-24 21:13:06.290 - info: zigbee.0 (10827) terminating
2022-04-24 21:13:06.292 - warn: zigbee.0 (10827) Terminated (UNCAUGHT_EXCEPTION): Without reason -
@asgothian 2022-04-24 21:12:32.005 - info: host.raspberrypi "system.adapter.zigbee.0" enabled
2022-04-24 21:12:32.152 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 10827
2022-04-24 21:12:35.646 - info: zigbee.0 (10827) starting. Version 1.6.16 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.1, js-controller: 4.0.21
2022-04-24 21:12:35.756 - info: zigbee.0 (10827) Starting Zigbee npm ...
2022-04-24 21:12:36.391 - error: zigbee.0 (10827) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00'"
2022-04-24 21:12:36.392 - error: zigbee.0 (10827) Failed to start Zigbee
2022-04-24 21:12:36.393 - error: zigbee.0 (10827) Error herdsman start
2022-04-24 21:12:36.396 - info: zigbee.0 (10827) Installed Version: iobroker.zigbee@1.6.16
2022-04-24 21:12:46.396 - info: zigbee.0 (10827) Try to reconnect. 1 attempts left
2022-04-24 21:12:46.397 - info: zigbee.0 (10827) Starting Zigbee npm ...
2022-04-24 21:12:46.419 - info: zigbee.0 (10827) Installed Version: iobroker.zigbee@1.6.16
2022-04-24 21:12:46.652 - error: zigbee.0 (10827) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00'"
2022-04-24 21:12:46.653 - error: zigbee.0 (10827) Failed to start Zigbee
2022-04-24 21:12:46.654 - error: zigbee.0 (10827) Error herdsman start
2022-04-24 21:13:06.266 - error: zigbee.0 (10827) 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().
2022-04-24 21:13:06.267 - error: zigbee.0 (10827) unhandled promise rejection: Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00'
2022-04-24 21:13:06.268 - error: zigbee.0 (10827) Error: Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00'
at SerialPort. (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28)
at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)
at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12
2022-04-24 21:13:06.268 - error: zigbee.0 (10827) Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2451654-if00'
2022-04-24 21:13:06.283 - info: zigbee.0 (10827) cleaned everything up...
2022-04-24 21:13:06.286 - info: zigbee.0 (10827) Zigbee: disabling joining new devices.
2022-04-24 21:13:06.290 - info: zigbee.0 (10827) terminating
2022-04-24 21:13:06.292 - warn: zigbee.0 (10827) Terminated (UNCAUGHT_EXCEPTION): Without reasonHast du eigentlich deconz zuvor gestoppt oder deinstalliert?
-
Hast du eigentlich deconz zuvor gestoppt oder deinstalliert?
-
@thomas-braun erst nicht... Als es nicht funktionierte habe ich erst zigbee deinstalliert, dann deconz deinstalliert und dann zigbee wieder installiert. Brachte aber keine Veränderung
systemctl status deconz deconz-gui -
systemctl status deconz deconz-gui● deconz.service - deCONZ: ZigBee gateway -- REST API
Loaded: loaded (/lib/systemd/system/deconz.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2022-04-24 14:17:04 CEST; 7h ago
Main PID: 407 (deCONZ)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/deconz.service
└─407 /usr/bin/deCONZ -platform minimal --http-port=80Apr 24 14:17:04 raspberrypi systemd[1]: Started deCONZ: ZigBee gateway -- REST API.
Apr 24 14:17:05 raspberrypi deCONZ[407]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-pi'
Apr 24 14:17:06 raspberrypi deCONZ[407]: libpng warning: iCCP: known incorrect sRGB profile
Apr 24 14:17:07 raspberrypi deCONZ[407]: This plugin does not support propagateSizeHints()
Apr 24 14:17:07 raspberrypi deCONZ[407]: This plugin does not support propagateSizeHints()
Apr 24 14:17:09 raspberrypi deCONZ[407]: This plugin does not support propagateSizeHints()● deconz-gui.service - deCONZ: ZigBee gateway -- GUI/REST API
Loaded: loaded (/lib/systemd/system/deconz-gui.service; disabled; vendor preset: enabled)
Active: inactive (dead)Apr 24 21:30:24 raspberrypi systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitIntervalSec' in section 'Service', ignoring
Apr 24 21:32:52 raspberrypi systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitIntervalSec' in section 'Service', ignoring -
● deconz.service - deCONZ: ZigBee gateway -- REST API
Loaded: loaded (/lib/systemd/system/deconz.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2022-04-24 14:17:04 CEST; 7h ago
Main PID: 407 (deCONZ)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/deconz.service
└─407 /usr/bin/deCONZ -platform minimal --http-port=80Apr 24 14:17:04 raspberrypi systemd[1]: Started deCONZ: ZigBee gateway -- REST API.
Apr 24 14:17:05 raspberrypi deCONZ[407]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-pi'
Apr 24 14:17:06 raspberrypi deCONZ[407]: libpng warning: iCCP: known incorrect sRGB profile
Apr 24 14:17:07 raspberrypi deCONZ[407]: This plugin does not support propagateSizeHints()
Apr 24 14:17:07 raspberrypi deCONZ[407]: This plugin does not support propagateSizeHints()
Apr 24 14:17:09 raspberrypi deCONZ[407]: This plugin does not support propagateSizeHints()● deconz-gui.service - deCONZ: ZigBee gateway -- GUI/REST API
Loaded: loaded (/lib/systemd/system/deconz-gui.service; disabled; vendor preset: enabled)
Active: inactive (dead)Apr 24 21:30:24 raspberrypi systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitIntervalSec' in section 'Service', ignoring
Apr 24 21:32:52 raspberrypi systemd[1]: /lib/systemd/system/deconz-gui.service:10: Unknown lvalue 'StartLimitIntervalSec' in section 'Service', ignoringdeconz läuft noch
sudo systemctl stop deconz sudo systemctl disable deconzBitte setze Konsolenoutput in CodeTags.
-
deconz läuft noch
sudo systemctl stop deconz sudo systemctl disable deconzBitte setze Konsolenoutput in CodeTags.
-
@thomas-braun ....verrückt.. danke... Scheint alles zu funktionieren wie es soll. pairing läuft. also für dummys, der Fehler war letztlich, dass ich Deconz vor dem deinstallieren im IOB hätte... Stoppen müssen? Grüße
Der Service lief noch. Es kann auf ein serielles Gerät immer nur ein Prozess zugreifen.
Support us
721
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge