Live data from Hacker News

Home Assistant blocked from integrating with Garage Door opener API

home-assistant.io

151–160 of 655 posts

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

#151

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...

TBH, that's better, as that is a problem that could be fixed. Even if we had to switch to a tilt sensor and just retain control, that'd be much better than their approach.

IOW, this real reason is better than their dumb comment about "unauthorized use".

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

#152

Earlier quoted context omitted.

The main reason why HA accounted for so many requests is probably because it was a polling integration, requesting data every 30 seconds from the server, while the official app either had push events when something changes, or it updated state when the app gets opened.

Isn't the high road solution here to open your API to enable users to make a less shitty HA integration? Either way, they'll almost certainly pull the plug on this service sometime before the end of the decade.

Or open up a local API so Home Assistant users don't even need to hit their servers in the first place, which is preferable anyway...

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

#153
post #18

Earlier quoted context omitted.

The cloud is some one else’s computers and internet. That internet connection for cloud services for smart gear always costs someone. Smart home devices that can’t be locally hosted or easily made to be locally hosted should be avoided. There’s no reason a light switch that normally works for 10-20 years will only work for 2-5 due to cloud connectivity. Luckily for the time being a lot of the providers can be reflash…

Agree with you overall, while adding a note that light switches normally work for far, far longer than 20 years .

Extremely fair comment that light switches normally work far longer than 20 :)

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

#154
post #106

Earlier quoted context omitted.

That helps, but a remote integration doesn't _have_ to be hostile. I get that it's different from IoT, and most of my stuff is local Zigbee after learning the hard way, but my Home Assistant also talks to the Norwegian meteorological institute and Tailscale :) One reason this is tricky to do is because up until let's say the last 6 months or so, myQ _wasn't_ hostile, even if it was Cloud-based. (I get that that align…

All remote are more potentially hostile than any local will ever be.

Yes, but some can't be local. For instance an integration that scrapes news from a website.

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

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

Can someone post the endpoint it is trying to reach for “research” purposes?

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

#156

Earlier quoted context omitted.

Isn't the high road solution here to open your API to enable users to make a less shitty HA integration? Either way, they'll almost certainly pull the plug on this service sometime before the end of the decade.

Or open up a local API so Home Assistant users don't even need to hit their servers in the first place, which is preferable anyway...

I was just going to comment this. The device is network connected anyhow. So just open up the local api.

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

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

> - Home Assistant users are power users, thus more likely to actually use the devices in question; >50% traffic from 0.2% of the users is far too big of a discrepancy to just explain it away with powerusers. Customers too have to follow a fair level of usage. > designed to discourage effective use (while maximizing data collection). What valuable data can they collect, if nobody is using it?

“Valuable Data” doesn’t have to be valuable but can be valuable anyway if investors and other partners believe it is.

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

#158

Earlier quoted context omitted.

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

I'm quite confident my parents and the many people like them in the world would not find running VPN/Tailscale/ZeroTier to be "easy." Nor would they have any idea how to troubleshoot when those services have issues. Nor would they want to play intermediary between Tailscale and myQ customer support to figure out which one is broken and fix it. Having options like this is great for powerusers, but the vast majority of…

They can just pay for home assistant cloud?

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

#159

> We understand that this impacts a small percentage of users, ... Wow, what a contemptuous statement. I have news for you, Chamberlain Group. You are not only alienating, being hostile and losing a "Small percentage of users" (most companies would prefer to call them "valued customers", but I get it). You are causing an enormous permanent damage to your own brand.

This is the own goal that Intel did with their Pentium FDIV bug. They were absolutely correct that it only impacted a small percentage of users. They still ended up losing their shirts over the problem.

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

#160
post #34

Earlier quoted context omitted.

There are lots of devices these days that rely on cloud infrastructure, like Apple devices, Teslas. Its becoming more devices. The same for software. Even Microsoft is going fully Cloud. Just had problems to activate my MS Office for Mac Business 2019, which I bought in physical. They now require on @outlook.com email address to be able to activate. Otherwise I can't use my "box" software.

They require Microsoft account, not an outlook.com address; though that address is an easy way to get the account. It is used for activation/license management, one nice feature is that you can yank a license on a dead device and use it with your new one. Outside of activation, it is easy to use MS Office for Mac completely offline -- there's a checkbox for that in preferences. You will lose some marginal functionali…

Nope, a Microsoft account is not enough. It must be an @outlook.com address, or any registered company/school/university address.

It took me almost 3 days to find the problem. Microsoft changed that and between all "answers" there is only one single thread in the Microsoft forums that had the solution.

Post reply on HN