Correct me if I'm wrong, but...

Buyer Beware! Aqara hubs use the Zigbee protocol, but lock out 3rd party devices!

A few months ago, I bought an Aqara hub and went deep into their ecosystem. I saw their hub and sensors had good reviews, plus they were using the Zigbee open protocol, so I figured I'd stick with their stuff. I had no reason to try other devices until recently.

I picked up a tilt sensor for my garage door from a 3rd party. I made sure it was also using the Zigbee protocol, so I assumed it would be compatable. Unfortunately, when I tried connecting it to the hub, I was wrong and it wouldn't connect. Turns out, Aqara uses the Zigbee protocol, but locks out 3rd party devices. [source]

If anyone has a workaround to integrate a 3rd party device with an Aqara Hub (IIRC, I have the M3?), I'd love to hear about it. But until then - I'm looking for a refund. I would have never picked up their hub if I had known about their shennanigans; and consequently, I wouldn't have picked up so many of their sensors.

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 7 months ago (2 children)

Nabu Casa's own documentation says the ZBT-2 does NOT support multi-protocols. The zbt-2 does work with Matter, but then won't support Zigbee.

https://www.home-assistant.io/connect/zbt-2

"Connect ZBT-2 cannot do both Zigbee and Thread simultaneously. This technology is often called “multiprotocol” or “MultiPAN”. Though it is theoretically possible with the hardware within Connect ZBT-2, in our experience, this functionality doesn’t work well, and we don’t plan to implement it. We previously thoroughly tested multiprotocol with our Connect ZBT-1 adapter and found its operation to be inconsistent, often causing device stability issues. We do not believe multiprotocol is suitable for operation in the home, and strongly recommend dedicating a device to each protocol."

  • source
  • parent
  • hideshow 2 child comments