Zigbee/Conbee II not working with version 2026.3.2

Solved - See last my last reply.

The Zigbee/Conbee II is not working in version 2026.3.2.

I have tried many things like updating the driver
“sudo wget https://github.com/robertklep/dsm7-usb-serial-drivers/raw/main/modules/apollolake/dsm-7.3/cp210x.ko
and
“sudo modprobe usbserial
sudo modprobe ftdi_sio
sudo modprobe cdc_acm”
and updating the configurtion.yaml with
“zha:
usb_path: /dev/ttyACM0 # Update this path if your ConBee II is recognized differently
database_path: /config/zigbee.db # Path for the Zigbee database”

Disconnecting the Conbee II and connecting it again and then run:
/sbin/modprobe usbserial
/sbin/modprobe ftdi_sio
/sbin/modprobe cdc-acm
chmod 777 /dev/ttyACM0
chmod 777 /dev/ttyUSB0
do not help either.

The error I get is that it cannot find /dev/ttyACM0


but it is configured
billede

I do not know what to do now, it could be a bug or no drivers for the version 2026.3.2 or 2026.2.2 (have also tried this version).

I must go back to version 2025.8 and wait for a Fix for this problem - or is there anyone who know how to solve this issue?

Try using the by-id path. Go to Settings > System > Hardware. Click All hardware. Scroll down and find the tty path for the coordinator that uses /dev/serial/by-id. Try using that path in your settings.

When I go to Settings > System > Hardware I will get the below window and nowhere to click All hardware.

Is this this you means:

billede

How are you running HA? I was assuming HAOS…

In HAOS, it looks like this -

Solved - here is what I did.

I deleted all Containers.
I made a Task Scheduler with the following content:
docker run -d
–name=homeassistant
–privileged
–device /dev/ttyACM0:/dev/ttyACM0
-v /volume1/docker/homeassistant:/config
-v /etc/localtime:/etc/localtime:ro
–network=host
homeassistant/home-assistant:latest


The part “homeassistant/home-assistant:latest” is the Image with the latest version of HA

First I tried to make the Container by indicating the Image and then click Run, but that didn’t succeed for me.

Remember to take BackUp and maybe the way I did, read here:

Like @mmstano mentioned…
The TTY ports can sometimes change internally, so it is suggested to use the /serial/by-id/ URL that always talks to your dongle by serial number so it is always right.
You can find out what that is by using:

and looking for it under all hardware, something like this:

Once you have the long URL use that instead of the ttyxxx one.

If you are using a Container installation, this is how to see the /serial/by-id/ URL:
ls -l /dev/serial/by-id

Current version is 2026.3.1

Yes you right :slight_smile:

–device /dev/ttyACM0:/dev/ttyACM0

Map the device by id to ttyASM inside the container.

  • device /dev/serial/by-id/conbeeII:/dev/ttyACM