I’m trying to install HA Supervised on my Raspberry Pi4 using the os-agent_1.4.1_linux_armv7.deb OS agent.
When it is time to issue the command dpkg -i homeassistant-supervised.deb I get the error:
[error] Raspbian GNU/Linux 10 (buster) is not supported!
dpkg: error processing archive homeassistant-supervised.deb (--install):
new homeassistant-supervised package pre-installation script subprocess returned error exit status 1
[info] Undo divert on abort-install
Not sure what else to do.
Raspbian is not Debian, it is a derivative of Debian. And as the requirements for supervised states:
Debian Linux Debian 11 aka Bullseye (no derivatives)
You should read this:
Or just install HAOS instead.
Or just install HAOS instead.
This 100%
I’d 100% do that if raspberry pi4s weren’t being scalped 5x the price. 
Right now, the only pi4 I have is being used for my VPN, adblocker, NAS and a few other things. I just don’t wanna reinstall/reconfigure everything again.
You’ll want to install HA Container instead then since HA Supervised is meant to be installed on a machine with nothing else installed on it other than the installation requirements.
If you can live without support for Add-ons, you can install Home Assistant Container on your RPI4.
If that’s unacceptable, then you are in an unfortunate position of having requirements that cannot be fulfilled by your RPI4’s current configuration (to create a supported system).
That is the unfortunate situation I am in. I do need to have add-ons.
If I could find where the docker-containers.yaml file is, I might be able to use the docker version by adding the add-ons manually. Unfortunately any results regarding that are pretty inconsistent.
Docker Compose makes it easy to set up multiple containers. You wouldn’t want to try to add the add-ons themselves manually though; just Google “software name docker” for anything you want to install (or just see if a package exists for whatever it is you’re looking for)
Looks like it only supports AMD or intel chipsets. Looks like it needs about 4GB of RAM minimum too supposedly. My pi is the 1gb version
I wonder if using one of my Windows servers would be a better option. I could always just load it up on a virtual machine too.
Nah, you can run Docker Engine (and then compose) on a pi with 1 GB of RAM. That being said, you should indeed consider another platform if your pi is the 1GB version.
I’ll give it a try. To be fair, only about 53% of RAM is being used with everything else running including HA. I’ll see how it goes, I got a backup plan if it can’t handle it.
If you have the server 24h. on then thats a good option. Otherwise that would be expensive because of the electricity cost.
You could start with the rpi and then decide.
YOU HAVE TO change the OS. It will run faster - much faster - and much cooler.
The below is coming from someone who had to teach himself linux and python to get all this to work, so if you are willing like I am to endlessly bang your head against a wall until you either break through the wall of die in the attempt - if I did it you can do it lol!
Hope this helps:
Make sure you have anough RAM first for the below - and for the beginning part of the directions, you need a cable to connect your monitor directly to the RPI (only needed for the first part, the proper OS install) - they are pretty inexpensive. Then after that, I run it headless (connectiing to it through my network - and it ideally should be pluged into ethernet instead of WiFi as that is more stable and faster) -
I would suggest you do a full backup of your RPI so you can just go back to the old one if anything blows up - and can mount the original storage while running on the new storage to be able to copy anything from the old to the new so you lose - NOTHING. If you are going to install using this which starts from scratch including the correct OS - and follow it EXACTLY (but read my item underneath the first link as well):
You may run into a situation that at the very last step, where you are doing this:
dpkg -i homeassistant-supervised.deb
And you are monitoring your syslog during the install, if your RPI is unable to download things so it cannot come up, it may be because you need to do this (which is what I did and that fixed it):
So where they say, this step in the above directions -
apt-get install jq wget curl udisks2 libglib2.0-bin network-manager dbus apparmor-utils systemd-journal-remote -y
Instead do this:
apt-get install jq wget curl udisks2 libglib2.0-bin network-manager dbus apparmor systemd-journal-remote -y
Basically the only difference between the two is using apparmor instead of apparmor-utils. Supposedly apparmor-utils is supposed to install apparmor but in my case that doesn’t happen for some reason.
After I got HA Supervised up and running, then I connected my old storage to the new and oinstalkled and set up the other items I also had running on the RPI in addition to HA Supervised. Those are:
Dec 30 12:48:13 kruse-pi fancontrol.py: Fan still off 40.89°<50-60 (1672422493)
Dec 30 12:53:08 kruse-pi fancontrol.py: Fan still off 42.35°<50-60 (1672422788)
Dec 30 12:58:03 kruse-pi fancontrol.py: Fan still off 42.35°<50-60 (1672423083)
Dec 30 13:02:59 kruse-pi fancontrol.py: Fan still off 41.38°<50-60 (1672423379)
Dec 30 13:07:54 kruse-pi fancontrol.py: Fan still off 41.87°<50-60 (1672423674)
Dec 30 13:12:49 kruse-pi fancontrol.py: Fan still off 41.38°<50-60 (1672423969)
Dec 30 13:17:44 kruse-pi fancontrol.py: Fan still off 40.89°<50-60 (1672424264)
Dec 30 13:22:40 kruse-pi fancontrol.py: Fan still off 42.35°<50-60 (1672424560)
Dec 30 13:27:35 kruse-pi fancontrol.py: Fan still off 40.89°<50-60 (1672424855)
Dec 30 13:25:29 kruse-pi weewx[510] INFO weewx.restx: Windy: Published record 2022-12-30 13:25:00 EST (1672424700)
Dec 30 13:25:29 kruse-pi weewx[510] INFO weewx.restx: PWSWeather: Published record 2022-12-30 13:25:00 EST (1672424700)
Dec 30 13:25:29 kruse-pi weewx[510] INFO weewx.restx: Wunderground-PWS: Published record 2022-12-30 13:25:00 EST (1672424700)
Dec 30 13:25:29 kruse-pi weewx[510] INFO weewx.restx: WindGuru: Published record 2022-12-30 13:25:00 EST (1672424700)
Dec 30 13:25:29 kruse-pi weewx[510] INFO weewx.restx: CWOP: Published record 2022-12-30 13:25:00 EST (1672424700)
Dec 30 13:25:29 kruse-pi weewx[510] INFO weewx.restx: OWM: Published record 2022-12-30 13:25:00 EST (1672424700)
Dec 30 13:25:29 kruse-pi weewx[510] INFO weewx.restx: Meteoservices: Published record 2022-12-30 13:25:00 EST (1672424700)
Dec 30 13:25:29 kruse-pi weewx[510] INFO weewx.restx: Weather365: Published record 2022-12-30 13:25:00 EST (1672424700)
Dec 30 13:25:29 kruse-pi weewx[510] INFO weewx.restx: WeatherCloud: Published record 2022-12-30 13:25:00 EST (1672424700)
Dec 30 13:25:29 kruse-pi weewx[510] INFO weewx.restx: WOW: Published record 2022-12-30 13:25:00 EST (1672424700)
Dec 30 13:25:29 kruse-pi weewx[510] INFO weewx.restx: AWEKAS: Published record 2022-12-30 13:25:00 EST (1672424700)
But to be honest with you, once I finally did a reinstall of my original buggy incorrect OS on my RPI (which was 32 bit and cause it to run alot hotter etc. - the original raspbian it came with) i’ve turned all of those cron jobs off and even when my router or other things reboot - the RPI just reconnects flawlessly 
In any event, I have an RPI 4 w/8Gig of RAM (running off an an SSD (Samcung T7 which even comes with the needed USB C to USB 3.0 cable) - you HAVE TO use an SSD, not a MicroSD Card unless you want to fall asleep whenever you need to the RPI to do anything) and this is how it is typically running:
Here are my current Home Assistant stats (Healthy and Supported).
| version | core-2022.12.8 |
|---|---|
| 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.29.0 |
| Stage | running |
| Available Repositories | 1273 |
| Downloaded Repositories | 23 |
| can_reach_server | ok |
|---|---|
| remaining_requests | 25 |
| 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.12.1 |
| agent_version | 1.4.1 |
| docker_version | 20.10.21 |
| disk_total | 915.4 GB |
| disk_used | 18.1 GB |
| healthy | true |
| supported | true |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | AdGuard Home (4.7.6), AppDaemon (0.11.0), 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 | December 1, 2022 at 5:28 AM |
|---|---|
| current_recorder_run | December 27, 2022 at 3:45 PM |
| estimated_db_size | 1986.25 MiB |
| database_engine | sqlite |
| database_version | 3.38.5 |
Lastly when I did my install that finally worked properly in addition to the apparmor instead of apparmor-utils, a coupe of things I did as well:
Lastly, backup, backup, backup! I made things blow up and had to start over several times but was abloe to restore a backup and try again which did help. Also, before I make a backup, I issue these at the command line and then rboot first, to stop HA from automatically starting when the device starts.
sudo /lib/systemd/systemd-sysv-install disable weewx (but you don’t need this)
sudo systemctl disable hassio-supervisor.service
sudo systemctl disable hassio-apparmor.service
That way, when you do a restore, you can do whatever you want to the RPI first - before slowing it down with running processes. And then once you are ready, just issue the below command line instructions and reboot:
sudo /lib/systemd/systemd-sysv-install enable weewx (but you don’t need this)
sudo systemctl enable hassio-supervisor.service
sudo systemctl enable hassio-apparmor.service
Being somewhat of a noob, I’ve learned that if I install a shell on my RPI it typically screws things up and breaks things, so I’ve given up on that and only telnet to it to get to a command line instead to do thw work needed.
I haven’t found a better way, but this works - to do a backup, I actually boot the system up on a micropsdcard running the generic raspbian, then plug in my storage - both the backup source and destination - and then from the raspbian shell menu I just use the “SD Card Copier” app.
