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

381–390 of 655 posts

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

#381

Post by op00to »

juahan wrote: post #235
op00to wrote: post #58

I built my own HA integration with a tilt sensor and a relay to trigger the button. I have a camera on the door, I wonder if I can use that to validate the switch. I normally leave it disconnected from the switch because I don’t need to open the door remotely and I am afraid that some exploit will have a Russian 13 year old opening and closing my door at 4am.

I have my Home Assistant completely local, if I need to access it from outside, I open Wireguard VPN to my local network and do my business in Hassio locally.

Oh my Hassio has no open ports to the internet, but I sleep better knowing no one can open my garage from another country.

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

#382

Post by judge2020 »

SoftTalker wrote: post #352
Nextgrid wrote: post #328

Earlier quoted context omitted.

But that can be achieved by giving the retailer a one-off access code/secret which will be handed to the delivery driver by the retailer's company? At no point does "preventing random people in your garage" required a greedy middleman in the path between you and whoever you want to give your garage door access code.

Many people already have a keypad mounted outside that will open the garage door. You can set up a guest code there and give to Amazon, or anyone you want. There is zero need for internet-enabled smartness in the garage door opener here.

Okay, but the adoption rate of "let me create a code for my packages and give it to the Amazon person" is perhaps two or three orders of magnitude lower than if Amazon shows a bunch of call-to-actions for "link your myQ account for secure deliveries".

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

#383

Post by judge2020 »

xxpor wrote: post #343
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…

If anything, Chamberlain should be paying Amazon for the right to be included with Key. It drives sales to Chamberlain.

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.

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

#384

Post by kube-system »

judge2020 wrote: post #383
xxpor wrote: post #343

Earlier quoted context omitted.

If anything, Chamberlain should be paying Amazon for the right to be included with Key. It drives sales to Chamberlain.

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.

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

#385

Post by sneak »

bluGill wrote: post #284
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…

For retailers I want someone to verify that they are legitimate. I don't want random people in my garage. If someone enters my garage when I'm not home they better really be agents for WalMart/Amazon/target/UPS (as opposed to WolMort/Amozan/targit/USP...) , and whatever company does that does background checks on drivers. Probably they also need to have other cameras in their vehicles so that drivers trying to steal…

Background checks don’t ensure trustworthy staff, they just select for only criminals who are slick enough to not get caught doing crime, or criminals who haven’t been caught yet. Their effectiveness is overstated.

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

#386

Post by paulgerhardt »

cptcobalt wrote: post #282
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 know it's a distraction and orthogonal to your point, but your statement of a "key fob for your Tesla for $300" is fallacious and incorrect. Tesla uses Phone Key with with the Tesla app as your primary method of unlocking the car, with a $20 NFC card as fallback, and the limit of paired phones is above any practical real-world use. If you want a keyfob as a status symbol, it's $175. (Mine is a desk ornament, it doe…

Since you noted it, it’s actually very much part of my point. Tesla engages in price segmentation for replacement key fobs because they have key control. Perhaps even more aggressively than most other automakers short of VW Group. When done well it’s invisible to the user. I suspect by your (polite) comment that you may not be aware that’s going on here.

Premium users pay $300 to replace the fob on their Model S / Model X. Mid users pay $175 to replace the fob on the Model 3 / Model Y. And an entry level option exists for the cards. Plus programming fee. Handling fee. Local taxes. Processing fee. Etc :-)

Without control of their PKI anyone could self program a replacement for a few dollars as is the case with the garage door market.

As an aside, I find the fob useful for booting the car up prior to getting in, rather than waiting 40 seconds before the fly-by-wire shifter starts responding to commands to put it in gear.

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

#387

Post by veleek »

SoftTalker wrote: post #352
Nextgrid wrote: post #328

Earlier quoted context omitted.

But that can be achieved by giving the retailer a one-off access code/secret which will be handed to the delivery driver by the retailer's company? At no point does "preventing random people in your garage" required a greedy middleman in the path between you and whoever you want to give your garage door access code.

Many people already have a keypad mounted outside that will open the garage door. You can set up a guest code there and give to Amazon, or anyone you want. There is zero need for internet-enabled smartness in the garage door opener here.

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.

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

#388

Post by kube-system »

api wrote: post #25
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…

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…

> Why in the hell does a garage door opener need a server?

Because the user is almost certainly installing the device behind a NAT with a dynamically assigned public IP. These are mass-market garage door openers, not devices targeted to those familiar with advanced network configuration.

I also avoid cloud connected IoT stuff. I have the luxury of doing so because I have IT skills. For those who do not, accessible alternatives simply don't exist.

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

#389

Post by function_seven »

dharmab wrote: post #319
codeTired wrote: post #305

Earlier quoted context omitted.

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

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

What's old is new again!

https://www.core77.com/posts/103681/When-Houses-Had-Built-In...

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

#390

Post by EMIRELADERO »

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.

Couldn't people do some reverse-engineering to figure out the first-party protocol and impersonate the official app in the API integration?
Post reply on HN