Earlier quoted context omitted.
As someone who gets caught in the occasional "could you just fix x – what do you mean y is not working? It always worked before you got here"-trap, essentially signing up to run your parents entire smart home setup, indefinitely, feels like some special kind of hell.
My choice with their new house was pretty simple. They wanted a smart home, and being the tech son I would inevitably have to help them at some point. So either I debug a system that is open and familiar, with remote access and reliable software/hardware. Or I deal with some closed proprietary trash which will end-up with me on the phone with some incompetent cash grab company. As mentioned in my post, the latter wou…
How many IoT devices are you working with?
I don't have the best router up north and some of my lousier routers can't handle more than about 25 devices before they start crapping the bed. Do they disconnect often from your router (and do the successfully reconnect)?
Similar router problem, though I've found some of the more finickier devices I own can have problems in my home where I have a number of options for connections. If you haven't had these problems, what router are you using?
What about "the internet is down"?
This was less of an issue when everything was Z-Wave/ZigBee, but all of the cheap stuff is WiFi. This mostly only concerns "the lights" and "the plugs". I don't want a switch to stop being able to control devices it's not directly attached to if home assistant or the target device can't reach the internet. All of the ones that I own broadcast state and can accept commands via UDP over the local network so I was thinking of writing something that HA could call, locally, which would issue those commands and receive the statuses (so they'd always be local-only).