Hi everyone,
I am reading up on that topic for a few weeks now and the only conclusion I have so far is: There is nothing that works perfect and you need to check for each device if it works with your setup.
So I am asking about your experience so far, what you use, if you plan to change your setup (for what reason?) or what you would do different. Or do you use multiple gateways / protocols at the same time?
I run HA in Docker for a few things, but I have nothing connected yet via one of the protocols mentioned above. Yesterday I came across SkyConnect and thought I found the holy grail of dongles. Zigbee? Check. Zigbee2MQTT? Check. Matter? Check. But then looking at the details… Zigbee2MQTT is experimental and in a few review (although none was younger than 9 months) people report that it works unreliable. Matter support also is not there yet it seems. And to add insult to insury it seems that it officially does not work with a Dockerized HA setup.
So whenever I think I found “my” solution, there is something that does not seem to work, is unreliable or not compatible with all devices. I even ran across reports that said if a device Support Zigbee or MQTT it might still not work with your particular setup because… well… not everything that has a specific protocol stamped on the package seem to work in the same way.
So I feel like running in circles. I wanted to start with a few simple things like Temperature / Humidity sensors and Door sensors like for example the ones from Aqara. But if I throw money at someone my highest priority is reliability. So I want to go a route that (at this moment) is the most stable, reliable and future proof in your opinion.
So I am very curious about your setups and the experience you made with it :-)
You must log in or # to comment.
HA matter support is still BETA
Matter supporting devices are still VERY few and far between (some vendors have back tracked from supporting it)
I am not even considering matter an important feature until HA is out of beta for it, it cant even act as a matter bridge yet. This is particularly important if you want HA to be the master of everything and you want to use matter with other systems directly.
For now my setup is all self run docker… I run the main HA container, zigbee2mqtt for zigbee support, and zwave-js in a docker for zwave support.
By far zwave has the most mature lock / security / control devices
By far zigbee has the MOST / cheapest sensors and other devices (Aqara in particular for sensors)
I would love to consolidate but I am in a complete rebuild of my setup and from the look of it most of my door locks will be going zwave and nearly all my sensors will be Aqara zigbee.
As for which way to go with zibee, I started with ZHA then switched to zigbee2mqtt for a few reasons
- zigbee2mqtt has slightly better device support, seems to get device support a litter faster for new strange devices and has a great online database of supported devices.
- zha restarts with HA, this includes restarting the zigbee dongle AND NETWORK… every time to do a full restart of HA you may cause all your zigbee devices to become unavailable till the network comes back up, particularly sensors. Running zigbee2mqtt as a separate docker it only ever gets restarted when I reload it for updates, the network is always VAST and up. When I restart HA the only wait is for HA to connect to MQTT and bang all the devices are back with the correct states
- Feedback… zha has a better UI integration IN HA, however I found using the native zigbee2mqtt webUI it had more real-time feedback for actions such as inclusion, or advanced stuff like binding devices together which requires some odd timing of you pressing device buttons.
- zigbee2mqtt was very tunable, from setting up the keys / channels to how often it polls to find out if battery devices have gone missing.
Thank you very much, that was very helpful! I am leaning towards Zigbee2MQTT and it seems to be a good choice.
ZHA is out of question now, since how often I have to restart HA for updates, I am sure it would be annoying to me. My Mosquitto Instance however does not receive updates as frequent, so Z2M might be the better choice for me.
Could you tell me what kind of Bridge / Device / Dongle you use? I often read Conbee II**, but this is not on the recommended list for Z2M. On the other hand I am thinking about getting a Network only Gateway (there are some on the recommended list too), so I do not rely on a USB connection that needs to be mapped to a Docker Container. Having pure Network connections and independent devices sounds like a more stable solution. Also I assume having a Networked Gateway instead of a USB connected one would be independent of restarts from my Containers or even the host.
**Edit: It IS on the Recommended list, I just got confused because it is not listed on the USB section, but under Other :-)
I have the Sonoff -P version
Thanks :-)
Where have you seen that Z-Wave devices are iffy? I’ve never had one that didn’t work with my setup, and I’ve even swapped my controller out (now, that was a pain). I have 51 nodes in my network, from many manufacturers and a 6 or 7 different types of devices. Where are you reading about Z-Wave compatability issues?
To be honest, I might have mixed something up reading up on all those standards. After researching a topic, my browser usually ends up having a hundred Tabs “just in case I need that information again” and honestly… in all that information I can not find it specifically. My consensus reading all that information was: “Make sure for each device you buy that it works with your specific gateway, even if it says it works with protocol X”.
That’s always good advice, but IME it’s not necessary with Z-Wave. And it’s only my experience, which is why I was interested in where you read it.
I wasn’t trying to attack you; I was simply curious.
Ignoring Matter, Zigbee and Zwave are the two radio protocols while Zigbee2MQTT and ZHA are your two options in Home Assistant to interface with Zigbee radios (pick one or the other).
I used to use a HUSZBZ dongle which had both Zigbee and Zwave radios integrated into a single dongle, but it’s older now and didn’t support newer devices. I’ve now switched to the Sonoff 3 Zigbee dongle and a separate newer Zwave dongle (can’t recall which brand).
As far as which integrations to use, I’m running Zigbee2MQTT (switched from ZHA when I added the new dongle to try it out) with little issues and running the default ZWave integration in HA.
As for devices, I’ve ran into some issues with Ikea Zigbee devices which is what lead to me buying the new Zigbee dongle and switching to Z2M, but those have all been resolved in the switch. Zwave devices have been pretty rock solid since day one but are generally much more expensive to buy.
I’d personally run both protocols so that you have more options when buying devices. I have numerous Aqara Zigbee devices and they’ve all worked without issue.
I use zigbee2mqtt myself and I’ve been very happy with it. I haven’t tried ZHA, but I believe z2m supports more devices. (I use z2m’s supported devices list to choose which ones to buy.) The downside is that it’s a bit more work to set up initially, as you need an MQTT broker as well. But in return, I feel like z2m is more reliable since it runs (and is updated) separate from HA core. I use it with a zzh! dongle and even though I got one of the bad ones with a faulty amplifier chip, it’s been rock solid.
As for Thread(+Matter), I’m waiting for things to settle down. Support in HA is still experimental and there are very few products out yet that use Thread. I’ll probably prefer Zigbee for as long as they sell them so all my devices will share the same mesh. Also, unlike Zigbee, Thread devices are not guaranteed to be local-only, which is my biggest worry. Thread/Matter won’t free us from having to check a device compatibility list before buying.
Thanks for your input! MQTT is not an issue, I have Mosquitto running on both my installs (one with HA + Frigate on a remote location, the other one HA for me which is also used by Owntracks), so MQTT is not a problem. I will even set up a second one and connect them together to have 2 Brokers for the setup where I need Internet access (Owntracks) to MQTT and I do not want to share this MQTT instance with the devices for my home.
My impression about Matter was too that it is not “done” yet and device support is poor. On the other hand you read at every corner that it will be the future. This is why the SkyConnect Adapter looked very interesting to me at first, but since most of the features I would use now (Z2M probably, Docker compatibility) do not seem to work yet, or at least not reliably.
My impression about Matter was too that it is not “done” yet and device support is poor. On the other hand you read at every corner that it will be the future.
This is my impression as well. I’m keeping an eye on how this space develops and I’ll probably buy a second dongle just for Thread when I need it (i.e. when some product I really want comes out that only supports Thread.) I believe most zigbee dongles are theoretically capable of supporting Thread, since they both share the same physical layer protocol.
I’m curious to hear people’s experiences with Thread/Matter devices. Ideally, I’d like to use my HA box as the border router and configure it to not allow any external Internet connections. Will this break any functionality on devices with a Matter logo on them? Ideally it shouldn’t, but given the track record of manufacturers so far, my expectations are low.
Matter and whether external connections are needed or not will be interesting to follow. My HA instance is internal only too, since it does nothing that needs me to access it over the internet. And Owntracks delivers to a separate MQTT instance that will have no internal devices. So my HA is shut off from the internet and I will pay attention to everything Smart Home I will buy, that it does not require an Internet connection too.
I suggest limiting yourself to ZHA, which is natively supported by Home Assistant, specially in these early stages.
I am doing that, and essentially waiting until Matter becomes the bigger protocol.
Yeah, except I bought a couple new Hue bulbs and ZHA wouldn’t find them. Z2M picked them up immediately. There really is no universal solution, even with “standards”.
Did you check the ZHA compatibility list? Find it, and stick to it.
Yeah, lesson learned there, but to OP’s point, nothing ever seems to just work.
Fun part in my case is that the specific bulb I want doesn’t have a ZHA-compatible counterpart. (Hue a19 white& color 1100. The 800 isn’t bright enough.)
I am leaning more towards something that might be complex to set up, but has broader support and is future proof. And the latter one seems something that is not really clear for any of the current protocols. Maybe in 10 years things will have settled and everyone uses the same protocol, but who knows what it will be :-) I am leaning towards Zigbee2MQTT for now since my impression is that you are very flexible to do with MQTT. I already use MQTT for Frigate and Owntracks and if other devices put their stuff into MQTT I will I have a pretty open pool for all the data / actions, even if I switch from HA to something else in the future. I feel MQTT is here to stay for a while, but well… that could all be wrong, Haha!
100% this. It’s the simplest and most straightforward integration of zigbee in hass.
I migrated from Samsung Smartthings when they did their big change I guess late last year. I am using zwave and Zigbee2mqtt as I had both zwave and zigbee devices already installed all over.
I went with z2mqtt because I wanted to integrate a few other things into HA like my weather station, and Blue Iris. It’s been working great for me.
I run HA on a Rpi, and the only ‘problems’ I had were because of radio interference from USB 3.0. I bought a cheap usb 2.0 port (HUB) and extension cables to move it away from the pi, and it’s been pretty solid since.
May I ask what Gateway / Dongle you use? Oh and that weather station sounds interesting, if you happen to have a Manufacturer / Model for me I would like to read up on that too :-)
I am leaning towards MQTT too because of other solutions that already integrate into that. It looks like a great way to throw different Data into a single pool to make them accessible in the same way, no matter if it is a switch, temp sensor, Camera, GPS Data etc.
Conbee Ii for zigbee and Aeotech z-stick for zwave.
As for weather, I use ecowitt devices that run through their GW1000 (gateway 1000). This is integrated with a weewx install (also on an rpi) that has an mqtt module installed. So once that’s all setup I configured the sensors on comfig in HA to look at the ones I wanted access to.
That is cool, thank you very much!
I have close to 30 z-wave devices. Some are hard wired, some USB powered, some battery powered. I’m mostly happy with it, and things have gotten a lot of polish in the past couple of years. Z-wave JS is very good. I’ve been using Z-Wave JS UI which does the same thing but has a UI along with it. It’s unnecessary and has a more complicated setup, so stick with Z-Wave JS.
The only thing I run into on occasion is slow response time. It usually happens after an update and works itself out in time, or worst case after a reboot. Otherwise things are good and fast.
I also have a ton of wifi devices (and enough WiFi backbone to support them all). Most lamps in the house have a sonoff basic wired in.
Thank you! I suppose you use a USB Dongle or is ist some kind of stand-alone Gateway that sits in your LAN?
A USB dongle, yes. I think mine is a 700 series which was a little buggy for a while. It has been fixed with updates. I believe there’s an 800 series now, but I haven’t read anything about it.
Nice thing about z-wave is there’s one “company” in charge of the tech who licenses it out, so the market isn’t flooded with crap. Downside to that is higher cost typically. That’s my understanding of it at least.
I have a lot of ZigBee devices with SLZB-06 Ethernet PoE ZigBee coordinator (it’s Ethernet, so hardware independent and you can put it wherever you want) and some Shelly (so WiFi) devices. I use ZigBee2MQTT (docker) and all the devices are managed by NodeRed, so If there is a device that is not supported by HA, I can make it compatible just with a couple of nodes in NodeRed that kinda works as protocol converter: it receives messages from devices and send them back to HA and vice versa. In this way I can use whatever device I want. For example I’ve just added acouole of 12 relays + 12 input ModBis over RS485 boards and with NodeRed in the middle, I can use it in HA without any problem!
I’m no HA expert, so maybe this can be done within it too, but with NodeRed it’s so easy, I don’t risk any break over HA updates since all the devices are basic MQTT devices and if tomorrow I want to switch to something different from HA, it would be pretty easy.
I was about to order a SLZB-06, but they were out of Stock. That one looks exactly what I want. I never really looked into NodeRed, but normalizing everything before using it makes sense. The SLZB-06 makes the Zigbee Network connections independent from any Servers and making everything going through MQTT makes you independent from any Software that has to communicate with the Devices. Sounds like a lot of flexibility and independence.
Exactly! If you’ve never used Node Red, get ready for a new world of possibilities!!!
I use zigbee2mqtt on a separate pi4 from home assistant specifically for it more central in my house with the sonoff zigbee 3 dongle with great success. The same pi actually has a zwave2mqtt instance on it with the conbee dongle, just make sure to use a powered USB hub on the pi for the radios, I always had flaky issues if the pi was powering it directly.
You can use a remote adapter with ZHA as well. See my guide.
Oh man, that’s a really slick idea, thanks for sharing! Have you tried it with zwave as well? Do you notice any delay in zigbee commands to the mesh at all?
I don’t run any zwave, but I don’t see why it wouldn’t work. I don’t notice any delays. Tbh things feel snappier and more reliable, but I was previously using like a 50 foot usb cable lol. I don’t think it would function any differently, in terms of stability, than zigbee2mqtt because Z2M actually uses ser2net as well to accomplish this.
Oh I didn’t know that, that’s cool, I’ll give it a whirl! Thanks for sharing.
Thank you! Regarding the Sonoff Zigbee 3 Dongle: I see it has an external Antenna. Did you need a USB extension cord too or is this interference problem other dongles seem to have with USB ports mitigated by the external Antenna?
So I couldn’t think of a short way to describe it without
so I just did that, the Pi is the one on the right side near the top with the red velcro and the radios are velcroed to the door on the left. I have cheaper extensions for both radios but that was more to keep it above the power strip because I was slightly concerned and make opening the door easier.If your adapter isn’t like buried in a metal cabinet and you have one or two zigbee router devices (like a switch or a bulb) close by it will be fine I bet, give it a whirl. Those extensions are just cheap USB 2.0 cablematters extensions from Amazon.
I also apologize for the cable management hire, that location is in transition to different gear 😀
ETA: The other radio is the z-wave radio and I was wrong above, it’s the zooz radio, guess I forgot I upgraded it hah
Technically I run OpenHAB not HA, but I’ve struggled with this too.
I’ve been wanting to dockerize my Openhab for a while but have found similar issues with compatibility and network discoverability so I’ve avoided it. My current setup is their official Raspberry Pi os (openhabian), with a Conbee II via Zigbee2mqtt for zigbee with Hue, Tradfri and Sonoff devices an Aeotec Zstick Gen5 (no plus) for Zwave with mostly Zooz devices, way too many WiFi devices (mostly TPLink Kasa) and probably some other things I’ve forgotten.
To be honest though I haven’t fully nailed reliability. It works for months straight with no issues but every so often I get a bug that requires resetting a device or two, or an update stomping over my SSL certs, or some intermittent slowness, but it’s reliable enough. I specifically avoid any cameras or security devices (beyond some door sensors for non-security reasons) so that I don’t have the headache of high reliability.
The whole setup is a patchwork of whatever happened to work at the time and wasn’t prohibitively expensive for me. I decided a long time ago that the flexibility was worth more than paying a bunch more for a single highly reliable system.
It sucks, but it works better than manually switching on my lights all the time, so it’s good enough for me.
I’m running a Debian Bookworm on a Zotac Tiny PC, plus Docker and Mosquitto with HomeAssitant supervisor installed and a Sonoff usb dongle P. No ZigBee2MQTT. To begin with the Dongle was recognised by HA, natively running ZHA, all worked okay. Then I added ZigBee2MQTT as a add-on in HA, linked it to my Mosquitto account, added MQTT as an add-on as you need it as well. The difference is enormous, as I now have a ZigBee Dashboard, many more options were seen by the ZigBee2MQTT on the devices that I had installed that weren’t seen by the ZHA, I was even able to update certain firmware on my switches.
I used to use ZHA and now Z2M, both work near-perfect.
Occasionally a few devices will drop off the network, or sometimes devices may take a few seconds to respond to an action. But overall there are very few issues.
I switched to Z2M because I saw so many posts saying how much better it is. In my experience, it’s a slightly nicer UI, but the functionality and reliability has been exactly the same across all devices I use.
