Live data from Hacker News

Home Assistant blocked from integrating with Garage Door opener API

home-assistant.io

21–30 of 655 posts

Re: Home Assistant blocked from integrating with Garage Door opener API

#22
I use Home Assistant and have this openner. My installer recommeneded it because he’s had happy customers like me who use home automation. I can tell you that I a) will never recommend or buy the brand again, and b) have already complained to my installer about his recommendation of this line (and he is moving to another brand).

I wish ratgdo a ton of success and have several on order.

Re: Home Assistant blocked from integrating with Garage Door opener API

#23

Here's the company's statement, which they've updated to accuse HA of, basically, DDOS: https://chamberlaingroup.com/press/a-message-about-our-decis...

As they themselves admit in that statement: There used to be an official way to integrate locally, but they discontinued it (myQ Home Bridge) and they're hard to find today (inc. huge markups when available).

Re: Home Assistant blocked from integrating with Garage Door opener API

#25
post #7

From company statement: > Our customers rely on us to make access simple without sacrificing quality and reliability. Unauthorized app integrations, stemming from only 0.2% of myQ users, previously accounted for more than half of the traffic to and from the myQ system, and at times constituted a substantial DDOS event that consumed high quantities of resources. Yeah, that sounds plausible, because: - Home Assistant u…

The problem is that these require some kind of server. Get one that just talks to HA over your local network.

Why in the hell does a garage door opener need a server?

Oh, data collection. And subscriptions. Nothing for the user.

I avoid any home automation thing that has any cloud backing that's not strictly optional. It's a strong anti-feature. In home stuff cloud means it won't work when the Internet is down, it spies on you, and it can become a brick or start requiring a subscription at any time.

Re: Home Assistant blocked from integrating with Garage Door opener API

#26
post #16
post #6

can we just make non-sens like that illegal no one has time for it you bought the device you should own it it's not even anything fancy where you could argue that continuous software updated need to be done or similar also pass a law that all smart home devices had to go through a hub, no direct internet connection allowed, uh put it under "reducing DDOS potential due to long term issues with internet connected smart…

> all smart home devices had to go through a hub I fully agree, this is the reason I mostly buy Zigbee devices for my smart home. The problem with this rule is that there is already a device on the market that complies with it on paper, but not how you intended: Amazon Echo devices act as Zigbee gateways. While I never tried it, I bet it will not turn on your lights without calling the mothership. If this rule were t…

> If this rule were to become reality, vendors would just sell your their "mandatory" hubs that handle the calling home part. Smaller vendors would no longer be able to offer their ESP based devices, even though I can easily decloud them via ESPHome etc, if even necessary.

No, what should become the reality is that only HARDWARE vendors that make a living off the hardware and some corollary service will have the incentives to be on the market, instead of the behemoths like Amazon or Google that just want to harvest your data with mostly loss leader products.

Re: Home Assistant blocked from integrating with Garage Door opener API

#27

Is this "myQ ecosystem" the only way to interact with these garage doors? i.e. is there no way to communicate with them without involving the manufacturer's server?

You can buy little ESPHome devices that will speak it’s local serial protocol and control it. (And then link to them how you want)

It’s incredibly annoying and dumb and I now have to get some. grumble

Re: Home Assistant blocked from integrating with Garage Door opener API

#29
One extra step I’ve learned to follow is to verify if needed, could the hardware be permanently redirected to a local server, and worst case reflagged with a different firmware or it can be redirected to remain local. The latter is sometimes easier if it’s a Tuya based device, which a lot of these unknown devices are.

https://github.com/make-all/tuya-local

One of the main things these “smart” devices do is use your internet connection. It’s wise to create a dedicated _IoT suffixed wifi which can’t access your network or devices, but at the same time your other devices can ping them.

How?

This is a pretty solid guide of a home network setup here. It can be running a $50 EdgeRouter X or translated to other devices.

https://github.com/mjp66/Ubiquiti/blob/master/Ubiquiti%20Hom...

Edit: comments below have additional info on Tasmota and ESPHome

Re: Home Assistant blocked from integrating with Garage Door opener API

#30
post #6

can we just make non-sens like that illegal no one has time for it you bought the device you should own it it's not even anything fancy where you could argue that continuous software updated need to be done or similar also pass a law that all smart home devices had to go through a hub, no direct internet connection allowed, uh put it under "reducing DDOS potential due to long term issues with internet connected smart…

> also pass a law that all smart home devices had to go through a hub, no direct internet connection allowed, uh put it under "reducing DDOS potential due to long term issues with internet connected smart home device security"

Assuming no authentication/encryption/intentional obfuscation shenanigans (which would need to be covered), I don't really care if it is forced to go through a local hub if only they were required to provide an easy mechanism for pointing the device at a local network endpoint.

Post reply on HN