I needed to test a Matter-Thread device, and despite having bought an Aqara (m-100) border router and a Nabu Casa ZBT-2, I’m unable to get it working.
It’s a Zemismart Matter Thread Roller Driver, which I can’t even connect using its own app because I don’t know if it uses a proprietary border router or hub; I imagine it does.
But after long sessions of trying different devices, credentials, preferred networks, and border routers, I’m completely disappointed with the device, and even more so with the Matter Thread protocol. I don’t know if Matter performs better over Wi-Fi; I hope so.
In short, although I prefer the ZBT-2 border router, I can’t connect it to Matter in HA because when I try to create credentials, it shows the old network created by the Aqara M-100. However, the procedure is identical, and with the Aqara, I got an error saying it was impossible to connect the device.
I can’t find any official information about whether the device is limited to their own brand’s hubs, but what’s the point of a Matter device like this? It makes no sense at all. In any case, the Zemismart app warns that the device is uncertified… perhaps that’s the problem.
I’ve experienced all sorts of issues along the way, including a kind of disconnection where the device wouldn’t even charge. Luckily, it came back on after several attempts.
To be perfectly clear, Google Home, which is responsible for linking with Home Assistant Companion, for some reason, and despite the fact that (and after many attempts) the HA app is properly synchronized with the Thread credentials, won’t leave the Aqara’s old network. So, if there was a possibility of adding the device, this completely eliminates it. Alexa has the same problem; it stays on that network, and even if you try to connect it to the Aqara, it asks for credentials and a network key that I can’t find anywhere.
The error I managed to get through trial and error was to make HA companion have the same preferred network as HA server, but this doesn’t help Google Home to make the connection since it’s still stuck on the old Aqara network.
Alexa is seeing the network created by the border router (ZBT-2), but it’s asking for credentials that you can’t easily obtain; it doesn’t make sense. The same thing happened with the Aqara.
All this so that when I had Aqara, the most I got (not counting the Aqara App) was this error message:
I’m convinced that if Google Home switched to the ZBT-2 network, it would get the same error.
Using the Aqara M-100, I could only get it to show up in the Aqara app, nothing else. And SmartThing sees it as a device to pair, but it requires a Samsung hub, which I don’t have.
It’s a vicious cycle that’s impossible to break.
I refuse to let a new protocol meant to simplify and make our lives easier screw them up so quickly.
A few more details.
Matter is configured in my HA instance, along with Thread and Open Border Router. These aren’t the problems, nor are the credentials. There must be a limitation with the device.
At the height of this issue, the device paired in the Aqara app and Alexa could see it through Aqara Skill/Compatibility, but I couldn’t see it in HA. Furthermore, any new pairing or other attempt would cause it to disappear from the Aqara app.
I don’t know what else to try, I need some clarification, maybe I’m missing something or not understanding something.
Thank you in advance.