NEWS
Zigbee mal wieder kaputt
Error/Bug
17
Beiträge
6
Kommentatoren
1.8k
Aufrufe
6
Watching
-
ok hier nochgmal:
zigbee.0 2022-04-23 09:47:35.471 silly States user redis pmessage zigbee.0.*/zigbee.0.info.connection:{"val":false,"ack":true,"ts":1650700055469,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651377248} zigbee.0 2022-04-23 09:47:35.471 silly States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Error: Starting zigbee-herdsman problem : \"Error while opening serialport 'Error: Error: Inappropriate ioctl for device setting custom baud rate of 115200'\". undefined","ack":true,"ts":1650700055469,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651553035} zigbee.0 2022-04-23 09:47:35.465 error Error herdsman start zigbee.0 2022-04-23 09:47:35.465 error Failed to start Zigbee zigbee.0 2022-04-23 09:47:35.465 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Inappropriate ioctl for device setting custom baud rate of 115200'" zigbee.0 2022-04-23 09:47:35.374 info Installed Version: iobroker.zigbee@1.6.18 zigbee.0 2022-04-23 09:47:35.366 debug Starting zigbee-herdsman... zigbee.0 2022-04-23 09:47:35.366 info Starting Zigbee npm ... zigbee.0 2022-04-23 09:47:35.365 info Try to reconnect. 1 attempts left zigbee.0 2022-04-23 09:47:25.396 silly States user redis pmessage zigbee.0.*/zigbee.0.info.connection:{"val":false,"ack":true,"ts":1650700045378,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651377248} zigbee.0 2022-04-23 09:47:25.396 silly States user redis pmessage zigbee.0.*/zigbee.0.info.pairingMessage:{"val":"Error: Starting zigbee-herdsman problem : \"Error while opening serialport 'Error: Error: Inappropriate ioctl for device setting custom baud rate of 115200'\". undefined","ack":true,"ts":1650700045377,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651553035} zigbee.0 2022-04-23 09:47:25.377 silly States user redis pmessage zigbee.0.*/zigbee.0.info.connection:{"val":false,"ack":true,"ts":1650700045373,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651377248} zigbee.0 2022-04-23 09:47:25.375 debug Backup /opt/iobroker/iobroker-data/zigbee_0/backup_2022_04_23-09_47_25.tar.gz success zigbee.0 2022-04-23 09:47:25.365 error Error herdsman start zigbee.0 2022-04-23 09:47:25.365 error Failed to start Zigbee zigbee.0 2022-04-23 09:47:25.364 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Inappropriate ioctl for device setting custom baud rate of 115200'" zigbee.0 2022-04-23 09:47:25.332 info Installed Version: iobroker.zigbee@1.6.18 zigbee.0 2022-04-23 09:47:25.292 silly States system redis pmessage system.adapter.zigbee.0.logLevel/system.adapter.zigbee.0.logLevel:{"val":"silly","ack":true,"ts":1650700045210,"q":0,"from":"system.adapter.zigbee.0","lc":1650651674279} zigbee.0 2022-04-23 09:47:25.152 debug Starting zigbee-herdsman... zigbee.0 2022-04-23 09:47:25.152 info Starting Zigbee npm ... zigbee.0 2022-04-23 09:47:25.134 debug Using zigbee-herdsman with settings: {"network":{"panID":6754,"channelList":[11],"networkKey":[x],"extenedPanID":[x]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_0/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_0/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/ttyACM0","adapter":"zstack"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false}} zigbee.0 2022-04-23 09:47:25.120 info starting. Version 1.6.18 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.1, js-controller: 4.0.23 zigbee.0 2022-04-23 09:47:25.003 debug Plugin sentry Initialize Plugin (enabled=true) zigbee.0 2022-04-23 09:47:24.949 silly statesDB connected zigbee.0 2022-04-23 09:47:24.949 debug States connected to redis: 127.0.0.1:9000 zigbee.0 2022-04-23 09:47:24.939 debug States create User PubSub Client zigbee.0 2022-04-23 09:47:24.938 debug States create System PubSub Client zigbee.0 2022-04-23 09:47:24.932 debug Redis States: Use Redis connection: 127.0.0.1:9000 zigbee.0 2022-04-23 09:47:24.931 silly objectDB connected zigbee.0 2022-04-23 09:47:24.929 silly redis psubscribe cfg.o.enum.* zigbee.0 2022-04-23 09:47:24.920 silly redis psubscribe cfg.o.system.user.* zigbee.0 2022-04-23 09:47:24.919 debug Objects connected to redis: 127.0.0.1:9001 zigbee.0 2022-04-23 09:47:24.917 debug Objects client initialize lua scripts zigbee.0 2022-04-23 09:47:24.900 debug Objects create User PubSub Client zigbee.0 2022-04-23 09:47:24.900 debug Objects create System PubSub Client zigbee.0 2022-04-23 09:47:24.899 debug Objects client ready ... initialize now zigbee.0 2022-04-23 09:47:24.878 debug Redis Objects: Use Redis connection: 127.0.0.1:9001 host.iobroker 2022-04-23 09:47:24.050 info instance system.adapter.zigbee.0 started with pid 46805 host.iobroker 2022-04-23 09:47:21.631 info instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) zigbee.0 2022-04-23 09:47:21.170 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d0005816448.link_quality:{"val":0,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471794} zigbee.0 2022-04-23 09:47:21.169 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d0005816448.available:{"val":false,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.169 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d000577ed85.link_quality:{"val":0,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.167 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d000577ed85.available:{"val":false,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.165 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d000581710d.link_quality:{"val":0,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.165 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d000581710d.available:{"val":false,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.165 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d0006954782.link_quality:{"val":0,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.156 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d0006954782.available:{"val":false,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.156 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d0006b36df2.link_quality:{"val":0,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.155 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d0006b36df2.available:{"val":false,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.154 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d0006b3f166.link_quality:{"val":0,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.153 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d0006b3f166.available:{"val":false,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.153 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d000400e524.link_quality:{"val":0,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471739} zigbee.0 2022-04-23 09:47:21.151 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d000400e524.available:{"val":false,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471697} zigbee.0 2022-04-23 09:47:21.146 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d000400c2e0.link_quality:{"val":0,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471695} zigbee.0 2022-04-23 09:47:21.141 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d000400c2e0.available:{"val":false,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471695} zigbee.0 2022-04-23 09:47:21.140 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d000416c1e5.link_quality:{"val":0,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471695} zigbee.0 2022-04-23 09:47:21.139 silly States user redis pmessage zigbee.0.*/zigbee.0.00158d000416c1e5.available:{"val":false,"ack":true,"ts":1650700041137,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651471694} zigbee.0 2022-04-23 09:47:21.128 silly States user redis pmessage zigbee.0.*/zigbee.0.info.undefinedDevices:{"val":"{}","ack":true,"ts":1650700041107,"q":0,"from":"system.adapter.zigbee.0","user":"system.user.admin","lc":1650651435076} zigbee.0 2022-04-23 09:47:21.091 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2022-04-23 09:47:21.090 debug Plugin sentry destroyed zigbee.0 2022-04-23 09:47:21.090 info terminating zigbee.0 2022-04-23 09:47:21.088 warn Failed to stop zigbee during startup zigbee.0 2022-04-23 09:47:21.039 info Zigbee: disabling joining new devices. zigbee.0 2022-04-23 09:47:21.037 debug onDeviceStatusUpdate: 00158d0005816448: false zigbee.0 2022-04-23 09:47:21.036 debug DeviceAvailability:Publish LQ for 0x00158d0005816448 = 0 zigbee.0 2022-04-23 09:47:21.036 debug onDeviceStatusUpdate: 00158d000577ed85: false zigbee.0 2022-04-23 09:47:21.035 debug DeviceAvailability:Publish LQ for 0x00158d000577ed85 = 0 zigbee.0 2022-04-23 09:47:21.036 debug DeviceAvailability:Publish available for 0x00158d0005816448 = false zigbee.0 2022-04-23 09:47:21.034 debug DeviceAvailability:Publish available for 0x00158d000577ed85 = false zigbee.0 2022-04-23 09:47:21.034 debug onDeviceStatusUpdate: 00158d000581710d: false zigbee.0 2022-04-23 09:47:21.033 debug DeviceAvailability:Publish available for 0x00158d000581710d = false zigbee.0 2022-04-23 09:47:21.033 debug onDeviceStatusUpdate: 00158d0006954782: false zigbee.0 2022-04-23 09:47:21.033 debug DeviceAvailability:Publish LQ for 0x00158d000581710d = 0 zigbee.0 2022-04-23 09:47:21.032 debug DeviceAvailability:Publish LQ for 0x00158d0006954782 = 0 zigbee.0 2022-04-23 09:47:21.031 debug DeviceAvailability:Publish available for 0x00158d0006954782 = false zigbee.0 2022-04-23 09:47:21.031 debug onDeviceStatusUpdate: 00158d0006b36df2: false zigbee.0 2022-04-23 09:47:21.030 debug DeviceAvailability:Publish LQ for 0x00158d0006b36df2 = 0 zigbee.0 2022-04-23 09:47:21.030 debug DeviceAvailability:Publish available for 0x00158d0006b36df2 = false zigbee.0 2022-04-23 09:47:21.030 debug onDeviceStatusUpdate: 00158d0006b3f166: false zigbee.0 2022-04-23 09:47:21.029 debug DeviceAvailability:Publish LQ for 0x00158d0006b3f166 = 0 zigbee.0 2022-04-23 09:47:21.028 debug DeviceAvailability:Publish available for 0x00158d0006b3f166 = false zigbee.0 2022-04-23 09:47:21.028 debug onDeviceStatusUpdate: 00158d000400e524: false zigbee.0 2022-04-23 09:47:21.027 debug DeviceAvailability:Publish LQ for 0x00158d000400e524 = 0 zigbee.0 2022-04-23 09:47:21.026 debug DeviceAvailability:Publish available for 0x00158d000400e524 = false zigbee.0 2022-04-23 09:47:21.026 debug onDeviceStatusUpdate: 00158d000400c2e0: false zigbee.0 2022-04-23 09:47:21.025 debug DeviceAvailability:Publish LQ for 0x00158d000400c2e0 = 0 zigbee.0 2022-04-23 09:47:21.023 debug DeviceAvailability:Publish available for 0x00158d000400c2e0 = false zigbee.0 2022-04-23 09:47:21.022 debug onDeviceStatusUpdate: 00158d000416c1e5: false zigbee.0 2022-04-23 09:47:21.019 debug DeviceAvailability:Publish LQ for 0x00158d000416c1e5 = 0 zigbee.0 2022-04-23 09:47:21.016 debug DeviceAvailability:Publish available for 0x00158d000416c1e5 = false zigbee.0 2022-04-23 09:47:21.014 info cleaned everything up... host.iobroker 2022-04-23 09:47:21.015 info stopInstance system.adapter.zigbee.0 send kill signal zigbee.0 2022-04-23 09:47:21.014 silly States system redis pmessage system.adapter.zigbee.0.sigKill/system.adapter.zigbee.0.sigKill:{"val":-1,"ack":false,"ts":1650700041013,"q":0,"from":"system.host.iobroker","lc":1650700041013} zigbee.0 2022-04-23 09:47:21.014 info Got terminate signal TERMINATE_YOURSELFIOB läuft auf einem Proxmox Container
ls -l /dev/ttyACM0 -------rw- 1 root root 0 Apr 22 19:53 /dev/ttyACM0Gut, Container also...
Auf einem nativen System schaut das jedenfalls so aus:ls -l /dev/ttyAMA0 crw-rw---- 1 root dialout 204, 64 Apr 23 01:04 /dev/ttyAMA0Mein zigbee-Stick wird aber auch woanders (nämlich /dev/ttyUSB0) eingehängt:
ls -la /dev/serial/by-id/ total 0 drwxr-xr-x 2 root root 60 Apr 23 01:04 . drwxr-xr-x 4 root root 80 Apr 23 01:04 .. lrwxrwxrwx 1 root root 13 Apr 23 01:04 usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_23_93_2C_A8-if00-port0 -> ../../ttyUSB0ls -l /dev/ttyUSB0 crw-rw---- 1 root dialout 188, 0 Apr 23 09:25 /dev/ttyUSB0 -
Ich weiß jetzt nicht warum, es geht jedoch wieder.
lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0451:16c8 Texas Instruments, Inc. Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ls -l /dev/ttyACM0 crw-rw---- 1 root dialout 166, 0 Apr 23 10:21 /dev/ttyACM0habe gestern 100te mal neu gestartet und nichts ist passiert. Eben nochmal neu gestartet und er findet ihn wieder
-
Ich weiß jetzt nicht warum, es geht jedoch wieder.
lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0451:16c8 Texas Instruments, Inc. Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ls -l /dev/ttyACM0 crw-rw---- 1 root dialout 166, 0 Apr 23 10:21 /dev/ttyACM0habe gestern 100te mal neu gestartet und nichts ist passiert. Eben nochmal neu gestartet und er findet ihn wieder
Dann stell den Link aus /dev/serial/by-id ein. Der ist robuster bei Neustarts.
-
gibts nicht
ls -la /dev/serial/by-id/ ls: cannot access '/dev/serial/by-id/': No such file or directoryGut, liegt vielleicht an dem Container-Gedöns.
Ich weiß schon, warum ich das nicht verwende. -
gibts nicht
ls -la /dev/serial/by-id/ ls: cannot access '/dev/serial/by-id/': No such file or directory -
gibts nicht
ls -la /dev/serial/by-id/ ls: cannot access '/dev/serial/by-id/': No such file or directory@mpl1338 sagte in Zigbee mal wieder kaputt:
ls -la /dev/serial/by-id/
Normal geht der Befehl unter Proxmox!
Hast Du den Stick auch richtig an den Container weitergegeben? Als VM ist das wesendlich entspannter!
Schau Dir das mal an : https://coldcorner.de/2018/07/12/proxmox-usb-passthrough-fuer-lxc-container-z-wave-uzb1/ -
ich habe die USB weitergabe nach der von dir geposteten Anleitung vor nem Jahr eingerichtet. Ohne dies ging Garnichts
-
ich hab das Problem, dass die Rechte bei dem Sonoff Zigbee Stick nicht passen.
Wie kann ich dem Stick die nötigen Rechte verpassen?Bei mir sieht das ganze so aus:
proxmox@zigbee2mqtt:/opt/zigbee2mqtt$ ls -la /dev/serial/by-id/ total 0 drwxr-xr-x 2 root root 60 Feb 21 18:54 . drwxr-xr-x 3 root root 60 Feb 21 18:54 .. ---------- 1 root root 0 Feb 21 18:54 usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0aktuell bekomme ich beim start von zigbee den Fehler:
Starting Zigbee2MQTT without watchdog. [2025-02-21 19:03:02] error: z2m: Error while starting zigbee-herdsman [2025-02-21 19:03:02] error: z2m: Failed to start zigbee-herdsman [2025-02-21 19:03:02] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions [2025-02-21 19:03:02] error: z2m: Exiting... [2025-02-21 19:03:02] error: z2m: Error: Error: Inappropriate ioctl for device setting custom baud rate of 115200 ELIFECYCLE Command failed with exit code 1.
Support us
804
Online32.4k
Benutzer81.6k
Themen1.3m
Beiträge