Hallo ! 👋
Is there a reason why HA Core seems to be expecting Connect ZBT-2 available on /dev/ttyACM1 ?
I mapped the device to another name '/dev/zbt2-zb' and it works just fine with the Zigbee integration but the Connect ZBT-2 Integration no longuer sees the device.
#HA Core expects Connect ZBT-2 to be on ttyACM1
slow pendant
rigid vine
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:
https://my.home-assistant.io/redirect/hardware/
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 Be sure to include the '/dev/serial/by-id/' in front of the response as you need to tell it the full path.
slow pendant
That is exactly what I am doing, but the Connect ZBT-2 integration seems to be looking for /dev/ttyACM1.
The ZHA use it as it is supposed but the "Home Assistant Connect ZBT-2" cannot find the device...
elfin robin
Generally if you use the docker compose from the docs you don't need to map anything as it uses privileged.
slow pendant
which is something i do not use 😉
elfin robin
I figured but if you deviate from the docs then some things will behave different 🙂
slow pendant
Is there any configuration parameter to tell the integration to look somewhere else ?
rigid vine
port: >-
/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0883963e9ec8fe8847drdc5c3de5b81b4-if00-port0
adapter: zstack
``` in the configuration.yaml of Z2M.