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

421–430 of 655 posts

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

#421

Post by kkielhofner »

deadbunny wrote: post #402
kkielhofner wrote: post #283

Earlier quoted context omitted.

At the end of the day this is a very reasonable business decision - an incredibly obvious and easy one. Chamberlain/myQ makes very low cost (likely loss-leader) mass manufactured devices. Like anything else if you can identify 0.2% of your users leading to 50% of an issue you're having the reasonable thing to do (from a business perspective) is to just cut them loose. If this CTO or anyone at Chamberlain were to try…

> There are 275k active Home Assistant installations[0] Nit: That they know of. As you say it's a techy product and I would assume that techy types are the exact kind of people to turn off analytics.

Very fair but even if you multiply it by 10 the end result turns $1m for myQ into $10m - or 1.2% of their yearly revenue.

Order of magnitude higher, same point, same result.

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

#422

Post by borski »

jacquesm wrote: post #209
lvh wrote: 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…

I'm happy to not have one of their devices but if they did this after I had installed it based on the fact that it works with HA then I'd definitely sue them for breach of contract or whatever else I can think of or to get a full refund. What a shit move to pull on your existing customers.

It was $30. I highly doubt it’s worth it, unfortunately.

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

#423

Post by sangnoir »

LeifCarrotson wrote: post #404
kelnos wrote: post #292

Earlier quoted context omitted.

> as already pointed out, most people have an unlocked door from the garage to the house Not sure where you live, but every house I've lived in (USA, a few different states) during my entire life has had an exterior-quality door with exterior-quality lock, including deadbolt, between the house and garage. In the one house I lived in that had a security system, that garage-to-interior door was also wired into the syst…

My in-laws have this, but mine, my parents, my siblings, my wife's siblings, and my neighbor all have a big window in that door. And none of them are ever locked.

How old are those houses? They probably are not compliant with current building codes[1], many places require your garage doors (and ceilings) to have higher fire resistance than the rest of the house. In my experience, fire-resistance correlates to sturdiness in doors.

1. I know it's a broad generalization, also location-dependant

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

#424

Post by jollyllama »

kube-system wrote: post #391
iAMkenough wrote: post #145

Earlier quoted context omitted.

Sounds like there's a market for intermediary tech support

If your mass-market commercial product needs this by design, you will fail. To successfully sell a product to the general public, it must work out of the box.

True, but there's contractors for pretty much everything else that can be installed on your home. Why not home automation contractors?

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

#425

Post by [deleted] »

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…

[deleted]

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

#426

Post by [deleted] »

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…

[deleted]

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

#427

Post by SrslyJosh »

tech_ken wrote: post #280
paulgerhardt wrote: post #234

Partially responsible for this. (Sold Lockitron to Chamberlain in 2017 which became the basis for Amazon Key integrations.) Contrary to the popular sentiment in a lot of the comments here, there’s not much value in the analytics. As we all painfully found out in the 2010’s, there are only two viable recurring revenue streams in the IoT space - charging for video storage and charging for commercial access. Chamberlain…

So you're saying that retailers will pay Chamberlain to act as more or less a clearinghouse for package deliveries in my garage, and that in order to successfully operate this model Chamberlain needs to funnel all users through their proprietary channels in order to fully vet the delivery transaction? Or at least to prevent HA users from nibbling at Chamberlain's lunch with DIY equivalents? Do you think that they wil…

Bold of them to assume that I will trust a stranger with access to my garage.

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

#428

Post by staplers »

SrslyJosh wrote: post #427
tech_ken wrote: post #280

Earlier quoted context omitted.

So you're saying that retailers will pay Chamberlain to act as more or less a clearinghouse for package deliveries in my garage, and that in order to successfully operate this model Chamberlain needs to funnel all users through their proprietary channels in order to fully vet the delivery transaction? Or at least to prevent HA users from nibbling at Chamberlain's lunch with DIY equivalents? Do you think that they wil…

Bold of them to assume that I will trust a stranger with access to my garage.

They'll just monopolize garage openers like smart phones and you'll have 2 options both which will be hooked into the surveillance grid.

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

#429

Post by judge2020 »

kube-system wrote: post #384
judge2020 wrote: post #383

Earlier quoted context omitted.

Maybe? How many people are switching out their garage door specifically for Key? Every new home I've experienced has no choice for which brand of garage door opener they use, the builder has standardized to a specific brand and often only updates the model whenever forced to.

I suspect new homes are a only small portion of garage door opener sales.

What would beat it? Who is buying garage door openers?

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

#430

Post by lostapathy »

chewmieser wrote: post #341
bonestamp2 wrote: post #267

Earlier quoted context omitted.

It does suck, but can you still use it remotely via the myQ app?

MyQ app should work fine. Just not the API integration to MyQ.

The MyQ app sucks, though. Besides the dark pattern ad-forcing they do, I've also had the thing redraw while I was holding the button to open a door. Which meant the wrong door opened entirely - one that happens to be 20 miles from where I was standing. I have had this happen multiple times, it's ridiculous.
Post reply on HN