After upgrade to the latest Supervisor, CPU and RAM usage is again not shown properly. It seems that only one measurement is taken upon opening of the page and then it is not refreshed accordingly. The value shown is stuck in the initial state, so it is not “live” according to the actual CPU and RAM usage.
I had already added cgroup_enable=cpuset cgroup_enable=memory cgroup_memory=1 systemd.unified_cgroup_hierarchy=false systemd.legacy_systemd_cgroup_controller=false in the cmdline.txt of my Pi4 to disable cgroup v2 and it worked ok in previous versions. I tried to remove/add some of the above attributes in the cmdline but the situation persists. cat /proc/cgroups shows both cpu and ram as enabled. Stats are shown ok and live through Portainer. This has to do with an upgrade of Supervisor (or OS-agent?).
Firstly, this guide is not for a Pi, there is separate guide for that. This one is for a generic x86/64 machine.
Secondly, Portainer will give you an “Unsupported” installation.
Third, best to log an issue on the HA Github about the CPU and RAM usage.
Ok, thanks, I’ll do that.
Hi,
thanks for the guide, worked well. I want to create a btrfs subvol for the entire HA instance and therefore I must completely stop the server from the terminal.
systemctl stop hassio-supervisor.service
leaves the server running, what is the best way to shut it down, to make sure I can move the entire directory?
TIA Micha
“sudo ha core stop” I guess, though I normally just use docker commands:
sudo docker container ls
look at container names associated with hassio plus addons
sudo docker container stop
dumb question from a moron who backed up his home assistant, but didn’t download the backup file (I figured I could snag it off the old SSD device after getting Debian installed).
So, where the HECK can I find a backup I took just a few hours ago? Which directory path, what are the file names?
(/me is st00pid tonight…)
Dumb answer for st00pid user:
/usr/share/hassio/backup/*.tar
May I ask how I would solve the fact that once I input curl -fsSL get.docker.com | sh
it give me the error: curl: (6) Could not resolve host: get.docker.com
And I can’t move forward because of that. Any suggestions?
You have a network problem.
Thank you for your reply, kanga_who!
In what way a network problem? I can access the internet via that server if this is what you mean. I just downloaded some packages.
Disable IPv6 and try again.
I found someone with a similar problem. He sent sudo -s and then the command and it worked. Unable to Install Docker - #5 by brikeyes - General Discussions - Docker Community Forums
I did the same and it worked as well. Don’t know what sudo -s does exactly 
Well, it gave me this error:
+ sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq docker-ce-rootless-extras >/dev/null
E: Failed to fetch https://download.docker.com/linux/debian/dists/buster/pool/stable/amd64/docker-ce-rootless-extras_20.10.10~3-0~debian-buster_amd64.deb Could not resolve 'download.docker.com'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
…but it seems I have docker is installed.
And now I have this
Grrr!!
wget https://github.com/home-assistant/os-agent/releases/download/1.2.2/os-agent_1.2.2_linux_x86_64.deb
--2021-11-07 17:15:56-- https://github.com/home-assistant/os-agent/releases/download/1.2.2/os-agent_1.2.2_linux_x86_64.deb
Resolving github.com (github.com)... failed: Name or service not known.
wget: unable to resolve host address ‘github.com’
I will try to disable IPv6
I reinstalled all from scratch and it is working now. thank you, guys!
LE: I backed up yesterday and it has not restarted since then. How do you check if HA is running what the problems are while on Debian? Any clues?
By installing as described it will be missing unzip and I can then not install HACS.
Assume by this description installing unzip will then give me an unsupported system?
You only get unsupported if you install extra docker containers.
Okay thanks, then possibly the opening post should have been slightly rephrased
Using Debian 11 and following a strict set of guidelines available HERE will give you a supported installation of Home Assistant Supervised. If you choose at anytime to install additional software to the Debian operating system, your installation will become officially unsupported.
Technically, installing anything else than the required dependencies for a Supervised installation does make it unsupported, so the opening comment is accurate.
and honestly who knows what bastardry is coming given the issue with ANY container made it unsupported only a couple of weeks ago after years with no issues…
I have trouble to get my bluetooth usb stick to find my BLE sensors. I use ble to get the data (this has worked before on my raspi3B+ very well.
How does HA supervisor can access the USB device? If I go to supervisor → host > hardware the stick is shown as Bluetooth_Radio. Did this also mean HA can access it?
Thanks
Hello,
A year ago, I installed ha supervised on my openmediavault 5.5 using the old script
curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | bash -s
which allowed me to choose the data folder on a disk accessible by the samba of omv.
I unfortunately broke my installation. And the old script doesn’t seem to work on omv 6 anymore.
So I would like to use the official way
dpkg -i homeassistant-supervised.deb
but I don’t see how I can declare the folder for
-d | --data-share $ PREFIX / share / hassio data folder for hass.io installation
Or is there a way to move this folder after installation?