I really want to like Z-Wave; no cloud dependency to pair devices, and it’s not fighting for airtime on the already crowded 2.4GHz band. I’ve started small with 3 ZWave devices, and the experience hasn’t been great.
- Physical state changes barely get reported. If I flip a switch by hand, Home Assistant (via ZWave JS) seems to catch it maybe 1 out of 6 times. It’s not just the switches either, the thermostat does the same thing. Different device categories, different manufacturers, same failure to report state changes, which is a big part of why I suspect this is a Z-Wave thing and not just bad hardware.
- Inclusion is absurdly finicky. The order has to be exact: Factory reset the device, power off the device, start inclusion in Z-Wave JS, power on the device, put device into inclusion mode. Mess up the order and it silently fails to include. No real error, it just doesn’t work.
- Z-Wave LR has apparently been broken in a pretty fundamental way for a while. See this zwave-js writeup: https://blog.zwave-js.io/2025/08/01/zwave-not-so-long-range/. Sounds like it’s fixed as of SDK 8.0, none of the end device I purchased has actually delivered firmware with the fix baked in. I rejoined all my devices with non-LR ZWave to see if that would fix state reporting, it did not.
- It seems like SDK bugs in general are common? I have searched online for my issues, and it turns up a lot of topics that dead-end in “SDK bug”
My setup, for reference:
- Honeywell T6 Pro thermostat
- Zooz Zen77 800LR dimmer
- Zooz Zen72 800LR dimmer
- ZWA-2 (firmware 1.2) antenna
- Z-Wave JS software
So, is this normal for ZWave? I see plenty of ZWave negativity online but I can never tell if that’s the usual “happy users don’t post” thing or if there’s real fundamental limitations with ZWave. Curious to hear from anyone running similar hardware. Is your experience this bad, or should I be looking at what I’m doing wrong?



