Hello. I almost screwed up today and am still having anxiety over my near screw-up. I currently have two ZBT-1 Skyconnect USB dongles - one is my Z2M coordinator with over 70 devices, and the other is a thread border router.
After updating to HAOS 15.2 and Core 2025.4.4, I suddenly saw that the Open Border Router integration was installed somehow and was giving me an error. Anyway, long story short, I tried to figure out what this error was and ended up somehow pressing the button to reconfigure my z2m coordinator into a Thread border router, because I was silly enough to pull out the wrong USB extension dongle while trying to figure out which dongle was which. Somehow, that rewrite attempt failed (thankfully).
So now after I’d done everything I could to fix things, my Z2M coordinator is in a state where it absolutely works 100%, all devices are responsive, it shows up correctly in the “all hardware” page under ttyUSB0, but it is no longer recognized in the “Home Assistant Connect ZBT-1” integration. Instead, there is only the thread border router ZBT-1.
In the systems → hardware section, there is only one ZBT-1 showing (the Thread one). The coordinator has pretty much been abandoned by the integration, even if it works perfectly fine. I am just wondering if there are any yet unforseen repercussions here as all my future backups across even new systems will now have this form of disconnect, for so long as I still use this Skyconnect dongle as my Z2M coordinator.
Is this fine? Perhaps someone can advise a way on how to get the ZBT-1 back into the integration, as when one tries to configure the dongle, you’re given the choice to configure it to work with Zigbee (which I assume will erase my coordinator and initialize it for ZHA) or Thread.
Edit: okay it seems I discovered a GUI issue exclusive to my situation. If I ignore the said Skyconnect, when checking System → Hardware, Home Assistant is no longer able to determine that I’m using an HA Green (I see a red banner saying “Unknown Error”).
Gemini assumes a websocket communications error related to the Skyconnect with Keyerror: ‘vid’. This is almost certainly due to my unique circumstance.
When I stop ignoring the ZBT-1, everything’s fine again and the system gets recognized properly in the hardware page.