I’ve been using HA about 3 years now, running HAOS on a dedicated PC server. My devices (about 40) are all Zigbee via ZHA, with the exception of a couple WiFi devices. My system has run flawlessly and meets my needs … for the most part.
I want to add energy monitoring components now, most likely using CT clamp devices installed in my breaker panels. The devices I want to use DO NOT have a native ZHA integration, but DO have full features exposed through Zigbee2MQQT. (Zemismart Model SPM01-D2TZ)
If I want to stick with ZHA, I found a quirk that does the required translation. The quirk would push my software limits. I’m not very confident in yaml or messing with configuration files. Kind of that “don’t break it” mentality.
A second option would be to install a second coordinator and create a separate ZigBee network using Zigbee2MQQT to handle this and other unsupported devices. A side benefit would be future Thread capability to play with using the NabuCasa Connect ZBT-1 dongle. The second network sounds a safer choice and lets me putz around with new things without messing up my existing system.
Do this ^^. Bear in mind this will be its own zigbee network so devices will form their separate mesh. As time goes by, you might find out that your existing ZHA devices have more supported features in Z2M, so running both integrations is the best of both worlds if you ever want to migrate slowly.
No, to run thread you will need a third coordinator. On paper, multi-protocol is supported, but in reality it’s an experimental feature that is prone to loads of issues. TLDR: if you want thread, get a dedicated device.
Yep, like I said in my first paragraph, this lets you pick & choose which integration provides more value to you. It’s simply a matter of removing a device in ZHA and adding it to Z2M (or vice-versa) as you putz around.
If I can offer 1 tip - get a network coordinator instead of the ZBT-1. It doesn’t have to be POE - anything will do as long as it doesn’t rely on USB for communication (USB power is fine). You’ll be able to place it in a more central area of the house and avoid USB interference issues.
Thanks for the feedback. I think i will actually be more adventurous with the second network, pushing myself a bit more.
Regarding the recommendation of a network-based coordinator. I like the bandwidth bonus and the lack of radio inference with the other coordinator. My concern is how that network behaves in the case of an internet outage. My USB coordinator and ZHA network currently stays up during an internet outage. How will a network coordinator behave?
Thanks again for all the helpful comments and suggestions. I have decided to add a second Zigbee network to my HA instance. The second network will run Zigbee2MQQT on a dedicated coordinator. I plan on locating the second coordinator close to my host because my installation is pretty small and I don’t have ethernet connections elsewhere.
After going over data sheets, product reviews and installation issues stories on YouTube, I narrowed down to two possible coordinators.
SMLight SLZB-06
I was impressed with the product reviews and the flexibility people found with this coordinator. It can connect to my HAOS installed hardware via ethernet, POE, or USB. Very flexible indeed. The ethernet connection ability seems to be its major differentiating feature. People with large building footprints liked the ability to locate the coordinator anywhere in their space that had an ethernet connection tied to their router and eventually their HA host. If I chose this product, I would likely connect with USB to keep my Zigbee networks isolated from my house internet.
Home Assistant Connect ZBT-1
This is the renamed SkyConnect dongle that was introduced a couple years ago. I like it is produced and supported by the Nabu Casa team. The NabuCasa specs claim it is compatible with Zigbee2MQQT, but I haven’t found installation instructions or videos by other people on this.
So the question is: Is the ZBT-1 a good choice for a USB coordinator with Zigbee2MQQT?
, and yes, the ZBT-1 is a good choice.