Hacker News Reader

Comment by ryukoposting | Hacker News Reader

Isn't the high road solution here to open your API to enable users to make a less shitty HA integration?

Either way, they'll almost certainly pull the plug on this service sometime before the end of the decade.

Or open up a local API so Home Assistant users don't even need to hit their servers in the first place, which is preferable anyway...

I was just going to comment this. The device is network connected anyhow. So just open up the local api.

Haha this is the company that has an undocumented encrypted wire protocol between the wired button and the opener so you have to use their button instead of a normal doorbell switch.

If I recall correctly, Chamberlin had an optional accessory that added HomeKit support to garage door openers, and that was discontinued last year. Home Assistant is capable of acting as a HomeKit hub, allowing it to control HomeKit compatible devices locally that otherwise would've required a cloud connection.

I'm so glad HomeKit exists because without it I'm positive the vast majority of "smart" home devices wouldn't support any kind of local connectivity.

It sucks how many iot devices skip home kit integration for this very reason. :(

I would argue that letting HA define a callback URL or some way to receive those events instead of relying on polling would do it. But also, are they caching the responses? I have a weird feeling that the vendor is not caching enough, especially for data that changes insanely infrequently.

That’s definitely the high road solution. The low road solution would have been to start suing HA users under the CFAA. So I guess they took the middle road.

Reply on news.ycombinator.com