NEWS
Zigbee iobroker Error while opening serialport
-
@arteck besten Dank, das war wohl der Fehler, auch wenn ich nicht verstehe warum das nach Jahren erstmals auftrat und das Teil nie bewegt wurde.
-
Hallo zusammen, auch ich bin verzweifelt den Zigbee adapter mit dem CC1352p-2 coordinator zum laufen zu bringen.
Hier mal einiges was ich so gemacht hab. Ich hoffe jemand kann mir Helfen. DankePS: ioBroker läuft auf ein LXC in Proxmox
2022-12-07 18:50:59.448 - info: backitup.0 (385) [iobroker] backup was activated at 02:40 every 1 day(s) 2022-12-07 18:56:16.554 - info: admin.0 (343) ==> Connected system.user.admin from ::ffff:192.168.178.68 2022-12-07 18:59:17.572 - info: host.ioBroker "system.adapter.zigbee.0" enabled 2022-12-07 18:59:17.587 - info: host.ioBroker instance system.adapter.zigbee.0 started with pid 416 2022-12-07 18:59:18.664 - info: zigbee.0 (416) starting. Version 1.7.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v16.18.1, js-controller: 4.0.23 2022-12-07 18:59:18.704 - info: zigbee.0 (416) Starting Zigbee npm ... 2022-12-07 18:59:18.916 - info: zigbee.0 (416) Installed Version: iobroker.zigbee@1.7.6 2022-12-07 18:59:18.953 - error: zigbee.0 (416) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Permission denied, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.15__Embed_with_CMSIS-DAP_L430042O-if00'" 2022-12-07 18:59:18.954 - error: zigbee.0 (416) Failed to start Zigbee 2022-12-07 18:59:18.954 - error: zigbee.0 (416) Error herdsman start 2022-12-07 18:59:21.505 - info: admin.0 (343) ==> Connected system.user.admin from ::ffff:192.168.178.68 2022-12-07 18:59:21.555 - error: zigbee.0 (416) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups') 2022-12-07 18:59:28.956 - info: zigbee.0 (416) Try to reconnect. 1 attempts left 2022-12-07 18:59:28.957 - info: zigbee.0 (416) Starting Zigbee npm ... 2022-12-07 18:59:28.964 - info: zigbee.0 (416) Installed Version: iobroker.zigbee@1.7.6 2022-12-07 18:59:29.047 - error: zigbee.0 (416) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error: Permission denied, cannot open /dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.15__Embed_with_CMSIS-DAP_L430042O-if00'" 2022-12-07 18:59:29.048 - error: zigbee.0 (416) Failed to start Zigbee 2022-12-07 18:59:29.048 - error: zigbee.0 (416) Error herdsman start 2022-12-07 18:59:32.398 - info: admin.0 (343) <== Disconnect system.user.admin from ::ffff:192.168.178.68
root@ioBroker:~# ls -l /dev total 0 crw--w---- 1 root tty 136, 0 Dec 7 18:50 console lrwxrwxrwx 1 root root 11 Dec 7 18:50 core -> /proc/kcore lrwxrwxrwx 1 root root 13 Dec 7 18:50 fd -> /proc/self/fd crw-rw-rw- 1 nobody nogroup 1, 7 Dec 7 12:41 full lrwxrwxrwx 1 root root 12 Dec 7 18:50 initctl -> /run/initctl lrwxrwxrwx 1 root root 28 Dec 7 18:50 log -> /run/systemd/journal/dev-log drwxrwxrwt 2 nobody nogroup 40 Dec 7 18:50 mqueue crw-rw-rw- 1 nobody nogroup 1, 3 Dec 7 12:41 null crw-rw-rw- 1 root root 5, 2 Dec 7 19:20 ptmx drwxr-xr-x 2 root root 0 Dec 7 18:50 pts crw-rw-rw- 1 nobody nogroup 1, 8 Dec 7 12:41 random drwxr-xr-x 3 root root 60 Dec 7 18:50 serial drwxrwxrwt 2 root root 40 Dec 7 18:50 shm lrwxrwxrwx 1 root root 15 Dec 7 18:50 stderr -> /proc/self/fd/2 lrwxrwxrwx 1 root root 15 Dec 7 18:50 stdin -> /proc/self/fd/0 lrwxrwxrwx 1 root root 15 Dec 7 18:50 stdout -> /proc/self/fd/1 crw-rw-rw- 1 nobody nogroup 5, 0 Dec 7 12:41 tty crw------- 1 root tty 136, 1 Dec 7 19:20 tty1 crw--w---- 1 root tty 136, 2 Dec 7 18:50 tty2 crw-rw-rw- 1 nobody nogroup 166, 0 Dec 7 12:41 ttyACM0 crw-rw-rw- 1 nobody nogroup 188, 0 Dec 7 12:41 ttyUSB0 crw-rw-rw- 1 nobody nogroup 1, 9 Dec 7 12:41 urandom crw-rw-rw- 1 nobody nogroup 1, 5 Dec 7 12:41 zero
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0451:bef3 Texas Instruments, Inc. CC1352R1 Launchpad Bus 001 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@Intel:~# ls /dev/serial/by-id/ usb-FTDI_FT232R_USB_UART_A90782OJ-if00-port0 usb-Texas_Instruments_XDS110__03.00.00.15__Embed_with_CMSIS-DAP_L430042O-if00 usb-Texas_Instruments_XDS110__03.00.00.15__Embed_with_CMSIS-DAP_L430042O-if03 root@Intel:~#
root@Intel:~# ls -l /dev/serial/by-id total 0 lrwxrwxrwx 1 root root 13 Dec 7 12:41 usb-FTDI_FT232R_USB_UART_A90782OJ-if00-port0 -> ../../ttyUSB0 lrwxrwxrwx 1 root root 13 Dec 7 12:41 usb-Texas_Instruments_XDS110__03.00.00.15__Embed_with_CMSIS-DAP_L430042O-if00 -> ../../ttyACM0 lrwxrwxrwx 1 root root 13 Dec 7 12:41 usb-Texas_Instruments_XDS110__03.00.00.15__Embed_with_CMSIS-DAP_L430042O-if03 -> ../../ttyACM1 root@Intel:~#
GNU nano 5.4 100.conf arch: amd64 cores: 2 features: nesting=1 hostname: ioBroker memory: 4096 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=1A:BA:1E:27:F0:F7,ip=dhcp,ip6=dhcp,type=veth ostype: ubuntu rootfs: local-lvm:vm-100-disk-0,size=16G swap: 512 unprivileged: 1 lxc.cgroup2.devices.allow: c 189:* rwm lxc.mount.entry: usb-Texas_Instruments_XDS110__03.00.00.15__Embed_with_CMSIS-DAP_L430042O-if00 dev/serial/by-id/usb-Texas_Instruments_XDS110__03.00.00.15__Embed_with_CMSIS-DAP_L430042O-if00 none bind,optional,create=file lxc.cgroup2.devices.allow: c 166:* rwm lxc.mount.entry: /dev/ttyACM0 dev/ttyACM0 none bind,optional,create=file lxc.cgroup2.devices.allow: c 189:* rwm lxc.mount.entry: usb-FTDI_FT232R_USB_UART_A90782OJ-if00-port0 dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A90782OJ-if00-port0 none bind,optional,create=file lxc.cgroup2.devices.allow: c 188:* rwm lxc.mount.entry: /dev/ttyUSB0 dev/ttyUSB0 none bind,optional,create=file
-
@galli2k Du hast ein Problem damit das die Berechtigungen zum zugriff auf die serielle Schnittstelle nicht ausreicht. Das ist ein Problem des LXC Setups - da musst du suchen.
Mehr kann ich dazu nicht sagen - ich setze das nicht ein.
A
-
@asgothian Falls es jemanden helfen sollte:
Ich hatte vorher beim Anlegen des Lxc im Netzwerk DHCP gewählt.
Nun habe ich einen neuen Container mit einer statische IP angelegt und alles läuft wunderbar. -
@galli2k sagte in Zigbee iobroker Error while opening serialport:
Ich hatte vorher beim Anlegen des Lxc im Netzwerk DHCP gewählt.
da muss noch mehr gewesen sein .. DHCP hat nix mit USB belegun gzu tun.
-
Hallo,
leider muss ich dieses Thema nochmal hervorholen.
Ich habe heute einen Sonoff Zigbee Stick bekommen.
Ich habe ihn in den NUC gesteckt und in Proxmox zur VM iobroker durch gereicht.ls -la /dev/serial/by-id/ ergibt
total 0 drwxr-xr-x 2 root root 80 Nov 7 17:44 . drwxr-xr-x 4 root root 80 Nov 7 17:44 .. lrwxrwxrwx 1 root root 13 Nov 7 17:44 usb-1a86_USB_Serial-if00-port0 -> ../../t tyUSB1 lrwxrwxrwx 1 root root 13 Nov 7 17:44 usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Pl us_c24d83bbb59ded11acdcdba5a7669f5d-if00-port0 -> ../../ttyUSB0
Eingegeben unter COM-Anschluss im Adapter habe ich
/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c24d83bbb59ded11acdcdba5a7669f5d-if00-port0Hier der komplette log
zigbee.0 2023-11-07 19:16:24.684 error Error herdsman start zigbee.0 2023-11-07 19:16:24.684 error Failed to start Zigbee zigbee.0 2023-11-07 19:16:24.684 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" zigbee.0 2023-11-07 19:16:24.604 info Installed Version: iobroker.zigbee@1.8.23 zigbee.0 2023-11-07 19:16:24.596 info Starting Zigbee npm ... zigbee.0 2023-11-07 19:16:24.596 info Try to reconnect. 1 attempts left zigbee.0 2023-11-07 19:16:14.595 error Error herdsman start zigbee.0 2023-11-07 19:16:14.594 error Failed to start Zigbee zigbee.0 2023-11-07 19:16:14.594 error Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information" zigbee.0 2023-11-07 19:16:14.532 error Re-commissioning your network will require re-pairing of all devices! zigbee.0 2023-11-07 19:16:14.532 error If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json. zigbee.0 2023-11-07 19:16:14.532 error Please update configuration to prevent further issues. zigbee.0 2023-11-07 19:16:14.532 error - Channel List: configured=11, adapter=11 zigbee.0 2023-11-07 19:16:14.532 error - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d zigbee.0 2023-11-07 19:16:14.531 error - Extended PAN ID: configured=dfddfddddddddeed, adapter=00124b002b48282c zigbee.0 2023-11-07 19:16:14.531 error - PAN ID: configured=6258, adapter=6258 zigbee.0 2023-11-07 19:16:14.531 error Configuration is not consistent with adapter state/backup! zigbee.0 2023-11-07 19:16:14.261 info Installed Version: iobroker.zigbee@1.8.23 zigbee.0 2023-11-07 19:16:14.159 info Starting Zigbee npm ... zigbee.0 2023-11-07 19:16:14.097 info starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.1, js-controller: 5.0.12 zigbee.0 2023-11-07 19:15:37.122 info terminating zigbee.0 2023-11-07 19:15:36.683 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason zigbee.0 2023-11-07 19:15:36.683 info terminating zigbee.0 2023-11-07 19:15:36.674 warn Failed to stop zigbee during startup zigbee.0 2023-11-07 19:15:36.625 info Zigbee: disabling joining new devices. zigbee.0 2023-11-07 19:15:36.622 info cleaned everything up... zigbee.0 2023-11-07 19:15:36.621 info Got terminate signal TERMINATE_YOURSELF zigbee.0 2023-11-07 19:09:56.448 info List of port: [{"path":"/dev/ttyUSB1","manufacturer":"1a86","pnpId":"usb-1a86_USB_Serial-if00-port0","vendorId":"1a86","productId":"7523"},{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"c24d83bbb59ded11acdcdba5a7669f5d","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c24d83bbb59ded11acdcdba5a7669f5d-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS10"},{"path":"/dev/ttyS11"},{"path":"/dev/ttyS12"},{"path":"/dev/ttyS13"},{"path":"/dev/ttyS14"},{"path":"/dev/ttyS15"},{"path":"/dev/ttyS16"},{"path":"/dev/ttyS17"},{"path":"/dev/ttyS18"},{"path":"/dev/ttyS19"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS20"},{"path":"/dev/ttyS21"},{"path":"/dev/ttyS22"},{"path":"/dev/ttyS23"},{"path":"/dev/ttyS24"},{"path":"/dev/ttyS25"},{"path":"/dev/ttyS26"},{"path":"/dev/ttyS27"},{"path":"/dev/ttyS28"},{"path":"/dev/ttyS29"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS30"},{"path":"/dev/ttyS31"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyS8"},{"path":"/dev/ttyS9"}] zigbee.0 2023-11-07 19:09:56.370 error getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups') zigbee.0 2023-11-07 18:28:27.996 info List of port: [{"path":"/dev/ttyUSB1","manufacturer":"1a86","pnpId":"usb-1a86_USB_Serial-if00-port0","vendorId":"1a86","productId":"7523"},{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"c24d83bbb59ded11acdcdba5a7669f5d","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c24d83bbb59ded11acdcdba5a7669f5d-if00-port0","vendorId":"10c4","productId":"ea60"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS10"},{"path":"/dev/ttyS11"},{"path":"/dev/ttyS12"},{"path":"/dev/ttyS13"},{"path":"/dev/ttyS14"},{"path":"/dev/ttyS15"},{"path":"/dev/ttyS16"},{"path":"/dev/ttyS17"},{"path":"/dev/ttyS18"},{"path":"/dev/ttyS19"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS20"},{"path":"/dev/ttyS21"},{"path":"/dev/ttyS22"},{"path":"/dev/ttyS23"},{"path":"/dev/ttyS24"},{"path":"/dev/ttyS25"},{"path":"/dev/ttyS26"},{"path":"/dev/ttyS27"},{"path":"/dev/ttyS28"},{"path":"/dev/ttyS29"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS30"},{"path":"/dev/ttyS31"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyS8"},{"path":"/dev/ttyS9"}] zigbee.0 2023-11-07 18:28:27.938 error getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups') zigbee.0 2023-11-07 18:26:08.388 error Error herdsman start zigbee.0 2023-11-07 18:26:08.388 error Failed to start Zigbee zigbee.0 2023-11-07 18:26:08.388 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" zigbee.0 2023-11-07 18:26:08.293 info Installed Version: iobroker.zigbee@1.8.23 zigbee.0 2023-11-07 18:26:08.278 info Starting Zigbee npm ... zigbee.0 2023-11-07 18:26:08.277 info Try to reconnect. 1 attempts left zigbee.0 2023-11-07 18:25:58.275 error Error herdsman start zigbee.0 2023-11-07 18:25:58.275 error Failed to start Zigbee zigbee.0 2023-11-07 18:25:58.275 error Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information" zigbee.0 2023-11-07 18:25:58.233 error Re-commissioning your network will require re-pairing of all devices! zigbee.0 2023-11-07 18:25:58.233 error If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json. zigbee.0 2023-11-07 18:25:58.233 error Please update configuration to prevent further issues. zigbee.0 2023-11-07 18:25:58.233 error - Channel List: configured=11, adapter=11 zigbee.0 2023-11-07 18:25:58.232 error - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d zigbee.0 2023-11-07 18:25:58.232 error - Extended PAN ID: configured=dfddfddddddddeed, adapter=00124b002b48282c zigbee.0 2023-11-07 18:25:58.232 error - PAN ID: configured=6258, adapter=6258 zigbee.0 2023-11-07 18:25:58.232 error Configuration is not consistent with adapter state/backup! zigbee.0 2023-11-07 18:25:57.935 info Installed Version: iobroker.zigbee@1.8.23 zigbee.0 2023-11-07 18:25:57.803 info Starting Zigbee npm ... zigbee.0 2023-11-07 18:25:57.758 info starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.1, js-controller: 5.0.12 zigbee.0 2023-11-07 18:25:54.553 info Terminated (NO_ERROR): Without reason zigbee.0 2023-11-07 18:25:54.552 info terminating zigbee.0 2023-11-07 18:25:54.122 error Error herdsman start zigbee.0 2023-11-07 18:25:54.122 error Failed to start Zigbee zigbee.0 2023-11-07 18:25:54.121 error Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information" zigbee.0 2023-11-07 18:25:54.075 error Re-commissioning your network will require re-pairing of all devices! zigbee.0 2023-11-07 18:25:54.075 error If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json. zigbee.0 2023-11-07 18:25:54.075 error Please update configuration to prevent further issues. zigbee.0 2023-11-07 18:25:54.074 error - Channel List: configured=11, adapter=11 zigbee.0 2023-11-07 18:25:54.074 error - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d zigbee.0 2023-11-07 18:25:54.074 error - Extended PAN ID: configured=dfddfddddddddeed, adapter=00124b002b48282c zigbee.0 2023-11-07 18:25:54.074 error - PAN ID: configured=6258, adapter=6258 zigbee.0 2023-11-07 18:25:54.074 error Configuration is not consistent with adapter state/backup! zigbee.0 2023-11-07 18:25:54.052 info Zigbee: disabling joining new devices. zigbee.0 2023-11-07 18:25:54.049 info cleaned everything up... zigbee.0 2023-11-07 18:25:53.725 info Installed Version: iobroker.zigbee@1.8.23 zigbee.0 2023-11-07 18:25:53.628 info Starting Zigbee npm ... zigbee.0 2023-11-07 18:25:53.582 info starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.1, js-controller: 5.0.12 zigbee.0 2023-11-07 18:25:21.806 info terminating zigbee.0 2023-11-07 18:25:21.336 warn Terminated (UNCAUGHT_EXCEPTION): Without reason zigbee.0 2023-11-07 18:25:21.335 info terminating zigbee.0 2023-11-07 18:25:21.335 warn Failed to stop zigbee during startup zigbee.0 2023-11-07 18:25:21.309 info Zigbee: disabling joining new devices. zigbee.0 2023-11-07 18:25:21.306 info cleaned everything up... zigbee.0 2023-11-07 18:25:21.299 error Cannot read properties of undefined (reading 'getClients') zigbee.0 2023-11-07 19:16:24.684 error Error herdsman start zigbee.0 2023-11-07 19:16:24.684 error Failed to start Zigbee zigbee.0 2023-11-07 19:16:24.684 error Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" zigbee.0 2023-11-07 19:16:24.604 info Installed Version: iobroker.zigbee@1.8.23 zigbee.0 2023-11-07 19:16:24.596 info Starting Zigbee npm ... zigbee.0 2023-11-07 19:16:24.596 info Try to reconnect. 1 attempts left zigbee.0 2023-11-07 19:16:14.595 error Error herdsman start zigbee.0 2023-11-07 19:16:14.594 error Failed to start Zigbee zigbee.0 2023-11-07 19:16:14.594 error Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information" zigbee.0 2023-11-07 19:16:14.532 error Re-commissioning your network will require re-pairing of all devices! zigbee.0 2023-11-07 19:16:14.532 error If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json. zigbee.0 2023-11-07 19:16:14.532 error Please update configuration to prevent further issues. zigbee.0 2023-11-07 19:16:14.532 error - Channel List: configured=11, adapter=11 zigbee.0 2023-11-07 19:16:14.532 error - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d zigbee.0 2023-11-07 19:16:14.531 error - Extended PAN ID: configured=dfddfddddddddeed, adapter=00124b002b48282c zigbee.0 2023-11-07 19:16:14.531 error - PAN ID: configured=6258, adapter=6258 zigbee.0 2023-11-07 19:16:14.531 error Configuration is not consistent with adapter state/backup! zigbee.0 2023-11-07 19:16:14.261 info Installed Version: iobroker.zigbee@1.8.23 zigbee.0 2023-11-07 19:16:14.159 info Starting Zigbee npm ... zigbee.0 2023-11-07 19:16:14.097 info starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.1, js-controller: 5.0.12
Wenn ich es richtig verstanden habe, stimmt etwas nicht mit dem Adapterstatus/Backup überein.
Ich habe allerdings keine Ahnung was und auch nicht wo ich etwas ändern kann.
Ich würde mich freuen, wenn einem unwissenden etwas unter die Arme gegriffen werden könnte.
Vielen Dank und VG
-
Extended PAN ID: configured=dfddfddddddddeed, adapter=00124b002b48282c
Die Werte müssen übereinstimmen.
-
@thomas-braun sagte in Zigbee iobroker Error while opening serialport:
00124b002b48282c
Super, vielen Dank. Ich habe mich nicht getraut das einzutragen, jetzt habe ich es einfach rein kopiert und siehe da funktioniert.
Nochmal vielen Dank
-
Hallo, ich hänge mich hier mal rein. Mein Zigbee will auch einfach nicht laufen, habe schon einiges ausprobiert was hier so geschrieben wurde, leider ohne Erfolg. Ich hoffe ihr könnt mir helfen. Wie ihr wisst, bin ich ein absoluter Anfänger, wenn möglich für ganz ganz doofe erklären.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Nov 3 17:54:35 2023 from 192.168.178.45 pi@raspberrypi:~ $ ls -la /dev/serial/by-id/ insgesamt 0 drwxr-xr-x 2 root root 60 Nov 13 14:01 . drwxr-xr-x 4 root root 80 Nov 13 14:01 .. lrwxrwxrwx 1 root root 13 Nov 13 14:01 usb-Texas_Instruments_TI_CC2531_USB_CDC__
-
Der Geräte-Link ist ja auch offensichtlich falsch.
In den Einstellungen muss/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC__
eingetragen werden. Wobei mir der Dateiname auch irgendwie abgeschnitten aussieht.
-
Wenn ich das als code eingebe wird der Eintrag beschnitten.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Nov 3 17:54:35 2023 from 192.168.178.45
pi@raspberrypi:~ $ ls -la /dev/serial/by-id/
insgesamt 0
drwxr-xr-x 2 root root 60 Nov 13 14:01 .
drwxr-xr-x 4 root root 80 Nov 13 14:01 ..
lrwxrwxrwx 1 root root 13 Nov 13 14:01 usb-Texas_Instruments_TI_CC2531_USB_CDC__ _0X00124B001CDD4A3A-if00 -> ../../ttyACM0 -
@tiobb sagte in Zigbee iobroker Error while opening serialport:
usb-Texas_Instruments_TI_CC2531_USB_CDC__ _0X00124B001CDD4A3A-if00
Der Eintrag im Adapter muss also
/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CDD4A3A-if00
lauten. Am besten kopieren. Der vollständige Link steht aber als Service auch in der Ausgabe von
iob diag
fertig zum kopieren drin.
-
@thomas-braun sagte in Zigbee iobroker Error while opening serialport:
/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CDD4A3A-if00
Ok danke, jetzt scheint es zu funktionieren, bin der Meinung ich hatte das schon genauso in den Einstellungen stehen, aber wahrscheinlich irre ich mich.
-
@tiobb sagte in Zigbee iobroker Error while opening serialport:
bin der Meinung ich hatte das schon genauso in den Einstellungen stehen
In deinen Screenshots definitiv nicht.
-
@thomas-braun
Ich hatte ja schon einiges probiert, aber egal, jetzt scheint es zu funktionieren, zumindest ist alles grün. Für meine Sensoren und den Bewegungsmelder von Aqara brauche ich erstmal neue Batterien -
Ich hänge mich hier mal an mit meinem Problem:
Versuche auch den Sonoff Zigbee 3.0 USB Dongle Plus am Raspi 4B zum Laufen zu bringen, aber leider ohne Erfolg
Bekomme die Meldung "You need save and run adapter before pairing!"
Als Port habe ich den genauen Pfad angegeben:
dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4d856ba1ab6ed1196ded60ea8669f5d-if00-port0Die erweiterte und die Pan-ID habe ich geändert, schon tausendmal neu gestartet, nix ändert sich. Bin mit meinem Latein nach Stunden am Ende und würde mich freuen, hier Hilfe zu bekommen...
-
Genaues Log vom Adapter-Start?
-
@greenhorn sagte in Zigbee iobroker Error while opening serialport:
dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4d856ba1ab6ed1196ded60ea8669f5d-if00-port0
Und zeig mal das Ergebnis
ls -lAh /dev/serial/by-id
-
@meister-mopper sagte in Zigbee iobroker Error while opening serialport:
ls -lAh /dev/serial/by-id
simon@iobroker:~ $ ls -lAh /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Jan 14 13:56 usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c4d856ba1ab6ed1196ded60ea8669f5d-if00-port0 -> ../../ttyUSB0 -
Wie mein Username schon sagt bin ich ein absolutes Greenhorn und google mir mein Raspberry-Wissen zusammen. Zum Auslesen der Log-Datei des IOBrokers habe ich jetzt aber keinen Befehl gefunden...