deConz/ConBee II - not found(?) in add on - how to set up correctly!

Third party integrations
1

Running HassOS4.11 on Pi4b with Home Assistant 0.113.1

Read the other topics, found stuff similar but hasn’t helped me, turning to the forum for assistance please guys!!!

Have a ConBee II (want to decommission my Hue hub). Have installed the add on for deConz, changed the configuration to:

device: /dev/ttyAMA0
vnc_password: ''

Followed the steps in the documentation (also used a nice video here which showed it being dead easy!).

When I got to the viewing the Gateway in Phoscon something doesn’t seem correct:

image
image1572×796 62 KB

It doesn’t seem to be finding the stick; checked Supervisor > System > Hardware > and its listed as: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2191372-if00

Took it out of HomeAssistant and plugged into a Windows 10 machine, found it could access the ConBee, did a firmware upgrade on it and tired again. Rebuilt HomeAssistant and installed a snapshot from before installing deConz and repeated (several times) and still no joy!

At a loss where to turn, the ConBee seems to be working (as proved when I ran it in a different machine), HA can see it (as proved when checking Hardware) - whats the missing link here I’ve not found. Not a tech guru but not too stupid, but its beaten me :slight_smile: Thank you

2

Does it work when you use:

device: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2191372-if00
3

Hi, thanks for the quick reply.

Wow, yes that did work…amazing thank you. Everything I had read said not to do that but use the /dev/ttyAMA0 setting.

Just goes to show, sometimes don’t believe all you read and break the rules! Thanks again (was going mad with it!!)

4

This is the better solution anyway since the port might change when you plug in different devices.
Always try to use by-id :slight_smile:

1 Like
5

Well
Not really.
There is still many that have a problem with the deconz addon and using the symlink device. So if you only have ONE usb device then I advice to use the straight device link

A Conbee Ii stick is created as /dev/ttyACM0 and not AMA.

The AMA is for their Raspberry Pi hat as I recall it.

Typically the people that have problems with devices are us with Aeotec and Conbee as they both race for ttyACM0 and ttyACM1 respectively.

Those that have problems with by-id links typically see it 1-2 for every 10 restarts where the addon just fails to start claiming that the device does not exist. As far as I know this is not resolved as I still see people reporting the issue.

I personally move my deconz to its own bare metal and that solved all my problems. But if you only have one ttyACM0 device then you have no worries with the addon.