Conbee2 mit Zigbee Adapter kein pairing
-
@cynric10 sagte in Conbee2 mit Zigbee Adapter kein pairing:
Wo könnte man hier Logs auslesen?
Loggen für die Instanz auf Debug stellen und im IoBroker log schauen ob da etwas kommt.
Vielleicht gibt es auch logs vom/auf dem Stick, weiß ich aber nicht.
-
Danke dir !
Ja hab auch schon was rausbekommen .. und scheint so als ob er auf den Port nicht zugreifen kann, wobei den Stick erkennt er ja?
Kann es an Berechtigungen für den Debian User liegen?
2022-02-07 20:03:51.370 - error: zigbee.0 (425) 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-02-07 20:03:51.370 - error: zigbee.0 (425) 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_DE2149798-if00' 2022-02-07 20:03:51.371 - error: zigbee.0 (425) 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_DE2149798-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-02-07 20:03:51.371 - error: zigbee.0 (425) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149798-if00' 2022-02-07 20:03:51.374 - info: zigbee.0 (425) cleaned everything up... 2022-02-07 20:03:51.375 - info: zigbee.0 (425) Zigbee: disabling joining new devices. 2022-02-07 20:03:51.376 - info: zigbee.0 (425) terminating 2022-02-07 20:03:51.377 - warn: zigbee.0 (425) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-02-07 20:03:51.841 - info: host.ioBroker instance system.adapter.sonos.0 started with pid 907 2022-02-07 20:03:51.921 - error: host.ioBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2022-02-07 20:03:51.926 - error: host.ioBroker Caught by controller[1]: 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_DE2149798-if00' 2022-02-07 20:03:51.926 - error: host.ioBroker Caught by controller[1]: at SerialPort. (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28) 2022-02-07 20:03:51.926 - error: host.ioBroker Caught by controller[1]: at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14) 2022-02-07 20:03:51.926 - error: host.ioBroker Caught by controller[1]: at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12 2022-02-07 20:03:51.926 - error: host.ioBroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-02-07 20:03:51.926 - info: host.ioBroker Restart adapter system.adapter.zigbee.0 because enabled 2022-02-07 20:03:52.344 - info: sonos.0 (907) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.sonos, node: v14.19.0, js-controller: 3.3.22 2022-02-07 20:03:58.223 - info: wled.0 (877) WLED initialisation finalized, ready to do my job have fun ! 2022-02-07 20:04:21.935 - info: host.ioBroker instance system.adapter.zigbee.0 started with pid 922 2022-02-07 20:04:22.829 - info: zigbee.0 (922) starting. Version 1.6.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.0, js-controller: 3.3.22 2022-02-07 20:04:22.859 - info: zigbee.0 (922) Starting Zigbee npm ... 2022-02-07 20:04:23.047 - info: zigbee.0 (922) Installed Version: iobroker.zigbee@1.6.6 2022-02-07 20:04:23.077 - error: zigbee.0 (922) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149798-if00'" 2022-02-07 20:04:23.077 - error: zigbee.0 (922) Failed to start Zigbee 2022-02-07 20:04:23.077 - error: zigbee.0 (922) Error herdsman start 2022-02-07 20:04:33.079 - info: zigbee.0 (922) Try to reconnect. 1 attempts left 2022-02-07 20:04:33.079 - info: zigbee.0 (922) Starting Zigbee npm ... 2022-02-07 20:04:33.083 - info: zigbee.0 (922) Installed Version: iobroker.zigbee@1.6.6 2022-02-07 20:04:33.141 - error: zigbee.0 (922) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149798-if00'" 2022-02-07 20:04:33.141 - error: zigbee.0 (922) Failed to start Zigbee 2022-02-07 20:04:33.141 - error: zigbee.0 (922) Error herdsman start 2022-02-07 20:04:53.058 - error: zigbee.0 (922) 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-02-07 20:04:53.058 - error: zigbee.0 (922) 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_DE2149798-if00' 2022-02-07 20:04:53.058 - error: zigbee.0 (922) 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_DE2149798-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-02-07 20:04:53.058 - error: zigbee.0 (922) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149798-if00' 2022-02-07 20:04:53.063 - info: zigbee.0 (922) cleaned everything up... 2022-02-07 20:04:53.064 - info: zigbee.0 (922) Zigbee: disabling joining new devices. 2022-02-07 20:04:53.066 - info: zigbee.0 (922) terminating 2022-02-07 20:04:53.066 - warn: zigbee.0 (922) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-02-07 20:04:53.588 - error: host.ioBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2022-02-07 20:04:53.588 - error: host.ioBroker Caught by controller[1]: 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_DE2149798-if00' 2022-02-07 20:04:53.588 - error: host.ioBroker Caught by controller[1]: at SerialPort. (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28) 2022-02-07 20:04:53.588 - error: host.ioBroker Caught by controller[1]: at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14) 2022-02-07 20:04:53.588 - error: host.ioBroker Caught by controller[1]: at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12 2022-02-07 20:04:53.589 - error: host.ioBroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-02-07 20:04:53.589 - info: host.ioBroker Restart adapter system.adapter.zigbee.0 because enabled 2022-02-07 20:05:23.595 - info: host.ioBroker instance system.adapter.zigbee.0 started with pid 939 2022-02-07 20:05:24.472 - info: zigbee.0 (939) starting. Version 1.6.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.0, js-controller: 3.3.22 2022-02-07 20:05:24.501 - info: zigbee.0 (939) Starting Zigbee npm ... 2022-02-07 20:05:24.715 - error: zigbee.0 (939) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149798-if00'" 2022-02-07 20:05:24.715 - error: zigbee.0 (939) Failed to start Zigbee 2022-02-07 20:05:24.715 - error: zigbee.0 (939) Error herdsman start 2022-02-07 20:05:24.716 - info: zigbee.0 (939) Installed Version: iobroker.zigbee@1.6.6 2022-02-07 20:05:34.716 - info: zigbee.0 (939) Try to reconnect. 1 attempts left 2022-02-07 20:05:34.716 - info: zigbee.0 (939) Starting Zigbee npm ... 2022-02-07 20:05:34.721 - info: zigbee.0 (939) Installed Version: iobroker.zigbee@1.6.6 2022-02-07 20:05:34.776 - error: zigbee.0 (939) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149798-if00'" 2022-02-07 20:05:34.776 - error: zigbee.0 (939) Failed to start Zigbee 2022-02-07 20:05:34.777 - error: zigbee.0 (939) Error herdsman start 2022-02-07 20:05:54.686 - error: zigbee.0 (939) 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-02-07 20:05:54.686 - error: zigbee.0 (939) 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_DE2149798-if00' 2022-02-07 20:05:54.687 - error: zigbee.0 (939) 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_DE2149798-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-02-07 20:05:54.687 - error: zigbee.0 (939) Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149798-if00' 2022-02-07 20:05:54.691 - info: zigbee.0 (939) cleaned everything up... 2022-02-07 20:05:54.692 - info: zigbee.0 (939) Zigbee: disabling joining new devices. 2022-02-07 20:05:54.693 - info: zigbee.0 (939) terminating 2022-02-07 20:05:54.693 - warn: zigbee.0 (939) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-02-07 20:05:55.212 - error: host.ioBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2022-02-07 20:05:55.213 - error: host.ioBroker Caught by controller[1]: 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_DE2149798-if00' 2022-02-07 20:05:55.213 - error: host.ioBroker Caught by controller[1]: at SerialPort. (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:182:28) 2022-02-07 20:05:55.213 - error: host.ioBroker Caught by controller[1]: at SerialPort._error (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14) 2022-02-07 20:05:55.213 - error: host.ioBroker Caught by controller[1]: at /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12 2022-02-07 20:05:55.213 - error: host.ioBroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2022-02-07 20:05:55.213 - info: host.ioBroker Restart adapter system.adapter.zigbee.0 because enabled 2022-02-07 20:05:55.213 - warn: host.ioBroker Do not restart adapter system.adapter.zigbee.0 because restart loop detected -
@cynric10
Ist der Conbee direkt am Server angeschlossen? -
@fortune95 Ja direkt am Server, keine USB Verlängerung.
-
@cynric10
Bei mir hat es nur mit einer Verlängerung funktioniert, versuch mal mit einer. -
@fortune95 Ich habe hier auch Probleme mit der Phoscon/Deconz App das es manchmal funktioniert und manchmal einfach nicht..
Schließe ich den Stick direkt an meinen Win10 PC an, läuft der Stick ohne Probleme und konstant.
-
@cynric10
Wie sehen die Einstellungen im Adapter aus? -
@cynric10 probiere trotzdem mal noch eine USB Verlängerung. Bei mir wollte der Stick auch nicht direkt am NUC. Gleiche Symptome, mal gings, mal nicht. USB Verlängerung dran, dann war Ruhe.
-
Gibt es das Device mit diesem Namen denn?
/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149798-if00 -
ls -la /dev/serial/by-id ?
-
@fortune95 ja
-
@Cynric10 wie schon geschrieben wurde Stick an eine USB Verlängerung, ein Stückweit weg positionieren und an einem USB 2.0 Port. Dann sollte es laufen.
Es ist ein bekanntes Problem das der Stick direkt am Gerät Probleme macht. -
Das sind die Settings im Adapter:
Das bekomm ich raus:
ls -la /dev/serial/by-id insgesamt 0 drwxr-xr-x 2 root root 60 7. Feb 22:03 . drwxr-xr-x 4 root root 80 7. Feb 22:03 .. lrwxrwxrwx 1 root root 13 7. Feb 22:03 usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2149798-if00 -> ../../ttyACM0 -
@jey-cee USB 2.0 habe ich leider an diesem Server nicht..
Aber werde es mal mit 2.0 Verlängerung generell probieren.
Danke
-
@cynric10 Dann liegt es entweder an der Sache mit dem Kabel, oder an den Rechten.
Da müsstest du mal schauen ob der iob user auf das Device zugreifen darf.
Hast du mal geschaut ob die Instanz oder etwas anderes läuft das eventuell auch den Port belegen könnte?
-
@fortune95 habe jetzt die VM mal neu gestartet jetzt sieht es etwas anders aus...
zigbee.0 2022-02-07 22:06:26.906 info Zigbee started zigbee.0 2022-02-07 22:06:26.905 info Currently no devices. zigbee.0 2022-02-07 22:06:26.905 info Unable to set transmit power, unsupported function. zigbee.0 2022-02-07 22:06:26.887 info --> transmitPower : normal zigbee.0 2022-02-07 22:06:26.859 info Unable to disable LED, unsupported function. zigbee.0 2022-02-07 22:06:26.838 info Coordinator firmware version: {"type":"ConBee2/RaspBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":114,"maintrel":0,"revision":"0x26720700"}} zigbee.0 2022-02-07 22:06:26.823 info Installed Version: iobroker.zigbee@1.6.6 zigbee.0 2022-02-07 22:06:26.627 info Starting Zigbee npm ... zigbee.0 2022-02-07 22:06:26.598 info starting. Version 1.6.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.0, js-controller: 3.3.22 host.ioBroker 2022-02-07 22:06:25.719 info instance system.adapter.zigbee.0 started with pid 973 host.ioBroker 2022-02-07 22:06:23.481 info instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zigbee.0 2022-02-07 22:06:22.923 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2022-02-07 22:06:22.922 info terminating host.ioBroker 2022-02-07 22:06:22.709 info stopInstance system.adapter.zigbee.0 send kill signal zigbee.0 2022-02-07 22:06:22.695 info Zigbee: disabling joining new devices. zigbee.0 2022-02-07 22:06:22.695 info cleaned everything up... zigbee.0 2022-02-07 22:06:22.694 info Got terminate signal TERMINATE_YOURSELF -
@cynric10
Hab den den Stick auch an USB 3.0 aber mit Verlängerung.
Anderen Kanal mal versucht? -
Es ging gerade für 2 pair Versuche. Da hat zumindest der Timer runtergezählt.
Das Aquara Sensor den ich pairen wollte schien zwar nicht auf, aber wie gesagt der Timer lief zumindest mal los.
Jetzt habe ich mal channel auf 20 geändert und tut sich wieder nichts. Wieder zurück auf 25 und wieder nichts...
Ich denke immer mehr das es an dieser Verlängerung liegen könnte .... Ich hab mal 1m bei Amazon bestellt, würde das reichen?
-
Wenn ich pairen möchte, sehe ich für ca. 5min nur das ..
Bleibe ich eben nach ca. 5min immer noch in der Session bekomme ich das zu sehen:
rattert auch extrem schnell runter das ganze... und sieht irgendwann dann auch so aus:
-
Nachdem ich mir jetzt auch eine Verlängerung geholt habe, läuft seit zwei Tagen alles ohne Probleme. Bin doch bei der Phoscon App geblieben, weil alles so gut läuft momentan.
Danke für eure Hilfe!
