I’ve been running HA for a short while, admittedly not fully understanding the various nuances of the different installation methods, benefits, etc at first or completely even now. In the bigger picture, I’ve moved away from my VMs and big power hungry, heat generating and loud Dell R710 and R410 servers to smaller more efficient and smaller servers and converted all of my services to run containerized via Docker (Gitlab, GestioIP, Nagios, Smokeping, PowerDNS for Authoritative, PiHole, Prometheus, Rails Apps, and other sundry services, NodeJs, Postgres and my coding toolboxes). It’s saved me a ton of required resources needed to power a multitude of VMs and allows me to quickly spin up dev environments.
So I’ve got Hassio installed as a Supervisord install via Docker. The Supervisor->System tab reports that “
You are running an unsupported installation.” The Learn more link provides two additional links to learn about how to resolve two issues (Operating System and Network Manager). In searching the home-assistant forum to learn more about the current installation methods, it’s clear that there’s been much confusion about how, what, and why. I’ve spent the better part of an afternoon reading reams of posts discussing the topic. I ran across the two links below, the first from @jal5376 asking for some clarification and the second a suggested read from @tom_l which provides a table and description of the different methods and pros/cons.
I now want to make something more permanent as well as reliable/redundant. That is, I want to set up a High Availability deployment. I have ZFS and GlusterFS on my storage devices to give me the benefit of ZFS and GlusterFS’s distributed data benefits. I understand there are some gotchas when it comes to physical attached adapters (ZWave, Zigbee, Wyze adapters, etc). I’m not yet educated on if or how one can have multiple Z-Wave access point adapters, for example. I’m ok with having to physically move my adapters to other physical servers in the event one goes down. But having another system ready and waiting a the drop of a hat is big. And let’s face it, if my single Home Assistant installation dies and I loose control of opening the motorized front gate to my property, or other various imperative automations, that’s unacceptable. And I’m not ok with having to reinstall a complete OS, dependencies, etc to get up and running again. With Docker done manually, or with Kubernetes, redundancy should be able to be accomplished with haste. Even if deployment is a little clunky at first.
I realize there are varying opinions all based on levels of experience with Home Assistant, as well as experience in their IT careers with servers, OS’s, containerization, SysOps and services in general, etc.
I’m interested in some feedback and your thoughts to help me ferret out what might be the best and wise course taking from the experience of others who have walked a few miles down this road.