Hacker News new | ask | show | jobs
by Lendal 1279 days ago
My house is standardized on Z-wave because I can afford a bit extra $ for each device in exchange for reliability. I can also add Zigbee if I need to, since my hub can do both. I just haven't needed to yet. Everything is available in both Zigbee and Z-wave versions, so I choose to pay the extra for added reliability.

I haven't had much luck with Bluetooth and Wifi IoT devices. They tend to last a couple of years and then die. They also are more hassle to set up, and use more power. I don't need more hassle in my life. Z-wave and Zigbee are both more reliable, with Z-wave taking the slight edge over Zigbee.

What's happening now is Thread (Matter) is coming. Thread is basically Zigbee Mark II. Thread is on par with Z-wave, but it supposed will retain its edge in cost benefit. I may start buying Thread stuff as it becomes available, but the problem is my mesh is solidly Z-wave. It doesn't seem worthwhile to start replacing stuff that works perfectly fine.

1 comments

Z-Wave also supports device associations which Zigbee doesn't. You can permanently associate devices together (i.e. switches) to create a virtual 3-way switch that will work even if the "smart home hub" is down. Which, from a reliability perspective is a much better design if you're installing something commercially.
Is that not binding in Zigbee?

Home assistant docs because I can't find a better description: https://www.home-assistant.io/integrations/zha/#binding-and-...

I wish Z-wave or something would support some form of physical connection instead of relying on wireless. I'd be perfectly happy running CAT-5 to every damn switch in the house if I could get reliability from it.

I've fallen back to physical switches that can be relay controlled.