July 11, 20196 yr Hi! I have been trying to move my Home Assistant setup from my pi to my Unraid server. I have gotten Home Assitant and Node-RED up and running without any problems, but I have trouble with getting deConz to work. To be more precise I have problem with getting the ConBee 2 usb device to show up in deConz. The docker I am using is this one https://hub.docker.com/r/marthoc/deconz. I suspect the problem is with the server recognising the ConBee. In the system logs i get this error for a couple a minutes before it stops Quote Jul 11 12:37:28 Tower kernel: usb 3-5: can't read configurations, error -110 Jul 11 12:37:28 Tower kernel: usb usb3-port5: attempt power cycle Jul 11 12:37:28 Tower kernel: usb 3-5: new full-speed USB device number 60 using xhci_hcd Jul 11 12:37:38 Tower kernel: usb 3-5: unable to read config index 0 descriptor/all Jul 11 12:37:38 Tower kernel: usb 3-5: can't read configurations, error -110 Jul 11 12:37:38 Tower kernel: usb 3-5: new full-speed USB device number 61 using xhci_hcd Jul 11 12:37:38 Tower kernel: cdc_acm 3-5:1.0: ttyACM0: USB ACM device Jul 11 12:37:40 Tower kernel: usb 3-5: USB disconnect, device number 61 Jul 11 12:37:41 Tower kernel: usb 3-5: new full-speed USB device number 62 using xhci_hcd Jul 11 12:37:46 Tower kernel: usb 3-5: unable to read config index 0 descriptor/all Jul 11 12:37:46 Tower kernel: usb 3-5: can't read configurations, error -110 Jul 11 12:37:46 Tower kernel: usb 3-5: new full-speed USB device number 63 using xhci_hcd Jul 11 12:37:52 Tower kernel: usb 3-5: unable to read config index 0 descriptor/all Jul 11 12:37:52 Tower kernel: usb 3-5: can't read configurations, error -110 Jul 11 12:37:52 Tower kernel: usb usb3-port5: attempt power cycle Jul 11 12:37:52 Tower kernel: usb 3-5: new full-speed USB device number 64 using xhci_hcd Jul 11 12:38:02 Tower kernel: usb 3-5: unable to read config index 0 descriptor/all Jul 11 12:38:02 Tower kernel: usb 3-5: can't read configurations, error -110 Jul 11 12:38:02 Tower kernel: usb 3-5: new full-speed USB device number 65 using xhci_hcd Jul 11 12:38:02 Tower kernel: cdc_acm 3-5:1.0: ttyACM0: USB ACM device Jul 11 12:38:04 Tower kernel: usb 3-5: USB disconnect, device number 65 Jul 11 12:38:05 Tower kernel: usb 3-5: new full-speed USB device number 66 using xhci_hcd Jul 11 12:38:10 Tower kernel: usb 3-5: unable to read config index 0 descriptor/all Jul 11 12:38:10 Tower kernel: usb 3-5: can't read configurations, error -110 Jul 11 12:38:10 Tower kernel: usb 3-5: new full-speed USB device number 67 using xhci_hcd Jul 11 12:38:16 Tower kernel: usb 3-5: unable to read config index 0 descriptor/all Jul 11 12:38:16 Tower kernel: usb 3-5: can't read configurations, error -110 Jul 11 12:38:16 Tower kernel: usb usb3-port5: attempt power cycle Jul 11 12:38:16 Tower kernel: usb 3-5: new full-speed USB device number 68 using xhci_hcd Jul 11 12:38:16 Tower kernel: cdc_acm 3-5:1.0: ttyACM0: USB ACM device After this the device is recognised in unraid as: Bus 003 Device 068:ID 1cf1:0030 Dresden Elektronik In the log for the deconz docker I get this message repeated all the time Quote 12:52:51:538 wait reconnect 11 seconds 12:52:52:538 wait reconnect 10 seconds 12:52:53:538 wait reconnect 9 seconds 12:52:53:538 wait reconnect 9 seconds 12:52:54:538 wait reconnect 8 seconds 12:52:55:538 wait reconnect 7 seconds 12:52:55:538 wait reconnect 7 seconds 12:52:56:538 wait reconnect 6 seconds 12:52:57:538 wait reconnect 5 seconds 12:52:57:538 wait reconnect 5 seconds 12:52:58:538 wait reconnect 4 seconds 12:52:59:538 wait reconnect 3 seconds 12:52:59:538 wait reconnect 3 seconds 12:53:00:538 wait reconnect 2 seconds 12:53:01:538 wait reconnect 1 seconds 12:53:01:542 COM: --dev: /dev/bus/usb/003/068 (RaspBee) 12:53:01:538 wait reconnect 1 seconds 12:53:01:542 COM: --dev: /dev/bus/usb/003/068 (RaspBee) 12:53:02:538 wait reconnect 15 seconds 12:53:02:542 COM: --dev: /dev/bus/usb/003/068 (RaspBee) 12:53:03:538 wait reconnect 14 seconds 12:53:04:538 wait reconnect 13 seconds 12:53:05:538 wait reconnect 12 seconds 12:53:06:538 wait reconnect 11 seconds 12:53:07:538 wait reconnect 10 seconds 12:53:08:538 wait reconnect 9 seconds 12:53:09:538 wait reconnect 8 seconds 12:53:10:538 wait reconnect 7 seconds 12:53:11:538 wait reconnect 6 seconds 12:53:12:538 wait reconnect 5 seconds 12:53:13:538 wait reconnect 4 seconds 12:53:14:219 found gateway 192.168.1.64:80 12:53:14:219 found gateway 192.168.1.64:80 12:53:14:538 wait reconnect 3 seconds 12:53:15:538 wait reconnect 2 seconds 12:53:16:538 wait reconnect 1 seconds 12:53:16:542 COM: --dev: /dev/bus/usb/003/068 (RaspBee) 12:53:17:538 wait reconnect 15 seconds 12:53:17:542 COM: --dev: /dev/bus/usb/003/068 (RaspBee) 12:53:18:538 wait reconnect 14 seconds 12:53:19:538 wait reconnect 13 seconds 12:53:20:538 wait reconnect 12 seconds 12:53:21:538 wait reconnect 11 seconds 12:53:22:538 wait reconnect 10 seconds 12:53:22:538 wait reconnect 10 seconds 12:53:23:537 wait reconnect 9 seconds 12:53:23:741 scan finished 12:53:24:538 wait reconnect 8 seconds 12:53:24:538 wait reconnect 8 seconds 12:53:25:538 wait reconnect 7 seconds 12:53:26:538 wait reconnect 6 seconds 12:53:26:538 wait reconnect 6 seconds 12:53:27:538 wait reconnect 5 seconds 12:53:28:538 wait reconnect 4 seconds 12:53:28:538 wait reconnect 4 seconds 12:53:29:538 wait reconnect 3 seconds 12:53:30:538 wait reconnect 2 seconds 12:53:30:538 wait reconnect 2 seconds 12:53:31:538 wait reconnect 1 seconds 12:53:31:542 COM: --dev: /dev/bus/usb/003/068 (RaspBee) 12:53:32:538 wait reconnect 15 seconds 12:53:32:542 COM: --dev: /dev/bus/usb/003/068 (RaspBee) 12:53:32:538 wait reconnect 15 seconds 12:53:32:542 COM: --dev: /dev/bus/usb/003/068 (RaspBee) Here is a pic of the docker configuration also
October 7, 20196 yr OK - I finally got this to work, I noticed the dongle kept changing address. I locked it down following this post to /dev/ttyUSB-zigbee In my rules I have used this for the conbee II stick. SUBSYSTEM=="tty", ATTRS{idVendor}=="1cf1", ATTRS{idProduct}=="0030", SYMLINK+="ttyUSB-zigbee" Edited October 7, 20196 yr by Spladge extra useful info
December 11, 20205 yr On 10/7/2019 at 8:27 AM, Spladge said: OK - I finally got this to work, I noticed the dongle kept changing address. I locked it down following this post to /dev/ttyUSB-zigbee In my rules I have used this for the conbee II stick. SUBSYSTEM=="tty", ATTRS{idVendor}=="1cf1", ATTRS{idProduct}=="0030", SYMLINK+="ttyUSB-zigbee" Is this still working for you? Im struggling so hard with deCONZ after reboot. After reboot the usb path is always /dev/ttyACM1, and by using that it won't connect to the network. I always have to wait a bit, for the stick to disconnect and reconnect by itself, then the path changes to /dev/ttyACM0, and the deCONZ docker will connect to the network perfect, and stay that way till next reboot. So I followed the topic you posted, and used the rule you used, and by my knowledge it seems to be working, it creates a symlink. root@Gothica:/dev# ls -alh ttyUSB-zigbee lrwxrwxrwx 1 root root 7 Dec 11 11:36 ttyUSB-zigbee -> ttyACM0 it connects to the network fine by using /dev/ttyACM0 in the deCONZ docker, but by using /dev/ttyUSB-zigbee it fails to connect and the docker log spams with reconnect tries. Any advice? Thanks in advance.
January 10, 20215 yr Sorry, I didn't see this for some reason. I stopped using it and migrated to a NUC. Was doing some messing around and making changes to unraid and decided to keep the home assistant stuff isolated.
February 16, 20215 yr I've had the same problem, tried numerous things including writing a Udev rule. Thought I fixed it but a few weeks later, the problem came back. What I ended up doing was go in the BIOS of my Unraid box and disabling USB3.0 I think this fixed it for me, I'll write an update if it acts up again.
Archived
This topic is now archived and is closed to further replies.