Why is "work[s] totally independently of Home Assistant" a desirable property?
https://www.zwaveoutlet.com/pages/z-wave-associations
https://www.silabs.com/documents/public/application-notes/AP...
https://inovelli.com/collections/z-wave-light-switches-red-s...
https://www.getzooz.com/products/
https://leviton.com/products/dz15s-1bz
https://byjasco.com/products/smart-home-automation/z-wave
How are any of these functionally different?
Any that you'd recommend in particular?
Zooz is probably a close second, and probably the go-to for switches, relays, smart plugs, sensors, etc. today.
For zwave, the best actual physical control was with Leviton - they have a rocker switch for dimming and are therefore easier to use than most. They don’t support multi-press scenes or anything like that but I found that to be a bit of a gimmick anyway, and dedicated buttons are a better option.
Inovelli had the most features, but aren’t precisely colour matched to other brands - they are kind of whiter than the standard white colour so stand out if you put them in a bank with others or against certain face plates.
In my new house I have a few zooz switches for special cases alongside Lutron for everything else and Zooz work fine.
Inovelli and Zooz dimming controls are both done by holding down the on/off paddles which isn’t intuitive for visitors, and it’s hard to fine adjust without resorting to app control.
Of everything my favourite is Lutron Diva for hands down the best looking and easiest to use actual physical control but these use a proprietary (albeit easy to integrate) hub.
Why is this an issue? Z-Wave is a mesh network, all hardwired switches/outlets/etc. are repeaters by default.
> low volt LEDs in your kitchen like I do
What is "low volt?" 12-24V? I have this in my kitchen using a 110V -> 24V dimmable LED PSU and a Z-Wave triac dimmer.
Zigbee is not Z-Wave - Z-Wave has far more definition and structure to available devices and can do everything Lutron can do at this point.
That’s not entirely correct. Zwave is more expensive because if you want to sell your zwave solution there’s a monopoly on zwave. Nothing to do with complexity or age.
As for “better performing”, I don’t even know how to respond. Latency? Reliability? Power? Bandwidth?
Zwave in general is better then zigbee due to lower frequencies and staying out of WiFi/bt. However it is more expensive and less options.
I do have a couple of zwave dimmers for special cases (dimmer and fan in one switch), and they support zwave association. Without the hub being available, one switch can turn on another - you could have the light turn on a fan, for example, or associate a remote control to a light. Zigbee has a similar feature.
A: > the idea that a botched software upgrade or failed VM could make it so I can't turn my lights on and off feels like a bit too much. Caseta doesn't use an open protocol, but it does allow all your switches, remotes, lights, etc, to work totally independently of HomeAssistant or Internet/WiFi
...I got the OG yellow/amber when it was kickstarted, and have added a 1tb NVME and a z-wave dongle (it came with zigbee).
The newer ones (green) have "ditched" internal networking other than wifi for compliance / regulatory reasons (eg: 1 hardware radio == complex, 2-3 hardware radios == exponentially more complex and requires differing international certifications).
https://www.home-assistant.io/green/
https://www.home-assistant.io/connectzbt1/
https://www.home-assistant.io/docs/z-wave/controllers/
https://www.home-assistant.io/common-tasks/os/#home-assistan...
...as that reddit thread alludes to: you're fairly better off chasing an old NUC-type-thing and just plugging in the extra dongles to that anyway (potentially zip-tying a hub, or maybe getting some 90º USB connectors so you're less worried about snapping things off if it gets bumped, dropped, or stepped on).
The software is pretty darned solid, I've dug into it a fair amount and haven't had much issues with it in the ~3-4 years I've had it.
As the CLI link describes, there's 2-3 layers of "reliability" going on: core => supervisor => host. Basically the supervisor will restart / rotate / backup the HA-core (aka: docker image), and you can occasionally update the "Host" (aka: OS). https://www.home-assistant.io/installation/linux/#install-ho... ...their HomeAssistantOS basically wraps all that up, and if you install it "that way", you effectively turn whatever hardware you're using into an "appliance"... really, just depends on what layer you want to handle your O.S. updates (ie: throw HA on as "just another service" on your homelab? ...or "let the little box manage itself").
The reason I added Z-Wave (eventually) was to get access to an exterior-rated, dimmable plug/extension cord (dimmable string lights) ... HomeKit ones were finicky, and I couldn't find any good ZigBee ones. The reason I added an NVMe inside (eventually) was I wanted to chase using it as kindof a plex-ish / backup / media server, but there's "gross" issues with HA's backup strategy by default (ie: it backs up the "whole HD", including `/Media/...`, which makes backup times exponential compared to "just the *.config.yaml", and effectively halves your usable disk space).
Since you'll have to buy some of those dongles anyway, start with that and do the "home assistant OS running on a rpi" route. Get a feel for it, and then jump in to a NUC which you can air-drop next to your family's cable modem.
I've got 80-90% of everything bridged over to Siri/HomeKit (all devices are treated "as good as apple home app", and only a few HA-specific "super-nerd stuff" that I've set up in the HA gui itself (ie: timed scripts for turning things on/off when we have a party in the back yard). You still have to pop in to HA when adding a new device, new device-type, or to update any of the three layers (integrations => home assistant => kernel/os/core), so like once every few months like any potentially vulnerable IoT device.
Overall, a solid 7-out-of-10 (because it's OSS) ... as OSS it's 9-out-of-10... just desperately needs some cohesion, GUI-love, simplification, etc, but the compatibility and power is all there!
Also: how hard is it to back up 6 YAML files and a small config directory?