![]() ![]() Example: if I bump up the low temp on my Venstar thermostat on the Home Assistant dashboard, Home Assistant will immediately set it back. I think to some extent this is an inherent problem in supporting a lot of devices that have crappy, non-standardized APIs. * A lot of the integrations seem half-baked or to not quite fit the generic Lovelace cards. I love that it has a real ecosystem and that it seems to have a decent HTTP/WebSocket API (that I just started playing with). Then there are additional docker-based add-ons you can install for stuff like MQTT, Z-Wave, Let's Encrypt, SSH access, nginx, and more. Write an image to disk as you usually would and you get a bare-bones OS with Home Assistant running in docker. Their supervisor/docker based install for Raspberry Pi is pretty slick. For example - I have Z-wave based motion detectors but I can control Hue lights and Wemo switches for motion detection - but only if I'm home as reported by the zone feature in their iOS companion application. It expresses everything from every integration as an entity in various device classes so as long as some random tech is supported by an integration you can group them seamlessly. The real power of HA is the rich integration ecosystem, the Community Store, and that it runs locally (more reliable and much faster for things like motion sensors, etc). It's pretty amazing but has a pretty steep learning curve (although they're getting better and better at this). Home Assistant is the best approach I've found for this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |