←back to thread

280 points RyanShook | 2 comments | | HN request time: 0s | source
Show context
briHass ◴[] No.45145753[source]
I got burned recently by Ecobee in the same way. The problem with 'smart' interfaces for traditionally mechanical devices is that the useable lifetime (support period) of low-end microprocessors and software, especially online APIs, is often far shorter than the mechanical device it's attached to.

Similar to how people that keep cars around for 10+ years are stuck with dated and worthless 'infotainment' systems, Google and Ecobee can't even honor their product for long enough to outlast the HVAC units.

What burns me is that it wouldn't be much of an ask for them to push one final (optional) update that would open LAN-only access to core functionality. I and many others in the HA/ESPHome community have written hardware integrations to devices over RS485/UART with unpublished/black-box protocols, so a simple HTTP API would have an integration within days.

It would maybe cost an engineer at Nest/Ecobee a day or two of work, and the goodwill would make me far more likely to purchase a newer model. As it is, I've committed to avoiding (where possible) devices that aren't local-first.

replies(11): >>45145799 #>>45145931 #>>45146011 #>>45146180 #>>45146556 #>>45146647 #>>45146754 #>>45146922 #>>45147255 #>>45147650 #>>45150597 #
1. throwaway2037 ◴[] No.45146754[source]

    > LAN-only access
Serious question: What does this mean? I'm such a dumbo about networking. Is it simple for an app to distinguish between "LAN" and "WAN" network requests?
replies(1): >>45146874 #
2. RHSeeger ◴[] No.45146874[source]
I assume it means

- You connect directly to the device to tell it what to do

vs

- You connect to some service at google/whatever that then tells your device what to do.

The former still works after google/whatever decide not to support/host the service that handles that.