3 ms·
Has anyone tried Home Assistant to get around things like this? Or are you locked in proprietary technology anyways?
by Vaslo 7y ago
Has anyone tried Home Assistant to get around things like this? Or are you locked in proprietary technology anyways?
- Klathmon 7y agoThe APIs that Home Assistant uses (and can possibly use in the future) are the exact ones they are shutting down here.
- magicalhippo 7y agoHome Assistant can interface with many different services. I use it with Z-Wave and the (undocumented) cloud API for my A/C, as well as pulling some data from weather services etc. There are a lot of different Z-Wave devices for controlling lights, motors, heat, as well as sensors for motion, smoke, luminosity etc. Zigbee is another standard which can also be used with Home Assistant, which is mostly for lighting AFAIK. The way Home Assistant is written it's relatively easy to write a new service which exposes devices that can control or sense. Sensor readings and control is unified, so you can mix multiple platforms in your automation. You could have a Z-Wave motion sensor trigger a Philips Hue (Zigbee) light if the weather service (HTTP) tells you it's past sunset. You can check out the supported components here: https://www.home-assistant.io/components/ https://www.home-assistant.io/components/
- dusing 7y agoHASS won't get you around this shutdown, but it is a great solution to avoid these kinds of things. local server, local communication is a requirement for all the devices I put in my smart home. HASS does not tie you down to any manufacturer, just make sure the devices you add have local control.