installation on a 3B rpi, installation from 0 with debian 12, I try to install everything that it asks to install Ha supervi, everything is fine until I install systemd-resoult which stops working any internet connection and does not let me finish installing Ha, nor neither update nor ping google
In the end I got the ping to work, but since then it has been very slow and when I finish the HA installation it gives me an error
23-09-18 17:04:46 WARNING (MainThread) [supervisor.misc.tasks] Watchdog miss API response from Home Assistant
23-09-18 17:06:46 ERROR (MainThread) [supervisor.misc.tasks] Watchdog found a problem with Home Assistant API!
23-09-18 17:06:46 ERROR (MainThread) [supervisor.misc.tasks] Home Assistant watchdog reanimation failed!
23-09-18 17:08:46 WARNING (MainThread) [supervisor.misc.tasks] Watchdog miss API response from Home Assistant
right now ,it´s working, but very,very slow HA and console debian 12 TOO
Running on a Micro SD Card or an SSD (Itâs like night and day)?
the rpi with sd card,but before install systemd-resoult the rpi went very fast,but after the install and change anything,the rpi and HA is very slowly,I change this:
nmcli con mod â501ba88f-a6be-4d68-bfd6-84696ba74aabâ ipv4.dns â8.8.8.8, 8.8.4.4â
domain localdomain
search localdomain.
nameserver 8.8.8.8
nameserver 8.8.4.4
Greetings all
I followed this guide (to the letter) for installation on an RPi 4 and also ran into the hostname resolution issue some have experienced (e.g. here ):
curl -fsSL get.docker.com | sh
curl: (6) Could not resolve host: get.docker.com
I could also not perform any other pings at this point.
Based on Allinijhofâs post which suggested that the issue might be with systemd-resolved, I proceeded to remove the package and try again.
This worked - I was once again able to ping successfully, resolve the docker and subsequent github links, and continue with the installtion.
I couldnât complete the installation without systemd-resolved, however, as it is still required for the homeassistant-supervised package. But installing it (apt install systemd-resolved) just before running dpkg -i homeassistant-supervised.deb seemed to do the trick.
Now everything seems to be working and Home Assistant Observer reports that all is well.
TLDR:
If youâre struggling with address resolution issues, try swapping the order of systemd-resolved and homeassistant-supervised installation, i.e.:
2.1
sudo -i
apt update && sudo apt upgrade -y && sudo apt autoremove -y
apt --fix-broken install
apt install apparmor jq wget curl udisks2 libglib2.0-bin network-manager dbus lsb-release systemd-journal-remote -y # (delete systemd-resolved)
curl -fsSL get.docker.com | sh
wget https://github.com/home-assistant/os-agent/releases/download/1.6.0/os-agent_1.6.0_linux_aarch64.deb
dpkg -i os-agent_1.6.0_linux_aarch64.deb
wget https://github.com/home-assistant/supervised-installer/releases/latest/download/homeassistant-supervised.deb
apt install systemd-resolved
dpkg -i homeassistant-supervised.deb
3 Likes
I tried again, and when installing systemd resolved, ping google doesnât work or install, I changed
nmcli with mod â501ba88f-a6be-4d68-
bfd6- 84696ba74aabâ ipv4.dns â8.8.8.8, 8.8.4.4â and Google is already pinging, I have installed homeassistant supervisor, but it works very very slowly and crashes
and the homeassistant not start because
[supervisor.misc.tasks] Watchdog miss API response from Home Assistant
Where did you get â501ba88f-a6be-4d68-bfd6- 84696ba74aabâ from?
Did you blindly copied/pasted some commands from this post without a clue what you are doing?
Really??? 
Do yourself (and this community) a favor and install Home Assistant OS on your Pi. There is nothing you will miss compared to the HA Supervised method which is considered advanced and should only be used if you are an expert in managing a Linux operating system, Docker and networking! Obviously you are not there yet.
1 Like
no,I put my nmcli with the mod, and not the one from crhis 1989, the problem with using the home assistant os is that I try to integrate a voltronic inverter and it doesnât work, but with the ha docker I can install serial cable packages
(post deleted by author)
Please stop tagging people who are not involved in this community guide. Thank you.
2 Likes
He is the author of the addon. He is not the author of Adguard. Adguard is a separate software package.
A simple Google search will help answer your question instead of needlessly tagging people and spamming this guide.
A simple Google search does not give answers to a complex subject covering many areas, and that is the purpose of forums like this. My enthusiasm and asking specific questions is not spam. I have deleted everything I have said as my input or questions are obviously not welcome.
IPv6 issue:
One of my routers blocks IPv6 so at the step where you
âdpkg -i homeassistant-supervised.debâ
the ping âPING checkonline.home-assistant.io(2606:4700:20::681a:4eeâŚâ fails.
After realizing it was pinging an IPv6 address I disabled it with help from this link on disabling IPv6 on debian 12 and installation proceeded normally.
1 Like
@kanga_who fyi
I posted a few months back with a query as to whether people were having an issue with cgroup reverting from version 1 to version 2, when doing host updates. It didnât get much traction so doesnât seem to be much of an issue. I personally run an rpi4 with an SSD. @Tamsy hinted the SSD may be part of the problem. I can neither confirm or deny this.
Anyway.
My system upon updating was removing the
systemd.unified_cgroup_hierarchy=0
line from the file
/boot/firmware/cmdline.txt
I was reading a bit through
/boot/firmware/config.txt
and
/etc/default/raspi-firmware
Both files mention creating an extra file to have the kernel/boot update automatically.
As such I created a new file.
sudo nano /etc/default/raspi-extra-cmdline
which contains
systemd.unified_cgroup_hierarchy=0
This so far has so far stopped the issue and I havenât needed to edit /boot/firmware/cmdline.txt or to re-run the supervisor script after updates to revert cgroup to version 1.
So
hopefully this is a solution to others and can potentially be added as an update to the tutorial.
It might also be something that can added to the supervisor script in the futureâŚ
Hello HA friends,
Iâve just installed HA on a Orange PI 3b running Debian 12 âBookwormâ and I spent a few hours making it works well because CGroup v2 was configured by default on the image provided by http://www.orangepi.org/.
No /boot/cmdline.txt file, no grub on that version, so I made some searching and finally foud the solution on a russian forum.
Here is the modifications to do :
cd /boot
sudo nano boot.cmd
Find the line :
if test "${docker_optimizations}" = "on"; then setenv bootargs "${bootargs} cgroup_enable=memory swapaccount=1"; fi
Add this line AFTER the above line :
setenv bootargs "${bootargs} systemd.unified_cgroup_hierarchy=false systemd.legacy_systemd_cgroup_controller=false cgroup_enable=memory apparmor=1 security=apparmor"
Save and quit nano (Ctrl+o, enter, Ctrl-x)
Built a new boot image :
sudo mkimage -C none -A arm -T script -d boot.cmd boot.scr
Reboot the Orange PI
sudo reboot now
After reboot, verify apparmor is correctly installed and working
systemctl status apparmor.service
Thatâs it !
No more warning message from HA about bad CGroup version.
HACS is now installing flawlessly (it was not before ⌠)
Hope that it helps !
Best regards
1 Like
@HasQT and @jca24440 How come you folks donât want to follow these steps whenever it becomes unhealthy? Then you arenât stuck with a setup that has any special on-off tweaks and is always healthy? Iâve done this maybe 5 times in the past year and it resolves all related issues with being unhealthy or unsupported every single time and only takes about 5 minutes!
Because that is a work around, not a solution.
My previous post is a fix unrelated to what you posted about previously.
This was occurring every update of the host. Even after re-running the supervisor install script.
There must be somethin different between your setup and mine, as the same steps always resolve it for me