Just received a ConbeeII to replace my Xiaomi Aqara hub. I can see the usb stick with lsusb and it shows up as ttyACM0 under /dev (not ttyUSBx)
However it does not get recognised in deCONZ (no device ever shows in the dropdown menu) and HA can’t connect to it either when configuring as ZHA.
I tried to configure it under Integrations, but I get an error message:
Same happens if I manually configure it in configuration.yaml with:
Turns out I did not RTFM. Once I followed the correct instructions to install deCONZ, I managed to get it running and apply a firmware upgrade.
The plan was to transfer my Xiaomi devices over to deCONZ/ZHA to get away from the Chinese spies.
Turns out I whether I use deCONZ or ZHA, I have the same issue where reported battery level is always 100% whereas via the Aqara Hub I get what appears to be a correct value (41% and 43% for 2 sensors with a 1+ year old battery in them.
I’ll raise a new post for this. The issue raised on this thread is now resolved
My Conbee II is working fine on RP3, but I am considering switching to my NUC with Ubuntu/Docker.
I have installed hass.io on Ubuntu and then tried the deCONZ addon as well as the proper docker container, but I can’t get the Conbee to show the firmware version - it just shows as “not connected”.
Was it the same for you?
I have added my user to the dialout group. ls /dev is lists the ttyACM0 device. Same if check within the deconz container, so it seems to be exposed, but it’s not talking to any devices. I also restored my Phoscon GW backup, but no joy.
I can’t remember exactly, I think I installed phoscon following these instructions and then it all started working.
linking to HA or using the container did not work until I installed phoscon (I guess some drivers are included in the phoscon package)
Please note: I’m on Ubuntu, not hass.io