Moving to Hass.io - tips?

I have an existing setup running “regular” HASS on linux. Its on version .86. I’ve been having issues with the hardware so I’m giving Hass.io a shot. Just curious if there are any tips in the order I approach moving my config (or how I move it). I’m not as worried about the history data, just the config.

I want to take the opportunity to update/modernize my setup to be aligned the HA best practices.

More specifically:

  • I currently have my config in a structure with some top level yaml files and then referenced files in /config. Is this considered a good idea?
  • I started with lovelace in the beta phase and have a ui-lovelace.yaml - what is the preferred mechanism?
  • I currently use appdaemon for some relatively simple scripts, is that still en vogue?

Thanks!

I think I would personally start doing one version update at a time with my current HA setup fixing any breaking changes as they occur until I’m finally up to the latest version.

Then you can switch to hassio if you still want.

If you are updating to try to fix hardware issues then I’m not sure it will accomplish what you want switching to hassio since the underlying HA app is exactly the same between Hassio & non-Hassio HA. The only real difference is that hassio runs in Docker (which is a big benefit in itself but still won’t fix your hardware issues) and it offers add-ons that also run in Docker.

I will say yes because that’s what I do as well but that is usually user specific.

Generally you will gain benefits from splitting up the config.

I personally use yaml mode and like the control I have over it. Other people use the GUI editor. But I’m not sure what limitations it currently has. Yaml mode just always works.

seems to be…But I’m not sure it’s worth it to use it for simple things that can easily be done directly in HA.