3 ms·
Coincidentally, I spent this past weekend looking into this. This space is ripe for a well-funded new entrant to step in, create a decent protocol for home aut
by lelanthran 3y ago
Coincidentally, I spent this past weekend looking into this.
This space is ripe for a well-funded new entrant to step in, create a decent protocol for home automation and make a killing.
The options in this space are awful, with no clear indication of security, competing "standards" that don't cover even the basics of an appliance-like device, and cloud-lockin for almost everything!
Nothing is aimed at the average homeowner (No - writing in Python or Lua is not how people want to automate their home).
Lets talk about the media-level protocols: WiFi in homes is ubiquitious and cheap, things like Zigbee or LoRa raises the cost and the effort for HA, local RF isn't widely supported by devices (with good reason). How does a homeowner know what to go with?
Let's talk about bootstrapping a new device on the HA network: device discovery!
Some devices require an internet connection and the homeowner has to have an account on the cloud (Adafruit IO, various proprietary vendors). Some use a fixed mDNS name (Shelly), some require to download the vendors app (used to set network config, credentials, etc), most simply don't do it at all. I even found one or two that require the owner to browse to a particular local IP, because the device starts off in AP mode.
Okay, lets say you jumped through the hoops (registered an account on a cloud service, gave the device internet access, used its AP to set it up, or it set itself up doing mDNS query for _mqtt._tcp.local, or whatever).
Next problem: authentication of the device on the network. Some devices just don't support it, some support it using AES with pre-shared keys, some support it with basic HTTP auth over TLS, some use mqtt with TLS, some offer mqtt, but in plaintext only, with encryption being over HTTPS (reverses the pub/sub model horrifically), many support x509 certs loaded onto the device (the worst option for an appliance!), some (using CoIoT) have support for DTLS (But need a valid x509 cert) ...
Problems aren't over yet. So, you go with something ... and then find out that your controller is not compatible with one device. Maybe you need a Zigbee bridge because everything else is WiFi. Maybe that device requires x509 cert over WiFi, while everything else is using auth credentials. Maybe it's hardwired to use vendor's cloud and the rest of your network is using Home Assistant. Maybe it's using ESPHome and everything else is using CoIoT.
That's fine, you think, I'll just use Home Assistant, which has integrations for everything on the planet, to "bridge" the different protocols. But now you're stuck with Home Assistant as a controller, which has limited automation facilities.
Honestly, what homeowners want is to buy a device and plug it in, and have a nice interface for devices which allow the homeowner to specify what happens on any event.
That's it. No messing about with Python, Containers, Lua, mDNS sniffers, accounts on public internet clouds, renewing x509 certificates, etc.
Plug it in, use username+password to access the Home Automation network, that's it.
From a technical PoV, I can see a mechanism to get it done this way.
- philjohn 3y agoThat's what Matter is supposed to do, and why all of the various smart home vendors seem to be jumping aboard. To your point of "stuck with HA as a controller" that's not entirely true, if you're an Apple household, install the HomeKit bridge and expose things to homekit where you can automate to your hearts content.
- lacrosse_tannin 3y agoI did rich-people home automation as job for a couple years, like 7 years ago though. It's all broken. It sucks. There's no good graphical programming thing in existence. The A/V or HA people are not the people that are going to invent it.
- fragmede 3y agoYou're making it way too complicated on yourself somehow. You just go to Home Depot or Lowes or whatever, buy a device, plug it in, create an account in the whatever and connect it to your Siri/Alexa/Google. There's no Lua or Python in sight. No Raspberry pi home servers either. If you want to make it hard on yourself you can, but why would you? Home Assistant is fine, and means a less technical customer doesn't deal with and of that nonsense you're talking about. I'm sure there's things you can't do with it and for that you would need to be a programmer but if you just want to say"hey Google I'm taking a shower", and have it set the lights in your bathroom, and turn on the heater, or have it switch the lights to warm at sunset, or an hour before, that's totally possible.