I have been using both IBT-1 (thread) and a Aeotec Gen5 Controller (Z-Wave) on my HAOS (Laptop) for sometime without any issues. When I tried to upgrade to a IBT-2 my connection to the Z-wave Controller failed.
My process for this install was to uninstall the Integrations (ZBT-1, Matter, Thread & Open Thread Border Router) and then install everything for the ZBT-1. I have since moved back to the ZBT-1 and everything seems to be working OK.
Has anyone else seen this? Any ideas how to proceed?
No. But my first guess would be that USB assignments changed and you did not assign the Z-Wave USB by serial id. I’d check to see the USB settings for the Aeotec.
Not sure what these are. It’s in your title as well.
Do you mean ZBT?
So sorry Zbt-1 & ZBT-2.
I am currently running with the Z-Wave (Z-stick GEN5) with ZBT-1. Here is what my links in /dev/serial/by-id look like:
lrwxrwxrwx 1 root root 13 Aug 23 14:24 usb-0658_0200-if00 → ../../ttyACM0
lrwxrwxrwx 1 root root 13 Aug 23 14:23 usb-Nabu_Casa_Home_Assistant_Connect_ZBT-1_c8e4d5d71912f011ad05fd13773d9da9-if00-port0 → ../../ttyUSB0
So I think everything looks OK with the ZBT-1 and the Gen5. Could it be that these links are not cleaned up when I uninstall the ZBT-1? Maybe I need to do some manual cleanup after the uninstall of the ZBT-1?
If you used the one with the serial ID instead of the numbered ones you cannot go wrong. If you used anything other, the controller software might be looking at the wrong device when the numbers are assigned differently.
Z-wave use 800/900Mhz and Thread/Zigbee/Bluetooth/WiFi use 2400Mhz, so it is not the radios that interfere.
Sorry still not clear to me what you are saying. I just checked and my Z-Wave setup points directly to the serial port: '/dev/ttyACM0. Should it be pointing to the link in ‘/dev/serial/by-id/usb-0658_0200-if00’, which is a soft link to ‘/dev/ttyACM0’.
Wally:
The problem is Linux trying to failing connect to the Z-Wave GEN5 stick. I am not even close to communicating with the Z-Wave or Thread devices. Remember my setup is working just fine with both ZBT-1 and Z-Wave. The problem occurred when I tried to upgrade to the ZBT-2.
At this time, dev/ttyACM0 points to the right device. But if you plug in another tty device and reboot, linux may decide the other device gets dev/ttyACM0 because it was initialized first. So by using the serial by id in your config you are 100% sure it is the right device you are connecting to, regardless of what number the serial port is assigned at boot or plug in.
At this moment that does not seem to be your problem, but it may be a month from now.
My comment was just to clear up that it was not radio interference.
My betbis on Edwin_d’s suggestion.
I was able to try again and I was successful.
Apparently this ZBT-2 connects (automatically) to the linux device (ttyACM0) but the Z-Wave controller has already been configured to use ttyACM0 so it fails. All I had to do was reconfigure Z-Wave to use ttyACM1 and everybody is happy.
It was an easy workaround (undocumented), but it is probably not the way you want this to work.
Thanks to WallyR and Edwin_D for your time & thoughts.
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. Zigbee2mqtt will not start , can not find the usb0 port - #5 by Saoshen