Live data from Hacker News

Home Assistant blocked from integrating with Garage Door opener API

home-assistant.io

91–100 of 655 posts

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

#91
post #32

Earlier quoted context omitted.

You can access the device when you're away from home if it's internet connected. Of course, the server doesn't need to be doing much besides proxying connections.

And of course, you can easily run a VPN/Tailscale/ZeroTier/whatever to achieve the same without the downsides.

I refuse to use cloud services, and I use tail scale, but telling the average consumer to do this instead of using whatever app came with the device is not going to work for most people

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

#92

Earlier quoted context omitted.

Some government agency could be doing the escrow, at no charge to the company.

There is still a process cost to participate in any escrow process, both on an initial and on-going basis. (That's before the blindingly obvious observation that even something provided by the government at no cost at point of use has a cost which is ultimately borne by the people.)

I don't disagree with either statement, but I think both of those are a price worth paying to avoid having hardware become e-waste because software support was stopped.

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

#93
We have nutriscore labels, excessive sugar labels, "smoking kills" labels...

Why not "This device does not support local cloudless control" and "This device does not allow 3rd party software access" labels too

Garage opener is a 10+ year device, expecting the company/cloud service to survive for that long and still be supported is too optimistic, but local control will still be usable, even if some 'adjustments' are needed.

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

#94
post #53
post #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 i…

> https://github.com/make-all/tuya-local Just a small warning: make sure to check whether your device needs to be added to the Tuya cloud to get a local API key. I was only able to get "my" lamp working locally after registering it via the app and creating a developer account. Another option can be flashing it with Tasmota: https://tasmota.github.io/docs/Tuya-Convert/

Thanks for that clarification, I also couldn’t remember the name of Tasmota.

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

#95
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…

Unofficial IoT software and integrations are not (much?) better. I wouldn't be at all surprised if this was partly due to a junk integration for this device cobbled together by an amateur and replicated by thousands more amateurs into their own ginormous pile of other junk YAMLs.

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

#96
post #32

Earlier quoted context omitted.

You can access the device when you're away from home if it's internet connected. Of course, the server doesn't need to be doing much besides proxying connections.

And of course, you can easily run a VPN/Tailscale/ZeroTier/whatever to achieve the same without the downsides.

> easily

Not for the average consumer.

I actually have gotten to know a lot of folks who are massive into home automation, who also know precisely fuck all about computers or whatnot.

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

#97
I'm not clear if people are really replacing a physical something here, but if you have an old smart home device which sucks, be sure to put it up on online marketplaces.

List it cheep along with a warts and all discussion of it's problems. Means less waste as there's always someone who'll want it, people who are looking for the product hear about the limits upfront, and the company actually gets a real loss from you leaving (assuming it sells to someone who might have bought a new one).

Plus it's fun to try to convince enquirers why they shouldn't buy your item

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

#98
post #77

FYI if you want smart things that are not yet limited by this bs decisions, afaik IKEA products are pretty neat

Yepp, I have some IKEA buttons and they are just Zigbee devices. They also sell lamps etc., mostly Zigbee based from what I remember. For the Germans (maybe other countries as well): The Lidl smart home things are nearly all Zigbee based. So far no problems with them and they are, IMO, reasonably priced. I somehow trust Lidl more to not burn my house down than random Amazon sellers. They also sell a Zigbee gateway th…

Zigbee in general is great. If you want the more expensive stuff, Philips is the leader in that.

And now that Matter support is slowly trickling in, they should all be fully interoperable. Currently it's touch and go if a Ikea bulb works well with the Hue hub for example.

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

#99
post #15

Based on my local big box store and garage installer availability, Chamberlain has a de facto monopoly. They also pulled the rug out from under customers: that behavior had been in Home Assistant since 2017, and it's their own recent changes that caused the alleged "DDoS". They say it's to promote official products, but the company previously had a local hub that didn't require their cloud service and discontinued it…

That project looks great! Now the issue is finding a Chamberlain or Liftmaster opener without myQ built-in. Or maybe I just don’t have to activate it.

Odds are that whatever nice Chamberlain opener you want will have myQ built in because that's their business strategy. You can try getting a different brand if you're voting with your wallet -- but if all you care about is security: the Cloud connectivity is optional and you can just not connect it to WiFi.

The ratgdo is more trustworthy, and it just connects (really easily, too, especially with the new v2.5 board) to the opener via the same contacts that the dry contact button does.

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

#100
Honestly smart features in large/permanent appliances is something I explicitly avoid these days. The majority of smart home products I’ve bought over the last ten years have been somewhat disappointing if not outright rage inducing. I don’t want that in something that is difficult or expensive to replace.

I sort of have to assume in the case of large appliances that the manufacturer will drop support for it well before I want to replace it, and that if there is any sort of functionality fully gated behind an app, that it will become unusable to me at some point when I reset my phone and discover they’ve unpublished the app from the store.

I’d much rather buy a dumb garage door opener and bolt on that ratgd device mentioned in this post, than be beholden to the manufacturer’s whims and invariably godawful garbage horrible no-good app.

Post reply on HN