The ratgdo says it work with “dry contact”… what does that mean?
Home Assistant blocked from integrating with Garage Door opener API
291–300 of 655 posts
Re: Home Assistant blocked from integrating with Garage Door opener API
#292Earlier 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…
> 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 system and arming it would treat it like an exterior door.
Having said that, I still wouldn't want random delivery people entering my garage without my knowledge.
Re: Home Assistant blocked from integrating with Garage Door opener API
#293Earlier 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 live in a townhouse and I _love_ the Key deliveries into my garage. I've been using it since it was a closed beta, and I haven't had a problem with it.
It provides a convenient service for both parties.
Re: Home Assistant blocked from integrating with Garage Door opener API
#294Any 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…
I had an internet connected baby monitor. In the end we decided to just get a local RF one and it is a far better experience. Pair it once, and it just works. Lower power. Very reliable. Coverage throughout the house without issue. No apps to crash in the background. No dropped streams. No needing to log in to the app. No worries about features getting taken away. No subscriptions. No having to send data out to the c…
I recently bought a baby monitor - or more specifically, spent a couple hundred € on Ubiquity hardware - two cameras, NVR/host, and a PoE switch - and made one myself, because that's the only way I know of (after serious research and asking on HN) one can buy a wifi-enabled baby cam in Europe, that doesn't route video through some sketchy cloud. Baby cam vendors, fuck you all very much.
Re: Home Assistant blocked from integrating with Garage Door opener API
#295Earlier quoted context omitted.
In US homes the garage is often a way to access the house with minimal security between the two.
That’s not true, the garage typically has a full outdoor door with standard security (dead bolts, wired into the security system) the same as any other door as the interface door between the garage and the house. This is a code thing for a variety of reasons but primarily because the outdoor door is weatherized and provides a barrier against CO, but also for the precise reason that the garage door is not considered s…
At least in my experience people are a lot more likely to leave the garage door unlocked than the front door, either intentionally or unintentionally.
Re: Home Assistant blocked from integrating with Garage Door opener API
#296Earlier quoted context omitted.
I agree as well, though I don't think we need to figure out all edge cases before the legislation is viable. All we need to do is allow any person who purchased said software a private cause of action in which they can petition a court to release the code. Then a judge could decide based on the merits of the person's need whether the code should be released or not.
I think that situation exists now , which is the essential root of the problem. It's too expensive and too unlikely to succeed, but I could sue Chamberlain now arguing that they have breached an implied contract and that the remedy I seek is for them to open-source their code.
I disagree; I believe any lawsuit brought against Chamberlain today would be dismissed for lack of standing. Further, even if it wasn't, I think you would have a very hard time convincing the court that open sourcing their code is a reasonable remedy.
Best case, I think you'd get your purchase price back. I'm not sure how you'd argue that remedy is insufficient, either - hence why my preference is to have the cause of action written into the law we're imagining here. It'd be even better if we can write in that the remedy for a degradation of the service is an open mechanism by which the user has sufficient level of control as to recreate their desired functionality.
Re: Home Assistant blocked from integrating with Garage Door opener API
#297Earlier quoted context omitted.
I prefer to have an e-waste law that says that if you stop maintaining the service, you have to open-source it :)
So they publish the crypto certificate that allows opening anybody's door?
Unless it's security by obscurity, releasing the source code of the entire infrastructure should never result in all systems becoming compromised. So, assuming the API is run over HTTPS with authentication tokens, Chamberlain wouldn't need to (and should under no circumstances) release its SSL certificates' private keys. Instead, the firmware and server infrastructure should be easily modified by the user to point to their own servers (or get rid of intermediate servers and directly be usable on the local network, which is the only good solution anyway).
Re: Home Assistant blocked from integrating with Garage Door opener API
#298Earlier quoted context omitted.
I prefer to have an e-waste law that says that if you stop maintaining the service, you have to open-source it :)
So they publish the crypto certificate that allows opening anybody's door?
If that exists, the company should be shut down for gross negligence, even before they go bankrupt.
Re: Home Assistant blocked from integrating with Garage Door opener API
#299Earlier quoted context omitted.
> - Home Assistant users are power users, thus more likely to actually use the devices in question; >50% traffic from 0.2% of the users is far too big of a discrepancy to just explain it away with powerusers. Customers too have to follow a fair level of usage. > designed to discourage effective use (while maximizing data collection). What valuable data can they collect, if nobody is using it?
> What valuable data can they collect, if nobody is using it? What permissions does the app have? If it has location data so it can open/close the garage door based on proximity, it can probably collect your location whenever the phone is on and that can be sold to data brokers. That's just an example. There is potentially a trove of information the app could collect and sell and not just when the user has the app op…
> What permissions does the app have?
"Location" (while using App) and "Notifications". So it can locate you when you trigger it, but it can't track you all the time.
Re: Home Assistant blocked from integrating with Garage Door opener API
#300Partially 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…
> If you want a keyfob as a status symbol, it's $175. (Mine is a desk ornament, it doesn't get used.)
The keyfob is super-useful. It fits perfectly into that small jeans pocket (that was originally meant for watches), so you can trigger the trunk/frunk opening without taking the fob (or phone) out.