This guide is for generic x86-64 installs, not Pi’s, so the provided OS Agent info is for that install type.
There is a seperate guide for Supervised + Pi.
Thanks for the guide. Followed it to install HASS on a BMAX B2 mini-pc. Just getting started but it’s been solid so far. Great community. Someday maybe I’ll be able to help someone else.
Keep at it! There is definitely a learning curve, and I felt the same when I first started. But you’ll eventually get to the point of comfort where you’ll be able to help others! 
Thank you for the guide. I had to do another install today, and the guide is definitely helpful.
FYI, the links to debian distros have changed since 11.2 is out now. As such the link to the full Debian image with all drivers is now:
I.e. In section 1.1 of the article, replace the full Debian image link’s “11.0.0” with “11.2.0” for the new image.
I just saw the following after I did the latest HA update
When I clicked on the link to learn more it said I need to run systemd-resolved service or reinstall Debian. I have just finished following this tutorial on a Lenovo M93P Tiny that I now plan to replace my older machine with and I am getting the exact same warning.
Is there something that has changed with the latest update? I would appreciate any pointers as I would like to resolve this before I switch machines
Thanks
Richard
I’ve made new installation of debian and HA two days ago. I still have this message obout unsupprted installation.
log:
[22:01:08] INFO: Using udev information from host
[cont-init.d] udev.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[22:01:08] INFO: Starting local supervisor watchdog...
22-03-10 22:01:11 INFO (MainThread) [__main__] Initializing Supervisor setup
22-03-10 22:01:11 INFO (MainThread) [supervisor.bootstrap] Initializing Supervisor Sentry
22-03-10 23:01:11 INFO (MainThread) [supervisor.bootstrap] Seting up coresys for machine: qemux86-64
22-03-10 23:01:11 INFO (SyncWorker_0) [supervisor.docker.supervisor] Attaching to Supervisor ghcr.io/home-assistant/amd64-hassio-supervisor with version 2022.03.3
22-03-10 23:01:11 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.INITIALIZE
22-03-10 23:01:11 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-03-10 23:01:11 INFO (MainThread) [__main__] Setting up Supervisor
22-03-10 23:01:11 INFO (MainThread) [supervisor.api] Starting API on 172.30.32.2
22-03-10 23:01:11 INFO (MainThread) [supervisor.hardware.monitor] Started Supervisor hardware monitor
22-03-10 23:01:11 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface io.hass.os
22-03-10 23:01:11 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.systemd1
22-03-10 23:01:11 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.login1
22-03-10 23:01:11 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.hostname1
22-03-10 23:01:11 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.timedate1
22-03-10 23:01:11 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.NetworkManager
22-03-10 23:01:11 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface de.pengutronix.rauc
22-03-10 23:01:11 WARNING (MainThread) [supervisor.dbus.manager] Can't load dbus interface de.pengutronix.rauc: The name de.pengutronix.rauc was not provided by any .service files
22-03-10 23:01:11 INFO (MainThread) [supervisor.dbus.manager] Load dbus interface org.freedesktop.resolve1
22-03-10 23:01:11 INFO (MainThread) [supervisor.host.info] Updating local host information
22-03-10 23:01:12 INFO (MainThread) [supervisor.host.services] Updating service information
22-03-10 23:01:12 INFO (MainThread) [supervisor.host.network] Updating local network information
22-03-10 23:01:12 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
22-03-10 23:01:12 INFO (MainThread) [supervisor.host.manager] Host information reload completed
22-03-10 23:01:12 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}
22-03-10 23:01:12 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-cli with version 2021.12.0
22-03-10 23:01:12 INFO (MainThread) [supervisor.plugins.cli] Starting CLI plugin
22-03-10 23:01:13 INFO (SyncWorker_1) [supervisor.docker.cli] Starting CLI ghcr.io/home-assistant/amd64-hassio-cli with version 2021.12.0 - 172.30.32.5
22-03-10 23:01:13 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-dns with version 2021.06.0
22-03-10 23:01:13 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
22-03-10 23:01:13 INFO (SyncWorker_0) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2021.06.0 - 172.30.32.3
22-03-10 23:01:13 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
22-03-10 23:01:13 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-audio with version 2021.07.0
22-03-10 23:01:13 INFO (MainThread) [supervisor.plugins.audio] Starting Audio plugin
22-03-10 23:01:14 INFO (SyncWorker_1) [supervisor.docker.audio] Starting Audio ghcr.io/home-assistant/amd64-hassio-audio with version 2021.07.0 - 172.30.32.4
22-03-10 23:01:14 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-observer with version 2021.10.0
22-03-10 23:01:14 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-multicast with version 2022.02.0
22-03-10 23:01:14 INFO (MainThread) [supervisor.plugins.multicast] Starting Multicast plugin
22-03-10 23:01:14 INFO (SyncWorker_0) [supervisor.docker.multicast] Starting Multicast ghcr.io/home-assistant/amd64-hassio-multicast with version 2022.02.0 - Host
22-03-10 23:01:14 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
22-03-10 23:01:14 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 1 Home Assistant secrets
22-03-10 23:01:14 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/qemux86-64-homeassistant with version 2022.3.3
22-03-10 23:01:14 INFO (MainThread) [supervisor.os.manager] No Home Assistant Operating System found
22-03-10 23:01:15 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/core repository
22-03-10 23:01:15 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/45df7312 repository
22-03-10 23:01:15 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/a0d7b954 repository
22-03-10 23:01:15 INFO (MainThread) [supervisor.store] Loading add-ons from store: 64 all - 64 new - 0 remove
22-03-10 23:01:15 INFO (MainThread) [supervisor.addons] Found 1 installed add-ons
22-03-10 23:01:15 INFO (SyncWorker_2) [supervisor.docker.interface] Attaching to homeassistant/amd64-addon-mosquitto with version 6.0.1
22-03-10 23:01:16 INFO (MainThread) [supervisor.backups.manager] Found 0 backup files
22-03-10 23:01:16 INFO (MainThread) [supervisor.discovery] Loaded 1 messages
22-03-10 23:01:16 INFO (MainThread) [supervisor.ingress] Loaded 0 ingress sessions
22-03-10 23:01:16 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.SETUP
22-03-10 23:01:16 INFO (MainThread) [supervisor.resolution.check] System checks complete
22-03-10 23:01:16 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
22-03-10 23:01:16 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-03-10 23:01:16 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not running - CoreState.SETUP
22-03-10 23:01:16 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
22-03-10 23:01:16 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-03-10 23:01:16 INFO (MainThread) [__main__] Running Supervisor
22-03-10 23:01:16 INFO (MainThread) [supervisor.jobs] 'OSManager.mark_healthy' blocked from execution, no Home Assistant OS available
22-03-10 23:01:16 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons
22-03-10 23:01:16 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' starting 1 add-ons
22-03-10 23:01:16 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-mosquitto with version 6.0.1
22-03-10 23:01:19 INFO (MainThread) [supervisor.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
22-03-10 23:01:21 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SERVICES' starting 0 add-ons
22-03-10 23:01:21 INFO (MainThread) [supervisor.core] Start Home Assistant Core
22-03-10 23:01:22 INFO (SyncWorker_0) [supervisor.docker.interface] Starting homeassistant
22-03-10 23:01:22 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
22-03-10 23:01:28 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.STARTUP
22-03-10 23:01:28 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-03-10 23:01:32 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
22-03-10 23:01:39 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
22-03-10 23:01:39 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.APPLICATION' starting 0 add-ons
22-03-10 23:01:39 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
22-03-10 23:01:39 INFO (MainThread) [supervisor.core] Supervisor is up and running
22-03-10 23:01:39 INFO (MainThread) [supervisor.host.info] Updating local host information
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.module] Create new suggestion SuggestionType.CREATE_FULL_BACKUP - ContextType.SYSTEM / None
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.CORE
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.PLUGIN
22-03-10 23:01:39 INFO (MainThread) [supervisor.host.services] Updating service information
22-03-10 23:01:39 INFO (MainThread) [supervisor.host.network] Updating local network information
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.check] System checks complete
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
22-03-10 23:01:39 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
22-03-10 23:01:39 INFO (MainThread) [supervisor.host.manager] Host information reload completed
22-03-10 23:01:39 WARNING (MainThread) [supervisor.resolution.evaluations.base] Found unsupported images: {'portainer/portainer-ce'} (more-info: https://www.home-assistant.io/more-info/unsupported/software)
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
22-03-10 23:01:39 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
I had the same issue… It seems like Home Assistant does not like Portainer (see the log error regarding unsupported image). Once I removed portioner the issue went away.
It doesn’t like ANY container not installed by itself hence unhealthy/unsupported. There is no way around this. Just run unsupported and be happy
There is a known issue with the Supervisor currently. The code notary server is down, so it’s a case of waiting until it is back online.
1 Like
Anyone with any ideas here?
Forgot myself and rebooted from terminal (“outside” hass) and once again z-wave is misbehaving and haven’t yet managed to get it back to as it should…
Can’t see why it should behave like this, why rebooting from “inside” hass gives no problems, but from “outside” does.
You’re posting in the wrong thread mate, this is an install guide, not for Z Wave troubleshooting.
I’d suggest searching the forums for a similar issue or starting a new topic.
1 Like
Posted here since it feels like more of a problem based in the installation rather than the z-wave.
I base that on the different behaviour depending on how I shut down/restart my computer, from “Outside”, terminal in debian, it messes with the z-wave, but not when I do it from “inside” hass (reboot host, system) So feels like there is a difference in how HASS is shutdown.
So maybe not exactley installation-related, but maybe more on how some part inside the installation is done, if you get what I mean.
But will try and find a better place for my question
OK Thank you,
I saw in another thread that running the following could be a fix:
sudo systemctl enable systemd-resolved.service
I am just a little nervous about running commands I know nothing about, Linux is not my area of expertise lol
FYI, this will cause issues if anyone is running pihole on the same raspberry pi, since that uses port 53. One option to get around that would be to run pihole in docker and/or exposure it to a different port.
Anyone here have a ever-increasing var/log/journal? I noticed my drive was steadily climbing about a GB per day, turns out it’s journal files. Anyways, I’m viewing them and it’s nothing bad. Basically information about every little thing possible that occurred, no errors. So before I limit the size, is this happening to anyone else? It was not happening on buster. I updated about 5 days ago.
I wanted to say – AWESOME JOB. I only ran into a few “glitches” and doing a google search was able to resolve them and get this process completed.
(1) I had the modem manager issue - and the systemctl disable ModemManager fixed that.
(2) I was then getting error:
Error response from daemon: Get “https://registry-1.docker.io/v2/”: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:60704->[::1]:53: read: connection refused
dpkg: error processing package homeassistant-supervised (–install):
installed homeassistant-supervised package post-installation script subprocess returned error exit status 1
I have IPv6 enabled in my home with a pfSense Router/Firewall. I followed these instructions to disable it on Debian 11 - and the installation completed:
a) Edit the /etc/sysctl.conf file. – sudo nano /etc/sysctl.conf
b) Place the following entry to disable IPv6 for all adapters.
net.ipv6.conf.all.disable_ipv6 = 1
(For a particular adapter (If the network card name is enp0s3))
net.ipv6.conf.enp0s3.disable_ipv6 = 1
c) To reflect the changes execute the following command.
sudo sysctl -p
d) ip addr
– Verify there are no IPv6 addresses shown.
I simply re-ran this line: ** dpkg -i homeassistant-supervised.deb**
3 Likes
Proxmox 7.1-10 - Debian 11 bullseye w kernel Linux 5.12.19-6-pve
root@debian:~# sudo sysctl -p
net.ipv6.conf.all.disable_ipv6 = 1
root@debian:~# dpkg -i homeassistant-supervised.deb
(Reading database ... 44475 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]
[info] Fix kernel dmesg restriction
/var/lib/dpkg/tmp.ci/preinst: line 21: /proc/sys/kernel/dmesg_restrict: Read-only file system
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
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
This is totally driving me nuts. Help please?
I mean how to fix this pretty please:
[info] Fix kernel dmesg restriction
/var/lib/dpkg/tmp.ci/preinst: line 21: /proc/sys/kernel/dmesg_restrict: Read-only file system
dpkg: error processing archive homeassistant-supervised.deb (--install):
new homeassistant-supervised package pre-installation script subprocess returned error exit status 1