Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Home Assistant blocked from integrating with Garage Door opener API

home-assistant.io

Post reply on HN
Print view View original

171–180 of 655 posts

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

#171

Post by cogman10 »

sarchertech wrote: post #89

Any IOT device that requires the cloud for functionality is a trap. I bought a Miku baby monitor specifically because of the 2 devices that offered a feature I wanted, Miku had no subscription fees. And they advertised that they never would. It cost $400. Then they went bankrupt and during bankruptcy they sent out a proposal to start charging for previously free features. Then they retracted that proposal. Not sure i…

Sounds like bait and switch to me, which is illegal.

You can report this action to the ftc https://reportfraud.ftc.gov/#/

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

#172

Post by duxup »

mikeryan wrote: post #170
TeMPOraL wrote: 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…

I have a MyQ door opener (and home assistant) This is bullshit. Their app is bloatware that they use to try to push additional services like Amazon home delivery etc. I mean it’s just a button, that’s all it needs to do. I’m going to replace it with one of the recommended devices. This is such an overt money grab.

I have the MyQ app (iOS).

I don't mind it at all. App works, fairly fast, the stupid extra stuff is just a chunk of the screen I can ignore / don't have to do / interact with.

I don't approve of the API situation but the app itself doesn't feel particularly bad.

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

#174

Post by mikeryan »

lvh wrote: post #127
a254613e wrote: post #90

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.

A third-party hub would have a similar problem, though, right?

MyQ has built in integrations for Apple Smart Home and Alexa. I’m assuming in those situations the MyQ app passes state to those services so they don’t have to poll.

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

#175

Post by op00to »

lvh wrote: post #132
op00to wrote: post #60

Earlier quoted context omitted.

You can just use a relay to open and close the door if that’s all you want. Edit: no you can't, if it's the fancy one. You gotta hack a switch like this: LiftMaster 883LM Security+ 2.0 MyQ Door Control Push Button

Sort-of: the newer ones require the physical button to speak the same rolling code protocol the remotes do. So, yes: but you have to modify a real door opener. ratgdo has the advantage that it pretends to be said door opener.

bummer! i had no idea it wasn't just a dumb switch! also super cool that they reverse engineered it. :)

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

#176

Post by jpitz »

lvh wrote: post #132
op00to wrote: post #60

Earlier quoted context omitted.

You can just use a relay to open and close the door if that’s all you want. Edit: no you can't, if it's the fancy one. You gotta hack a switch like this: LiftMaster 883LM Security+ 2.0 MyQ Door Control Push Button

Sort-of: the newer ones require the physical button to speak the same rolling code protocol the remotes do. So, yes: but you have to modify a real door opener. ratgdo has the advantage that it pretends to be said door opener.

There's often a pair of pins on the internal board that you can attach a relay to. Shorting the pins causes the door to close.

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

#177

Post by vetinari »

PinguTS wrote: post #160
vetinari wrote: post #108

Earlier quoted context omitted.

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.

What does "any registered company/school/university address" mean?

Some years ago, I activated some Office licenses using my company email; we never did any hosting with O365 or whatever was it's predecessor, and at the time, everything went fine. All I had to do was to create live account using that email address.

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

#178

Post by achandlerwhite »

mikeryan wrote: post #174
lvh wrote: post #127

Earlier quoted context omitted.

A third-party hub would have a similar problem, though, right?

MyQ has built in integrations for Apple Smart Home and Alexa. I’m assuming in those situations the MyQ app passes state to those services so they don’t have to poll.

Not for HoneKit unfortunately. They did sell a separate -$100 box that would bridge it officially but have discontinued it.

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

#179

Post by Spivak »

ranting-moth wrote: post #70

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

As much as I want this to be true I kinda doubt it. People who install and configure home assistant are far and away niche users. Almost everyone with one of their products will just use a physical clicker or pair it with their car directly.

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

#180

Post by thecapybara »

lhamil64 wrote: post #152
ryukoposting wrote: post #116

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

If I recall correctly, Chamberlin had an optional accessory that added HomeKit support to garage door openers, and that was discontinued last year. Home Assistant is capable of acting as a HomeKit hub, allowing it to control HomeKit compatible devices locally that otherwise would've required a cloud connection.
Post reply on HN