That is indeed the correct image to use for the RPI4.:
But:
points to Debian 12 (Bookworm) which is certainly unsupported as for HA Supervised. Where did you get that from?
Checking the script at https://get.docker.com/ Debian 12 alias Bookworm is not even implemented yet:
case "$dist_version" in
11)
dist_version="bullseye"
;;
10)
dist_version="buster"
;;
9)
dist_version="stretch"
;;
8)
dist_version="jessie"
;;
Thanks Tamsy,
This is exactly what I found too, except it took me a few hours while you probably found it in minutes. After loading the bullseye image, I thought the apt update && apt upgrade -y command might have brought it up to bookworm. But I have no idea.
sudo cat /etc/issue.net
will show you the name and version of the underlying OS.
It should read:
Debian GNU/Linux 11
Also it should be emphasized to strictly follow 1.5) to create an unpriviledged user to continue the installation as followed by 1.6.) where you are continuing the installation from âremoteâ through the LAN.
I have seen all sorts of hard to track errors with users doing the whole installation as super user (root) and directly connected to the RPI.
@kanga_who and @Tamsy, you have both saved my butt when I bit the bullet and reinstalled EVERYTHING on my HA machine (FYI it is a RPI 4 (8 Gig ram) - booting off a (samsung model T7) 1TB SSD) - a few weeks back - to make my supervised version fully supported, per the above post you just made. I smiled when I ready your latest post, really lucky timing on my part! I have to say, @Tamsy was UNBELIEVEABLY helpful, supportive and very patient with me as had to redo it numerous times due to strange issues. Long story short, most of the issues revolved around DNS. I think it is due to my local network setup as it is not very common for home use (someone tried to steal my identity right before I barely rectified a cvery bad flooding situation in my home - so I because a security âfreakâ and have leak sensors etc. al over thye home. My local network is using the Omada (TP-LInk product line) paradigm with a TL-ER7206 router controled via the OC300 controller with all sorts of whacky securitiy and VPN settings.
Long story short, when utlilizing this line in your install script (and as I said before it might be because of my router/local network):
apt-get install jq wget curl udisks2 libglib2.0-bin network-manager dbus apparmor-utils systemd-journal-remote -y
vs. the ever so slighlty different step in the official Nabu Cases / HomeAssistant.io instructions for Home Assitant Supervised (from here):
apt-get install \
apparmor \
jq \
wget \
curl \
udisks2 \
libglib2.0-bin \
network-manager \
dbus \
systemd-journal-remote -y
Your script include apparmor-utils whereas the otherone uses apparmor instead. My install only works flawlessly without any issues using the second version. Is my understanding the apparmor-utils automatically cause apparmor to be insalled (any maybe it is a slighly different version?), or the apparmor-utils has or is missing something that causes the DNS issues for me - ?
My system has been running smooth as glass lately so I do not want to make any unnecessary changes, but I thought I should mention this to you.
@kanga_who (and @Tamsy feel free to please chime in as you helped me with my journey), what are your thoughts on this?
Thanks to both of you again and I am so lucky to have finished the reinstall when I did!
| version | core-2022.12.4 |
|---|---|
| installation_type | Home Assistant Supervised |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.10.7 |
| os_name | Linux |
| os_version | 5.10.0-19-arm64 |
| arch | aarch64 |
| timezone | America/New_York |
| config_dir | /config |
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 1.28.4 |
| Stage | running |
| Available Repositories | 1227 |
| Downloaded Repositories | 23 |
| can_reach_server | ok |
|---|---|
| remaining_requests | 27 |
| logged_in | false |
|---|---|
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
| host_os | Debian GNU/Linux 11 (bullseye) |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2022.11.2 |
| agent_version | 1.4.1 |
| docker_version | 20.10.21 |
| disk_total | 915.4 GB |
| disk_used | 17.5 GB |
| healthy | true |
| supported | true |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | AdGuard Home (4.7.5), AppDaemon (0.10.1), Core DNS Override (0.1.1), Duck DNS (1.15.0), File editor (5.4.2), Home Assistant Google Drive Backup (0.109.2), Log Viewer (0.14.0), Mosquitto broker (6.1.3), Samba share (10.0.0), Terminal & SSH (9.6.1) |
| dashboards | 4 |
|---|---|
| resources | 15 |
| views | 25 |
| mode | storage |
| oldest_recorder_run | November 13, 2022 at 9:55 AM |
|---|---|
| current_recorder_run | December 13, 2022 at 7:06 AM |
| estimated_db_size | 1729.08 MiB |
| database_engine | sqlite |
| database_version | 3.38.5 |
Hi all,
I do have a quite dumb question and it bothers me a lot that I cannot find myself the answer to.
What is the username/password if I want to login via SSH after flashing the SSD with balenaEtcher?
No username/password does not work.
âroot/rootâ or âroot/passwordâ or âroot/â does not work as well.
I even tried to modify the sysconfig.txt file and set my own password or simply uncommenting the standard one. I also tried copy/pasting the password.
It just does not work.
I do not have a spare monitor at the moment so ssh is all I got :-/
edit: I just noticed that editing the sysconfig.txt does not help, because it is getting overwritten.
Just pulled the ssd and plugged it into my laptop and the changes are gone.
Best regards,
Manuel
Welcome to the forum, Manuel 
You simply cant without being connected directly to your RPI with a monitor and keyboard.
The root password can only be set by directly being connected to the RPI with a new installation and there are good reasons for this restriction.
User root is not supposed to connect directly through SSH anyway for security matters. Do yourself (and the community here) a favor and create that unpriviledged user as described with 1.5).
Login through SSH as that user only and manage the system by prepending sudo to every console command.
FYI if you are not strictly sticking to the guide there is little chance that you get support in here.
So I need to connect the PI to a montior at least once, right?
Adding an unpriviledged user would have been my first step.
That is correct, monitor and keyboard 
Hi again 
Does anyone have an idea what this is about?
Canât install hoomeassistant :-/
âroot@raspi:~# dpkg -i homeassistant-supervised.deb
(Reading database ⌠29384 files and directories currently installed.)
Preparing to unpack homeassistant-supervised.deb âŚ
[warn]
[warn] If you want more control over your own system, run
[warn] Home Assistant as a VM or run Home Assistant Core
[warn] via a Docker container.
[warn]
/var/lib/dpkg/tmp.ci/preinst: line 15: lsb_release: command not found
dpkg: error processing archive homeassistant-supervised.deb (âinstall):
new homeassistant-supervised package pre-installation script subprocess returned error exit status 127
[info] Undo divert on abort-install
No diversion âdiversion of /etc/NetworkManager/NetworkManager.conf to /etc/NetworkManager/NetworkManager.conf.real by homeassistant-supervisedâ, none removed.
No diversion âdiversion of /etc/NetworkManager/system-connections/default to /etc/NetworkManager/system-connections/default.real by homeassistant-supervisedâ, none removed.
No diversion âdiversion of /etc/docker/daemon.json to /etc/docker/daemon.json.real by homeassistant-supervisedâ, none removed.
No diversion âdiversion of /etc/network/interfaces to /etc/network/interfaces.real by homeassistant-supervisedâ, none removed.
[info] Resetting debconf selections
[info] Removal complete, due to the complexity of this installation method,
[info] you will need to manually remove the containers created by the supervisor
Errors were encountered while processing:
homeassistant-supervised.debâ
It is about the result of not paying attention to the very second paragraph of this guide which reads:
A closer reading of the above might bring you the enlightement that Raspberry Pi OS is not Debian 11.
Furthermore you are not following the advice:
And you think this helps?
For two times I had an supported OS - Version where my Supervised Hassio was running on - until I do: guess what:
I was executing following commands:
sudo apt update
sudo apt upgrade
After rebooting the OS, it was marked as unsupported in HA.
In both cases a new debian kernel version was part of the upgrade and the /boot/firmware/cmdline.txt was modified during the apt upgrade process.
You need install lsb_release with following command
apt-get install -y lsb-release
Works for me
@kanga_who
I did exactly as instructed and this is the error I got
[info] Undo divert on abort-install
No diversion 'diversion of /etc/NetworkManager/NetworkManager.conf to /etc/Netwo rkManager/NetworkManager.conf.real by homeassistant-supervised', none removed.
No diversion 'diversion of /etc/NetworkManager/system-connections/default to /et c/NetworkManager/system-connections/default.real by homeassistant-supervised', n one removed.
No diversion 'diversion of /etc/docker/daemon.json to /etc/docker/daemon.json.re al by homeassistant-supervised', none removed.
No diversion 'diversion of /etc/network/interfaces to /etc/network/interfaces.re al by homeassistant-supervised', none removed.
[info] Resetting debconf selections
[info] Removal complete, due to the complexity of this installation method,
[info] you will need to manually remove the containers created by the supervisor
Errors were encountered while processing:
homeassistant-supervised.deb
What OS are you using?
debian 11 (Bullseye)
Are you by any chance using Raspberry Pi OS (debian based) or Proxmox and a Debian VM?
Hi,
I get the same error with a non-privileged user following the installation guide step-by-step.
If I installed lsb-release package the supervised-installer finished without error, but after a sucessful login to HA instance I get Unsupported System because of invalid cgroup version.
What can I do to resolve this issue?
Sorry: after a reboot it resolved.
THX!
And what else have you installed or tried to install on the system, other than Home Assistant Supervised?