I try to avoid all smart devices, but I moved into a house that already had "smart" garage door openers installed, so I thought I'd try the smartness. It is indeed ridiculous in that it requires an Internet connection to work. Here I am, with a remote control device (my phone) that is on my LAN and a garage door opener that is on my LAN, but I need to do a round trip to the Internet to communicate with it? What idiot designs these things?
There has been some uproar lately about a particular manufacturer shutting down access to the API used for their garage door openers to HA, I forget the name but there was a Q in it I believe.
The solution, as I understand it, is a little device which talks the protocol of the door opener that gives you fully local access the way it should be.
I'll try and dig out the link now in case it's of use to you.
I got one for my decade-old not-smart opener around the time the manufacturer was shutting down API access for their fancy new smart models. Works like a dream. Why would anyone want to spend $$$ buying a fancy new cloud-smart appliance when a simple little chip can make the old one local-smart?
Yea, that's the kind I've got. I solved the problem by simply not using or caring about the "smart" feature, since it's pretty pointless. Why would I even need to open or close my garage with an "app" when the button is right there by the door?
I don't have a garage door opener myself, but from what I've gleaned from US YouTubers is that they like to know the _state_ of the door, open/closed which is handy if you use home automation.
I imagine if you're driving into the garage from outside you have a physical button in the car with you to open it, and if you don't run home automation, the "automation" part is likely not very useful.
I like knowing if the door is opened or closed from remote. Kids sometimes forget to close the door, and it's reversed direction before because the tracks needed lubricated and it raised the door again after I had pressed the button.
Look at it from the vendor’s perspective. Most people still want to be able to access and control their home from outside their home network, which generally means going through a hosted server, so why go to the extra trouble of implementing a separate method for local LAN only when you could just use the same central server? It’s almost always the case that the local LAN can access the internet, so there’s not much incentive to make it more efficient.
Yes, ideally the local user should just hit the local hub directly, but it’s double the development effort for negligible benefit.
I agree there isn't much incentive, and this is where standardised local protocols like ZigBee, Z-Wave etc come in; I can buy the hardware I want and run it how I want and those who want simplicity can buy a local hub, which can cover the cost of the hosted servers I have no interest in.
Failing that, I'd settle for manufacturers adding an option in their app of wherever suitable, that will let me change the server URL and leave me to it, I'll reverse engineer then protocol, or if they're feeling generous they can open source or provide an API doc.
Unfortunately, my experience reverse engineering lots of devices over the years is that they're often sharing more than they should, and subsidising the devices they sell you with your data.
There is also an overwhelming number of hardware manufacturers who just have piss poor software with atrocious security who should probably be embarrassed to release their code.
We already know what it's like in home WiFi router world.
