3 ms·
Not just Google, but the manufacturers themselves can often abandon product lines, or inadvertently break integrations with updates, or purposely stop a partner
by solardev 2y ago
Not just Google, but the manufacturers themselves can often abandon product lines, or inadvertently break integrations with updates, or purposely stop a partnership, etc. (like Sonos's years-long feud with Google over smart products). The ecosystem is as fragmented as Android, or worse.
I was all-in on the smarthome fad a few years ago, but so many things kept breaking that it just wasn't worth the complexity anymore. I went back to a mostly-dumb home setup again and things just work now, lol.
- packetlost 2y agoI've been happy with the stuff that is supported by Home Assistant. We really just need open protocols/standards and for manufacturers to stick to them. Unfortunately there's not much incentive for them to do that.
- loudmax 2y agoGetting my Nest thermostat to work with Home Assistant was a lot of work. I had to register a developer account and authorize obscure permissions deep inside some Google permissions structure. I suppose if it's all straightforward you habitually develop on Google's infrastructure, but as an outsider none of it was clear. Still, better than nothing. Hoping that Google actually stays committed this time.
- Marsymars 2y agoBy far the easiest way to integrate Nest products into a non-Google Home-based setup is with a Starling Home Hub. Starling integrates either directly to HomeKit, or to Home Assistant via HomeKit Controller.
- isatty 2y agoBeen on HomeKit and devices compatible with it for >5 years and I’ve not had any issues except maybe when there was the migration to thread(?).
- solardev 2y agoIs HomeKit the Apple version? I feel like they're much better about their integrations than Google's PC-like OEM strategy.