4 ms·

HASS makes it to the top of HN about once a month for good reason! Probably one of the most well developed open source projects I've seen, both from core contr

HASS makes it to the top of HN about once a month for good reason! Probably one of the most well developed open source projects I've seen, both from core contributors finding a way to get paid for what they do every day with nabu casa as well as a large and thriving community. Over the past two years there's been a ton of work put into making things more plug and play and GUI for folks, but all the technical wiring under the boards is still there for doing just about anything you want. I have basically everything off the cloud, except for a few things I want on there. If you want everything off the cloud you'd be wise to do a bit of research and get a zigbee and or zwave stick. Don't blame HASS for IoT providers that are routinely pushing up firmware that breaks anything that interfaces with their products without going through their cloud, but for most things there are things out there that work great without it.

Eduard 4y ago
My experience over the past six months of using Home Assistant is mixed. With every monthly update, something breaks, stuff gets deprecated, then removed. I report those issues, but they get quickly closed without being resolved.
- louis-lau 4y ago
  I just don't update home assistant monthly. Maybe once or twice a year? Tbh that seems to work super well. Never have to think about it and it just works.
  - int0x2e 4y ago
    My solution is similar - I read the release notes every month or so, and upgrade only if I am interested in some of the new features. I am willing to fix stuff if it breaks, and I have a backup config I can downgrade back if needed. I take a similar approach to firmware upgrades for my IoT devices - I run them on a couple of separate vlans, so I feel okay only updating them every few months when I see the need (mostly custom builds of tasmota/esphome/etc.) HA is not ready for grandma, but most technically inclined folks should be able to get a ton out of it after you get past the initial learning curve.
    - edelans 4y ago
      I recommend using the add-on "Check Home Assistant configuration" before every upgrade. I only upgrade when I get the confirmation from this add-on that nothing will break. The add-on actually download the new version and checks my config file against it. When something breaks, you get the error message so you can fix what's not working (happens once or twice a year for me, usually a config change), and relaunch the add-on to test again.

Eduard 4y ago

My experience over the past six months of using Home Assistant is mixed. With every monthly update, something breaks, stuff gets deprecated, then removed. I report those issues, but they get quickly closed without being resolved.

louis-lau 4y ago
I just don't update home assistant monthly. Maybe once or twice a year? Tbh that seems to work super well. Never have to think about it and it just works.
- int0x2e 4y ago
  My solution is similar - I read the release notes every month or so, and upgrade only if I am interested in some of the new features. I am willing to fix stuff if it breaks, and I have a backup config I can downgrade back if needed. I take a similar approach to firmware upgrades for my IoT devices - I run them on a couple of separate vlans, so I feel okay only updating them every few months when I see the need (mostly custom builds of tasmota/esphome/etc.) HA is not ready for grandma, but most technically inclined folks should be able to get a ton out of it after you get past the initial learning curve.
  - edelans 4y ago
    I recommend using the add-on "Check Home Assistant configuration" before every upgrade. I only upgrade when I get the confirmation from this add-on that nothing will break. The add-on actually download the new version and checks my config file against it. When something breaks, you get the error message so you can fix what's not working (happens once or twice a year for me, usually a config change), and relaunch the add-on to test again.