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

311–320 of 655 posts

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

#311

Post by 3guk »

smt88 wrote: post #257
whoopdedo wrote: post #245

Earlier quoted context omitted.

A stressed out underpaid and overworked delivery driver is the last person I want in my garage. Verified deliveries are left at the wrong house, or the driver simply takes it with them after posting the porch picture. And I've seen boxes arrive that were forced open and the contents pulled out. But sure, it's the customers who are untrustworthy not the delivery people.

> A stressed out underpaid and overworked delivery driver is the last person I want in my garage. Same, but this is irrelevant to the point GP was making. Some minority of people do want Amazon Key (and similar services), and those people are now unable to claim their package wasn't delivered once they sign up for the service. Add those people up and you have something worth millions, even if there aren't many of the…

I fully suspect though that the people who do want Amazon Key and the people who are happily defrauding Amazon are not one and the same.

I realise that there are the porch pirates who are another issue entirely!

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

#312

Post by bluGill »

giancarlostoro wrote: post #182
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.

Why not... just allow HA receive callback events at that point when things change? I feel like this has an easy resolve that doesn't piss off your power user customers, and makes them encourage others to invest in your products, IE power users, and they'll come back because despite being a little extra engineering effort, they were glad you thought of them.

Because that would require them to build a callback system for the 0.2%. I don't have this, but I'm guessing the app only checks if your garage is open when you open the app. That is if you don't have the app open and someone opens the door you don't get a notification.

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

#313

Post by belthesar »

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…

One would think a reasonably decently written HTTP client with a server that responsibly responded with HTTP 429's when a client was polling too hard would be able to set a standard and enforce "good netizen" behavior.

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

#314

Post by efitz »

I wish I had known about ratgdo a few months ago. I spent a month trying to get a Meross smart garage door opener add on to work with the chamberlain that was already in my home, only to realize that the button was using some kind of obfuscated signaling, not just connecting the circuit. I ended up soldering a pair of wires to the button on the board in the button unit, and then connected my smart home stuff to those wires; worked like a champ. F** you Chamberlain; try blocking that.

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

#315

Post by dharmab »

traviswingo wrote: post #252
whoopdedo wrote: post #245

Earlier quoted context omitted.

A stressed out underpaid and overworked delivery driver is the last person I want in my garage. Verified deliveries are left at the wrong house, or the driver simply takes it with them after posting the porch picture. And I've seen boxes arrive that were forced open and the contents pulled out. But sure, it's the customers who are untrustworthy not the delivery people.

True. Delivery drivers consistently deliver to my neighbor instead of myself. The last three digits of our addresses are 885 and 855, and they consistently confuse the two. They’re tired, overworked, underpaid, and I honestly don’t blame them. But I wouldn’t trust anyone in my garage/home when I’m not home. Not sure why these companies think that will actually work.

I use it for expensive items. My garage door opener has an integrated security camera.

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

#316

Post by gosub100 »

lexh wrote: post #123
api wrote: post #25

Earlier quoted context omitted.

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 sp…

Oh, data collection. And subscriptions. This makes sense (and myQ’s privacy policy is a nightmare: https://www.myq.com/privacy-notice ) but I’ve never understood how this particular bit of data is valuable to anyone. Any ideas?

No direct experience, just my guesses

* someone who drives frequently may rank higher for automotive products and services

* use to independently rank other statistics, i.e. someone with kids probably comes and goes more than a single person or non-child-rearing couple. Take the dataset where you know they have kids (and myQ) and see if you can detect the ones with kids using only myQ data (plus other statistics). If it allows you to infer this property accurately enough, profit.

* Someone who comes and goes a lot is most likely not physically disabled, so exclude them from those specific marketing materials.

* someone who is home a lot (hardly ever opens their garage door) might like to spend money on useless gadgets, try selling them IoT toasters

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

#317

Post by dharmab »

seemaze wrote: post #268
traviswingo wrote: post #252

Earlier quoted context omitted.

True. Delivery drivers consistently deliver to my neighbor instead of myself. The last three digits of our addresses are 885 and 855, and they consistently confuse the two. They’re tired, overworked, underpaid, and I honestly don’t blame them. But I wouldn’t trust anyone in my garage/home when I’m not home. Not sure why these companies think that will actually work.

I've got an 80% hit rate at best across all carriers (in the US). I'm constantly trading mail with my neighbors due to mis-deliveries. It's a good thing we now have the option to go mostly paperless for important documents at least..

Heck, I get food misdelivered to me at times! I might as well be a last mile delivery service

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

#318

Post by efitz »

beeboobaa wrote: post #261
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…

Why would any of those monetization strategies require fucking over your customers like this? How are they incompatible?

They are afraid a potential partner will use the automation meant for customers.

This is just more enshittification in order to exploit revenue channels other than direct sales.

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

#319

Post by dharmab »

codeTired wrote: post #305
whoopdedo wrote: post #245

Earlier quoted context omitted.

A stressed out underpaid and overworked delivery driver is the last person I want in my garage. Verified deliveries are left at the wrong house, or the driver simply takes it with them after posting the porch picture. And I've seen boxes arrive that were forced open and the contents pulled out. But sure, it's the customers who are untrustworthy not the delivery people.

Have you seen Walmart advertising delivery to your refrigerator? Absolute insanity.

Actually, this would be cool for say a fridge in a mudroom...

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

#320

Post by epcoa »

beeboobaa wrote: post #261
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…

Why would any of those monetization strategies require fucking over your customers like this? How are they incompatible?

Who here claimed it was, they literally said it was “ill conceived”
Post reply on HN