Actually as simple as you sharing the code already give tons of help… just need to change the directory. It should be simple too… wondering why HASS.core sound very difficult to install with its addon…
In my case the most important addon:
portainer
watchtower
influx
grafana
motioneye
tasmoadmin
MQTT
ESPHome
I install NGINX + certbot + docker + docker compose + glances using apt install and which is much flexible in terms of installations. Furthermore someone can also create a simple bash script to help this if needed. I install glances on my host OS just because I want to get the host info and not the docker info.
that would essentially mean a rewrite of supervisor, because it’s exactly what it does. And some more. Supervisor does that, yes, plus it handles all the updates and upgrades, of HA AND of all the add-ons. Perhaps it’s a good idea to seperate all this functionality to keep things simple and manageable and maybe this can prevent the devs from having a burn-out. Just an idea…
Just had a quick look. Looks good, but… Yes, this would fully automate upgrading HA and the add-ons, as thes are also separate containers. But when there are breaking changes in HA, which sometimes happens, you can end up having a broken system one morning without prior notice. Not good. I prefer to push the button myself, after i read the release notes. Then at least i know what will break when i do the upgrade.
EDIT: furthermore, there’s also the rest of the functionality of supervisor. It’s responsible for the updates, but it also installs new add-ons in HA when you click on one. Watchtower is only capable of keeping HA and add-ons up to date, but no more than that. If i would want to install a new add-on, i can’t because of missing supervisor. I think losing supervisor would also mean losing the entire add-on repo by the way.
Agree on that one problem with HASS is always breaking changes… But then again you are running docker so the simple way is to run portainer and install the old HASS back.
yeah correct. But i just added a small bit
this part:
EDIT: furthermore, there’s also the rest of the functionality of supervisor. It’s responsible for the updates, but it also installs new add-ons in HA when you click on one. Watchtower is only capable of keeping HA and add-ons up to date, but no more than that. If i would want to install a new add-on, i can’t because of missing supervisor. A.f.a.i.k. losing supervisor would also mean losing the entire add-on repo by the way.
Sorry if this has been covered - i couldn’t find anything in the thread. For those of us running on the supervisor, is it possible to move everything over to HassOs, or do we need to reconfigure from scratch. Also, is there any kind of guide out there?
Very sad about this decision. As others have mentioned, I would be happily pay an annual subscription fee to keep the supervisor.
untill we all know what HA team will do with supervised, i suggest you to do nothing.
If they’ll decide to maintain it, there will be no need to migrate.
TLDR;
HOLD.
Yes you’re correct. As long as the hardware is NUC-like, like embedded GPU etc. For instance, as a result of the upcoming changes of HA supervised i bought a Onlogic ML350G-10 with N4200 Apollo Lake CPU. Installed NUC image on mSATA disk and HassOS booted instantly.
I really hope that’s true, because i run HA in HassOS in docker on Linux. This is also called “supervised”.
I think the advice of Malaga82 is the best: HOLD until we know more.
Yup. I installed my generic supervised instance using the script and this thread has given me a great understanding of the building blocks of HA that I never took the time to learn. Thanks for the confirmation.