Update conbee II to conbee III in docker Container unsucessfull

deCONZ Setup Support
1

I am trying to replace my Conbee II with the new Conbee III. Deconz is running on a Synology NAS in a Docker container.
When I follow the instructions and close the container, swap the Conbee II for the Conbee III, I get the following error message:
“error gathering device information while adding custom device “/dev/ttyACM0”: no such file or directory”
and the container no longer starts.

What can I do?

2

The Conbee III is /dev/ttyUSB0, try using this as device

3

That doesn’t work either. I did a new install with this.

How to change this in a running container?

4

Did you add this?
- DECONZ_BAUDRATE=115200

5

Yes, i did. Nothing changed.

6

Did you update your deCONZ to 2.24.2? The Conbee III is not supported in 2.23 and smaller.

7

Yes, i did.
The container is starting now, but the conbee III ist not found by deconz.
Its listed as Conbee and i am not able to connect.

Wich device name ist correct for the conbee III?

Conbee II = /dev/ttyACM0
Conbee III = /dev/ttyUSB0???

8

ConbeeIII is now working with /dev/ttyUSB0 and DECONZ_BAUDRATE=115200

it´detected as “normal” Conbee I in the Phoscon App but ist working.

9

Hi @Spy ,

I have the same problem, see here:

Greetings

1 Like
10

Indeed inside Docker it’s not possible to query various USB descriptor information like product string.
The baudrate is the most important factor here to have it working.

The ConBee I vs. III text is only cosmetics, however I think we can also derive that info from the firmware once connected I’ll add a small fix for the upcoming version.

1 Like
11

For me configuration

serial:
  port: /dev/ttyUSB0
  adapter: deconz
  baudrate: 115200

works !

12

Hi @azyzynski ,

Where do you enter this configuration?

Greetings

13

In configuration.yaml, I was running a new instance , and the gui was not available yet.