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

481–490 of 655 posts

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

#481

Post by dheera »

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.

Why not you and your neigbor just give your address as

Big pink house on Foo St. (#8-5-5)

or

Big red-and-yellow-striped house on Foo St. (#8-8-5)

or whatever colors they are? If they are the same color, repaint one of them.

As a bonus, this will completely throw off all the automated data brokers, idiots that use "KYC" as an excuse to want to know where you sleep, etc.

Alternatively put an apartment number on your house (there will be only one apartment, of course.)

One of you will be

855 Foo St. Apt. 1

The other will be

885 Foo St. Apt. A

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

#482

Post by NavinF »

CodeWriter23 wrote: post #396
veleek wrote: post #387

Earlier quoted context omitted.

You’ve glossed over the most complicated part of this: “give it to Amazon”. There are so many things involved in that portion of the process that an internet enabled garage door solves, most importantly: not having a single code that can be used by anybody at any point in time until I manually go back and remove it.

If only there were some kind of information processing device that could automatically expire codes after a set period of time.

You still need an API for getting new codes. If you're willing to switch apps and manually generate a new code every time you order something online, you likely don't order often enough to be relevant to any e-commerce company

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

#485

Post by UberFly »

russell_h wrote: post #231
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…

Came here to plug ratgdo as well - mine is supposed to arrive today! And he should definitely charge more.

Glad you all mentioned it. I'm ordering today. Hope they don't run out. :) HN cometh.

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

#486

Post by seanalltogether »

jasonjayr wrote: post #451
seanalltogether wrote: post #416

Earlier quoted context omitted.

I don't disagree with you, since the company I work for supports both local network access to their devices as well as cloud access for when you are outside the home. But supporting both does not simplify business logic, it increases complexity. It introduces more states and failure points that your firmware devs and app devs need to account for.

I appreciate your response, and don't want to go too far off the thread here, but as a software developer/architect myself, how can that possibly be true? The state of the environment that the IoT device is sensing or controlling, has to match local reality. Therefore, the state that's actually on the IoT's MCU is the true state that matters. (Any state stored cloud-side could be stale if the MCU is disconnected, or…

Aside from all the small added complexities of swapping between local http polling vs mqtt pub/sub for both apps and devices, the big complexity is managing authorization. Think about how simple the device firmware gets to be if the only access pattern is a single secured mqtt channel for processing commands. Anything coming down that pipe comes from a cloud provider that has already negotiated who can and can't send those commands. When you open up local access the device itself now needs more code to manage authorization and all the attack surfaces that come along with that.

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

#487

Post by singleshot_ »

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…

I am suspicious of the idea that fraud could somehow be reduced by allowing gig workers access to the interior of my home. Somehow this seems an awful lot like a multibillion dollar company offloading work on me.

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

#489

Post by ordu »

gambiting wrote: post #475
fshbbdssbbgdd wrote: post #444

Earlier quoted context omitted.

> and now I sometimes get delivery drivers getting pissed off at me (for some reason) that the code doesn't work after they ring my doorbell Since Amazon clearly has no idea what they are doing, I would put up a note next to the keypad saying “Amazon drivers: just drop the package, there is no code”

As if amazon drivers read the notes. I once left a giant note saying in capital letters "DO NOT RING DOORBELL, SLEEPING BABY AT HOME" and of course the absolute knobhead from Amazon had to ring the doorbell. Literally never shouted at anyone in my life before this.

You see, a note may not prevent amazon drivers from doing what they do, but they lose their moral ground. Now they can be shouted at if they rang a doorbell or tried to use a code for a garage door.

No more anything like this "I sometimes get delivery drivers getting pissed off at me (for some reason) that the code doesn't work. You can cut into any their speech with "English, m****r, do you read it?".

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

#490

Post by [deleted] »

ajross wrote: post #479
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…

> go to the dealer to buy a replacement key fob for your Tesla for $300 and not eBay for $5. Off topic, but FWIW: Teslas don't in general use fobs (maybe you get one with an S or X?). You can buy one for $175 if you want, but in general the primary unlock mechanism is the app on your phone, with the effective root of trust held in an RFID wallet card (of which you can buy extras for $20 each).

[deleted]
Post reply on HN