• 2 Posts
  • 22 Comments
Joined 19 days ago
cake
Cake day: March 24th, 2026

help-circle














  • 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.”





  • My first ‘issue’ is I have everything in ZHA. I want to move to Zigbee2MQTT, but with 40 zigbee devices and associated automations it’s a pita. So I figured get the zbt-2 and migrate that way. ZHA doesn’t report LQI and RSSI, so measuring the mesh isn’t completely empirical. First issue was a window sensor I use for the mailbox. It was a 3rd reality sensor and it was losing network connectivity about once a week. It’s just outside the front door, and I have a 3rd reality zigbee outlet in the front entrance. The Sonoff coordinator is mounted on the wall at the bottom of the stairs, which go down from the front entrance. (difficult to visualize, I know).

    I then tried another window sensor on a closet door in the kitchen to trigger a light when the door was opened. Another zigbee outlet very close to the closet. Sensor (aqara in this case) can’t stay connected for 5 minutes.

    So, considering I want to migrate to zigbee2mqtt anyway, I figured this was an opportunity to experience that pain.