Hello,
I have spend the day playing with vanilla Home Assistant and go some z-wave module to work. However, when it comes to zigbee, I am getting stuck !
I have a couple of IKEA tradfri light-bulbs I would like to control so I :
ttyACM1 being my Zigbee stick
I can access the deconz gateway on 192.168.1.16:8080. I could also get Hone Assistant to “talk” to deconz and see the virtual sensor, but cannot see any light bulbs when trying to pair them in the Deconz interface. If there is a way to pair using HA, I did not find it.
I am running the last of Deconz as displayed in the settings/gateway (v.2.05.72), but I am not sure which firmware since under the software version the frimware part indicates “not connected”
So I guess the reason I cannot find the lightbulbs is that my stick isnot working properly
Can you please post the logs from the deconz container (docker logs deconz)? Is your host machine connected through WiFi? Do you have the stick on an extension cable or directly attached to the machine? When you go to Phoson -> Lights and press “add new lights” are you not able to add your lights? You need to add the lights to deconz and HA then reads the lights from deconz.
Are these USB 3.0 ports? Do you have a spare extension cable laying around? It’s always recommended to put the ConBee on an extension cable to avoid possible interference. USB 3.0 also causes interference with the ConBee.
What do you get when you enter lsusb on the host machine?
$ lsusb
Bus 002 Device 003: ID 8086:0189 Intel Corp.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 008: ID 1cf1:0030 Dresden Elektronik
Bus 003 Device 002: ID 0658:0200 Sigma Designs, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0408:2fb1 Quanta Computer, Inc.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I’ll try on a USB2 port to see if there is a difference, but on my future production server, I will be connected to a USB3 hub (only two ports available and one is connected to USB–>ethernet adaptator) , so I hope it is not the issue.
Use udev rules to map the stick to a fix address by using the device-id. This way it will always be the same no matter in which port you stick the ConBee. Take a look here
Is the docker user in the dialout group?
I Don’t see any DOCKER user in in /etc/passwd
And I an the only user in the DOCKER group.
If I try to see members of dialout group, it’s quite empty
But in the end, nothing really changed, I still cant pair my devices
the logfile is bad though
2020-01-04 22:35:16 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at 192.168.1.16
2020-01-04 22:35:16 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 80 seconds.
2020-01-04 22:36:37 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at 192.168.1.16
2020-01-04 22:36:37 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 80 seconds.
2020-01-04 22:37:58 ERROR (MainThread) [homeassistant.components.deconz] Error connecting to deCONZ gateway at 192.168.1.16
2020-01-04 22:37:58 WARNING (MainThread) [homeassistant.config_entries] Config entry for deconz not ready yet. Retrying in 80 seconds.
Update : I had chaged the port from 80 to 8080 for deconz so that is why I had HA error , it is bettter now
2020-01-04 22:51:06 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.deconz
2020-01-04 22:51:06 INFO (MainThread) [homeassistant.components.climate] Setting up climate.deconz
2020-01-04 22:51:06 INFO (MainThread) [homeassistant.components.cover] Setting up cover.deconz
2020-01-04 22:51:06 INFO (MainThread) [homeassistant.components.light] Setting up light.deconz
2020-01-04 22:51:06 INFO (MainThread) [homeassistant.components.scene] Setting up scene.deconz
2020-01-04 22:51:06 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.deconz
2020-01-04 22:51:06 INFO (MainThread) [homeassistant.components.switch] Setting up switch.deconz
2020-01-04 22:51:06 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new sensor.deconz entity: sensor.daylight
22:37:14:201 DB sqlite version 3.16.2
22:37:14:202 DB PRAGMA page_count: 30
22:37:14:202 DB PRAGMA page_size: 4096
22:37:14:202 DB PRAGMA freelist_count: 0
22:37:14:202 DB file size 122880 bytes, free pages 0
22:37:14:202 DB PRAGMA user_version: 6
22:37:14:202 DB cleanup
22:37:14:202 DB create temporary views
22:37:14:205 don't close database yet, keep open for 900 seconds
22:37:14:206 started websocket server at port 4443
22:37:14:207 GW firmware update not supported on x86 linux headless
22:37:14:208 found node plugin: libde_rest_plugin.so - REST API Plugin
22:37:14:209 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
22:37:14:213 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
This plugin does not support propagateSizeHints()
This plugin does not support propagateSizeHints()
22:37:18:032 New websocket 192.168.1.16:47326 (state: 3)
22:37:20:233 Announced to internet http://dresden-light.appspot.com/discover
22:37:34:445 start reconnect to network
22:37:39:445 failed to reconnect to network try=1
22:37:44:445 failed to reconnect to network try=2
22:37:44:449 New websocket 192.168.1.248:57502 (state: 3)
22:37:49:445 failed to reconnect to network try=3
22:37:54:445 failed to reconnect to network try=4
22:37:59:445 failed to reconnect to network try=5
22:38:04:445 failed to reconnect to network try=6
22:38:09:444 failed to reconnect to network try=7
22:38:14:445 failed to reconnect to network try=8
22:38:19:445 failed to reconnect to network try=9
22:38:24:445 failed to reconnect to network try=10
22:38:29:445 reconnect network failed, try later
22:38:29:445 start reconnect to network
22:38:34:445 failed to reconnect to network try=1
22:38:39:445 failed to reconnect to network try=2
22:38:44:446 failed to reconnect to network try=3
22:38:49:445 failed to reconnect to network try=4
22:38:54:445 failed to reconnect to network try=5
22:38:59:445 failed to reconnect to network try=6
22:39:04:446 failed to reconnect to network try=7
22:39:09:445 failed to reconnect to network try=8
22:39:14:445 failed to reconnect to network try=9
22:39:19:445 failed to reconnect to network try=10
22:39:24:445 reconnect network failed, try later
22:39:24:445 start reconnect to network
I tried with a USB3 dock 1 USB --> 4 USB with only the conbee stick in it but I still have the same issue,
I verified my ced user was part of the dialout group
I was reading conbee troubleshooting and it seems communication between ConBee II and deCONZ is not working as the frimware displays not connected.
I though I should try updating the firmware and used the script provided in the deconz docker container
docker run -it --rm --entrypoint "/firmware-update.sh" --privileged --cap-add=ALL -v /dev:/dev -v /lib/modules:/lib/modules -v /sys:/sys marthoc/deconz
-------------------------------------------------------------------
marthoc/deconz Firmware Flashing Script
Version: 0.5
-------------------------------------------------------------------
Listing attached devices...
GCFFlasher V3_06 (c) dresden elektronik ingenieurtechnik gmbh
Path | Vendor | Product | Serial | Type
-----------------+--------+---------+------------+-------
/dev/ttyACM0 | 0x1CF1 | 0x0030 | | ConBee II
/dev/ttyACM2 | 0x1CF1 | 0x0030 | | ConBee II
Enter the full device path, or press Enter now to exit.
Device Path : /dev/ttyACM0
-------------------------------------------------------------------
Firmware available for flashing:
deCONZ_ConBeeII_0x26490700.bin.GCF
deCONZ_ConBeeII_0x264a0700.bin.GCF
deCONZ_Rpi_0x26330500.bin.GCF
Enter the firmware file name from above, including extension,
or press Enter now to exit.
File Name : deCONZ_ConBeeII_0x26490700.bin.GCF
-------------------------------------------------------------------
Device: /dev/ttyACM0
Firmware File: deCONZ_ConBeeII_0x26490700.bin.GCF
Are the above device and firmware values correct?
Enter Y to proceed, any other entry to exit: Y
Flashing...
GCFFlasher V3_06 (c) dresden elektronik ingenieurtechnik gmbh
Reboot device /dev/ttyACM0 (ConBee II)
deCONZ firmware version 264A0700
action: update firmware after 6958 ms
flashing 158985 bytes: |=====error: timeout flashing firmware after 3004 ms
Flashing Error! Please re-run this script...
So I made some test connecting my conbee II direcly to my laptop, installing deconz, and there it work, I can detect and add lights.
So I guess the key is working and it is rather a soft problem. It may be the user owning the container not being in the dialout group, but there is not docker user, and [ced, root] are part of the dialout group so I am not sure who could be missing…
Thank you so much !!
it seems to work ! I can now see the firmware in the setting part, let me try to pair something…
it works !
What is your guess ? the - DECONZ_DEVICE=/dev/ttyZIGBEE was needed ?
or, at some point the port 5900 disappeared from my config, could it be that ?
It’s probably the DECONZ_DEVICE, it forces deconz to look for the stick at the address you specify.
Actually port 5900 is only used for VNC, so if you don’t need it you can remove it. However VNC access is quite nice, it allows you to view the mesh created from your devices and also helps in trouble shooting. If you want to enable it, add these to the environment part of deconz:
DECONZ_VNC_MODE=1
DECONZ_VNC_PASSWORD=your_super_secret_password
)