Ok then 1. what about the host processes I described that I am also running?, and 2. Why does HA Supervisor even exist if no other software is allowed to be on the host system?
- The point of it is to allow you to get the HAOS experience on hardware that can’t run HAOS itself, since initially HAOS had very limited hardware support. Things have changed a lot since then, HAOS supports a lot more hardware, so hopefully the future of Supervised is limited.
I can’t help with (1), but hopefully somebody who runs Supervised will be able to help you.
1 Like
My last few post in that thread cover some of the cgroup and connectivity things.
1 Like
At first I was going to give you a ‘heart’ for responding to help out, but then I reread your statement “hopefully the future of Supervised is limited”… NOOOOOOOOOOOOOO!!!
I also say that because I have fans along with some wires soldered together with a resistor and a transistor and plugged into some of the IO pins and wrote an app to monitor the temperature and turn the fans on if the RPI goes above 65 degrees C and the back off again when it falls below 55 degrees C. It writes to the syslog and I have the syslog sitting in the shared directory so that HA supervised in the container can see syslog so I’ve got a bunch of command line sensors monitoring various syslog entries - before you get rid of the supervised you’d have to support any and all such hardware and configurations within HAOS (so it would have to be able to support everything)…
(I’ll give you a “like” anyway 
)
1 Like
The trouble is, setups like yours are in breach of the requirements, which can (and have) result in issues with the whole environment not working correctly.
I understand why people do this, I worked in tech support for years and know too well that people view requirements as vague suggestions, but if you’re at that point you’re better off simply switching to a Container install using Docker (or Podman).
You’ll never fix the os issue. Only supported OS for supervised is debian, no derivations of debian (e.g. what you’re running).
As for cgroup_version, there’s a fix in the documentation
This highlights how to do the change
1 Like
@petro - As noob to python and linux but with alot of patience, time and (what I think is a somewhat) good aptitude, how do I migrate RPI that has two host processes running as well as a few cron jobs, and also HAS, from “Raspbian GNU/Linux 11 (bullseye)” to “Debian 11 (Bullseye)”?
I have a suggestion but not sure how to do it. Given that within HA I have full configuration backups so I can restore all of the HA settings with no issue (and have done so in the past) using the add-on “Home Assistant Google Drive Backup” - my question ultimately comes down to:
What backup system/software (preferably with a UI) can I use that will allow me to restore specific files and configurations on the host (just two processes and some cron jobs) after I have blown one OS away and installed the second OS from scratch?
I just back up the configuration folder for HA to source control. I’m currently using GIT, but I did use mercurial for a while. Both have steep learning curves, but it’s really easy to move between versions once you learn the CLI. You can also use both of those backup systems with interfaces. For mercurial I used TortiouseHG. For Git I use GitKraken or VSCode. GitKraken doesn’t let you use private repos. Both VSCode and TortiousHG are “harder” to use than GitKraken.
Thank you but what about the last paragraph - the items on the host is my main concern - weewx is a VERY process involved with huge number of moving pieces and add-ons - (note the below link and then the images on the right side of that web page)
Sounds like a question for the Weewx support community. I googled “move weewx to another computer” and found this:
https://groups.google.com/g/weewx-user/c/LukRChVm6R4
Hope it helps.
1 Like
@petro Thank you! Seems like I have alot to learn… So haos uses containers as well and I would have this (weewx) in one of them, managed by HA? So confused lol
I seem to have been able to fix the cgroup error by adding systemd.unified_cgroup_hierarchy=false to /boot/cmdline.txt on raspbian on a RPi CM4.
1 Like
If you see aboive I tried “=0” and it caused me all manner of issues, but the core issue is the wrong OS… I am doing some research tro see if weewx can run on Debian instead of Raspbian - and if it can, then I am going to bite the bulket and reinstall everything from scratch… UGH!
Since I am doing some research tro see if weewx can run on Debian instead of Raspbian - and if it can, then I am going to bite the bulket and reinstall everything from scratch…
- Can VNC be used on Debian (for headless use)?
- Can weewx run on debian?
Installing either of those is likely to lead to you still being Unsupported.
Just thinking aloud…since HA is not a commercial product, what does ‘unsupported’ actually mean?
People with questions normally end up here at the forum, and normally get answers quick enough.
So far I have heard nobody say ‘hey, I know the answer, but your system is not supported, so i’m not going to tell’
So, what is the relevance of running an ‘unsupported’ HA??? 