41–50 of 104 posts
Earlier quoted context omitted.
Wifi for cameras is arguably also a mistake
Cameras that require internet to connect to are a mistake, but cameras that use Wifi for local link are fine (wifi is perfect for this). And, having some way to connect remotely is a requirement, for most everyone.
Earlier quoted context omitted.
All it costs is significantly more money and less options. If you limit your pool of zigbee devices to just more reputable companies, you'll end up with around the same amount of options as zwave and they'll be reliable but significantly cheaper. You also have the option to find some super cheap stuff that works just fine. That usually requires some research but not much. You can also build ESPHome devices for zigbee…
My entire “smart” home setup is built with Matter over Thread. It’s fully local. No internet access required. With Home Assistant onboarding can be done without a smartphone now. Devices without official certification work but probably only in Home Assistant.
I’m a bit surprised they didn’t add zwave into this comparison.
Doesn't zwave use a different frequency, and zigbee and thread are both 2.4ghz? Perhaps that makes it a more fair comparison?
Zigbee is basically the same everywhere, however the 2.4GHz band is of course somewhat congested.
Earlier quoted context omitted.
Doesn't zwave use a different frequency, and zigbee and thread are both 2.4ghz? Perhaps that makes it a more fair comparison?
Yes, zwave is in the much less congested 900mhz range. It is a fair bit more reliable as it doesn’t compete with: - WiFi - Bluetooth - microwave ovens Additionally, it’s a bit more strict with certification so you can easily use multiple vendors for zwave whereas with zigbee it’s often a terrible experience since vendors implement things differently in ways that are not as interoperable. In fact, for a device to be c…
Earlier quoted context omitted.
Because zwave is proprietary. There's money to be made here! Can you imagine the lost profit potential if people standardize on an open protocol like ZigBee?
It is so proprietary in fact all of the spec is on github: https://github.com/zwave-js/specs
Earlier quoted context omitted.
Standing outside with an armfull of groceries, and a door is now our of range of your hub temporarily due to the failed node. 30s can seem like quite a while standing in the rain.
Not exactly a strong argument if you need like 5 qualifications to demonstrate the issue. If the right node fails, if it happens right as you walk up, if it's raining, if your porch is uncovered, if your door doesn't have an immediate fallback... I'm sure someone will be affected because of the law of large numbers, but it seems like an unlikely scenario to base a purchasing decision on.
Earlier quoted context omitted.
My entire “smart” home setup is built with Matter over Thread. It’s fully local. No internet access required. With Home Assistant onboarding can be done without a smartphone now. Devices without official certification work but probably only in Home Assistant.
My Matter over Thread stuff keeps occasionally falling over in Home Assistant and becoming unavailable, probably a router issue as I’m using a homepod mini but still endlessly frustrating.
Earlier quoted context omitted.
All it costs is significantly more money and less options. If you limit your pool of zigbee devices to just more reputable companies, you'll end up with around the same amount of options as zwave and they'll be reliable but significantly cheaper. You also have the option to find some super cheap stuff that works just fine. That usually requires some research but not much. You can also build ESPHome devices for zigbee…
My entire “smart” home setup is built with Matter over Thread. It’s fully local. No internet access required. With Home Assistant onboarding can be done without a smartphone now. Devices without official certification work but probably only in Home Assistant.
“The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair."
HA MoT has a simplified UI, that hides hellish complexity underneath, that's held together by loose pieces of gum, which means its difficult to troubleshoot. HA has a rather laissez faire policy to stability, for example, they rolled out an update just recently that made it impossible to add new devices.
I just readded yday evening my Ikea temp sensors as they mysteriously stopped working for no reason. Why? Who knows, but you can't ship stuff like this to a non-technical audience, especially if they rely on it. I had it connected as the temp sensor of my AC, and was surprised to find the AC was not working, thats how I found out it suicided itself.
I’m a bit surprised they didn’t add zwave into this comparison.
They're probably only comparing open protocols. If one doesn't care if their protocol is proprietary then sure one might consider zwave. But it's hardly "surprising" that it's left out.
All three of them have their shortcomings. Matter requires an unsecured IPv6 network to operate; I have my doubts about it having any longterm future.
These protocols add so much complications it makes wifi/tcp/ip a blaze They fix some problems but add more, you endup just like that xckd about protocols