How would you use this and ensure privacy and security? Without investing time in becoming an amateur network engineer?
How would you use this and ensure privacy and security? Without investing time in becoming an amateur network engineer?
This was exactly the nice thing about Zigbee (and Z-Wave). They're not IP networks, they basically just work with any hub, and have no way of phoning home at all. You can use them with Home Assistant or other open source tools or write your own stack if you wanted. The thing that really blows about the switch to matter, is that it is IP based, and it looks like vendors will have another opportunity to tie specific functionality to their own hubs (and probably find a way to exfiltrate telemetry). There really wasn't anything wrong with Zigbee or Z-wave that couldn't be fixed in incremental protocol revisions (IMHO), but they don't generate money the way WiFi devices collecting telemetry or hardware churn for the sake of hardware churn does.
I only have experience with the first three (besides Home Assistant) and they work very well (though the SmartThings hub is somewhat limited when it comes to device support, graphing, etc.).
I should also mention that with Homey Bridge the dashboard is in their cloud, though the Zigbee/Z-Wave devices are fully local. Homey Pro is also local. (I think they have a Homey Pro Mini in the US now.)
HA is fiddly but with enough effort you can make anything run the way you want to, and the community is pretty active.
weirdness going on in a regular home you need to accomodate that with any of these 'turnkey' solutions
Homey Pro supports user apps written in HomeyScript (which is JavaScript-based). Similar to Home Assistant, there are many community extensions, including more obscure things. For instance, our not-very-common heat pump is also supported in Homey. A lot of vendors make Homey apps as well.
In a household with more than one person, everyone eventually has to use the home automation system and with Homey (but also SmartThings), I am sure my wife can also manage it when necessary if I'm on the go. Managing Home Assistant + the hardware is going to take a lot more effort to learn.
I like Shelly's doodads. They are easy to work with, you can flash their firmware with an alternative if you want (Tasamota is popular). They have a decent onboard scheduler and the only app you need is a web browser pointed at its IP address. They don't need internet access.
1. Open/Close sensors, I would like to put sensors on my shed door and side gates that can tell me if they are open or closed. I will occassionally leave these open, or the kids may leave them open and would prefer they be closed each night. It's impossible for me to tell if they are closed at the moment without stepping outside.
2. Smart plugs. Being able to remotely operate / schedule plugs to shut off or on seems pretty nice. Outdoor lights being one usecase. Kids media area is another.
I started with similar needs and thought it would be frivolous, but now I find it genuinely useful and can’t believe I waited so long.
Despite this IKEAs devices have been mostly Zigbee and have worked very well with ZB2MQTT and Home Assistant out of the box. You are not required to buy a hub either that talks to some random server. Not to mention that IKEA had the to make sure the new smart hub the released was compatible with Matter/Thread meaning that customers are not forced to send more E-waste to landfill. The bar is pretty low these days and I feel IKEA exceeds that by a large margin
It seems like something for bored, married people.
It's just a personal tradeoff between features, downsides, and risks. Most people don't consider the risks at all (implicitly down-weighting that factor), and the value assigned to the features and downsides varies by person. I have some smart lights, because I like the convenience of those lights being on voice control. My TV is "smart" but doesn't get internet because I don't consider the risk of ads acceptable.
You'll still end up being an amateur network engineer though.