francisp
(Francis)
June 12, 2025, 7:50am
269
Yes it works with HA OS. Just need to enable
dtparam=i2c_vc=on
dtparam=i2c_arm=on
dtoverlay=i2c-rtc,ds3231
to boot/config.txt ,which you CAN do on HA OS
2 Likes
Tamsy
(Tamsy)
June 12, 2025, 7:54am
270
Such a basic function should work out of the box and without one has to tamper with any files within HA OS. It’s enough to make you weep…
Just bought a GSM modem to enable my system sending SMS in case of a really important event
habb0
June 12, 2025, 8:06am
272
Is this joke?
Why the earth they dropped supervised, That and HAOS is only wich support all things.
Now support container, and they own picture said add-ons not supported. April fools are too late
3 Likes
M0ebiu5
(M0ebiu5)
June 12, 2025, 8:18am
273
What about support for nvidia cards in HAOS?
joostlek
(Joost Lekkerkerker)
June 12, 2025, 8:39am
274
What deprecation message do you see? Can you provide system health info?
Synochy
(Martin)
June 12, 2025, 8:53am
275
I am using Supervised version of HA (with add-on) on an orange pi 5B.
How can I migrate to HAOS ?
If I understand well orange pi are not supported by HAOS.
HA runs on my current Debian server (Bookworm) together with other server services. Yes, exactly. For me, HA is a server service and nothing else, even if the software is treated differently.
Why?
I was dissatisfied with the HA OS.
I want full control over the operating system.
The CLI interface is for people who have no idea about operating systems. For me, it only offers disadvantages. I cannot install any additional tools and the Linux distribution used is not what I want to use.
Furthermore, I do not want to run HA in a virtual machine. HA should have access to all the hardware that the server offers (RAM, HD, etc.).
The container variant is also very limited.
Neither variant is relevant for me.
What are the consequences if I keep my supervised version?
Will I no longer receive updates?
That would be a reason for me to look for another smart home system that offers more freedom in terms of operating system and installation mode. Even if it means starting from scratch again after several years.
8 Likes
gonzotek
(Gonzotek)
June 12, 2025, 11:12am
278
There was a discussion within the integration deprecation PR where someone is potentially going to release an add-on to replace the core integration. So you may have a path forward.
dev
← edenhaus-deprecate-sms
opened 08:53AM - 29 May 25 UTC
## Breaking change
Deprecate integration as additional system packages need t… o be installed, which are currently not installed in our docker container, which is used by all supported installation methods.
## Proposed change
Deprecate the SMS notifications via GSM-modem integration as additional system packages need to be installed, which are currently not installed in our docker container, which is used by all supported installation methods.
Adding integration-specific system packages requires prior approval in an architecture discussion, and will only be considered if the use case is or is anticipated to be highly popular.
## Type of change
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [x] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/39312
- Link to developer documentation pull request:
- Link to frontend pull request:
## Checklist
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] I have followed the [perfect PR recommendations][perfect-pr]
- [ ] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
1 Like
Gabriel76
(Gabriel Moscalu)
June 12, 2025, 11:33am
279
Hi all, just adding myself to Supervised users list.
Tried to read the docs, i cannot easily see how i would do the migration:
Running HASS on a Debian VM, in my Synology NAS
using a couple of addons
in that VM, i deployed a MariaDB that stores all data for HASS
Migration means as i see it so far (as the 6 months will pass quite fast):
loosing years of history?
running a VM inside a VM?
Please reconsider this decision for Supervised, i do not wish to purchase new HW or replace everything, including the wonderful HomeAssistant just after the 6 months end and i face the least problem with it !
1 Like
francisp
(Francis)
June 12, 2025, 11:40am
280
if you can run a Debian VM on your Synology, you can run a HA OS VM. All your add-ons can move over using a backup and restore. For your MariaDB, you will have to use the MariaDB add-on and move your database over.
2 Likes
petro
(Petro)
June 12, 2025, 11:41am
281
Backup your supervised installation and restore. For the db, you can use phpmyadmin addon with mariadb addon to load your old database into your new one.
You can also just continue to use supervised in a deprecated state. I have no plans to move off supervised until it stops working.
3 Likes
I run orange pi. Your only option is to keep running supervised even past the support period.
I am currently running HA on orange pi zero 2w and migrating to an orange pi 5 plus 32gb model.
Ismoo
June 12, 2025, 12:43pm
283
Not found simple explanation on impacts, so stupid question: I’ve used HA supervised in RPI4, because when I set it up few years back I understood it was only option to enable use other apps running over Linux (now Bookworm) like python codes, Grafana, Node-Red etc. Is my option only to install with HA OS, or can I still run it via e.g. Docker, is there already dummy-guide how to move on to trial?
Synochy
(Martin)
June 12, 2025, 12:49pm
284
I think I’ll try to create a VM with KVM and run HAOS inside it. But I find it very heavy for simple task, but I don’t want to buy new HW because they don’t want to support it anymore.
Frog
June 12, 2025, 12:50pm
285
I think it’s a regrettable mistake to abandon HA Supervised. I used to run HA OS in a VirtualBox VM. Everything worked as expected until an upgrade made the VM consume an unacceptable amount of CPU.
See the thread:
opened 04:38PM - 18 Apr 23 UTC
closed 01:59PM - 05 Oct 23 UTC
bug
board/ova
hypervisor/proxmox
### Describe the issue you are experiencing
I have juste upgraded my proxmox … HAOS VM to OS 10
I immediately noticed CPU usage raising from around 2% to 10% after upgrade.
"docker stats" shows a normal container usage / nearly no load.
```
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
4448c00d8d7e addon_core_configurator 0.03% 30.43MiB / 1.925GiB 1.54% 892kB / 843B 23.9MB / 307kB 8
01cb0b8343ce addon_core_ssh 0.00% 27.51MiB / 1.925GiB 1.40% 943kB / 31.7kB 25.4MB / 393kB 12
7920e2a0c17a hassio_multicast 0.20% 848KiB / 1.925GiB 0.04% 0B / 0B 61.4kB / 102kB 4
f7aefac69874 hassio_audio 0.00% 23.89MiB / 1.925GiB 1.21% 911kB / 0B 21.3MB / 315kB 13
1d6b8aefd115 hassio_dns 0.00% 29.41MiB / 1.925GiB 1.49% 935kB / 26.7kB 24.8MB / 106kB 11
a4872c2f1be6 hassio_cli 0.00% 13.92MiB / 1.925GiB 0.71% 917kB / 4.07kB 13.2MB / 283kB 9
04f375c2f3cd hassio_supervisor 0.00% 106.5MiB / 1.925GiB 5.40% 1.31MB / 1.07MB 61.5MB / 958kB 24
13b89612a676 homeassistant 0.80% 354.9MiB / 1.925GiB 18.00% 0B / 0B 203MB / 116MB 33
47dda87b99d2 hassio_observer 0.00% 13.68MiB / 1.925GiB 0.69% 927kB / 9.84kB 12MB / 106kB 8
```
"top" shows containerd is using a consistent 6-8% CPU (this is the only process using significant CPU load)
```
349 root 20 0 1394.2m 43.1m 7.2 2.2 5:04.68 S `- /usr/bin/containerd
```
I rebooted the VM, but CPU load stays the same:

### What operating system image do you use?
ova (for Virtual Machines)
### What version of Home Assistant Operating System is installed?
10
### Did you upgrade the Operating System.
Yes
### Steps to reproduce the issue
1.Install 9.5 ova image in proxmox
2.Upgrade to Operating System 10
3.
...
### Anything in the Supervisor logs that might be useful for us?
```txt
23-04-18 18:22:24 INFO (MainThread) [supervisor.dbus.hostname] Load dbus interface org.freedesktop.hostname1
23-04-18 18:22:24 INFO (MainThread) [supervisor.dbus.logind] Load dbus interface org.freedesktop.login1
23-04-18 18:22:24 INFO (MainThread) [supervisor.dbus.network] Load dbus interface org.freedesktop.NetworkManager
23-04-18 18:22:24 INFO (MainThread) [supervisor.dbus.rauc] Load dbus interface de.pengutronix.rauc
23-04-18 18:22:24 INFO (MainThread) [supervisor.dbus.resolved] Load dbus interface org.freedesktop.resolve1
23-04-18 18:22:24 INFO (MainThread) [supervisor.dbus.systemd] Load dbus interface org.freedesktop.systemd1
23-04-18 18:22:24 INFO (MainThread) [supervisor.dbus.timedate] Load dbus interface org.freedesktop.timedate1
23-04-18 18:22:24 INFO (MainThread) [supervisor.host.services] Updating service information
23-04-18 18:22:24 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
23-04-18 18:22:24 INFO (MainThread) [supervisor.host.network] Updating local network information
23-04-18 18:22:24 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}
23-04-18 18:22:24 INFO (MainThread) [supervisor.docker.monitor] Started docker events monitor
23-04-18 18:22:24 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-cli with version 2022.11.0
23-04-18 18:22:24 INFO (MainThread) [supervisor.plugins.cli] Starting CLI plugin
23-04-18 18:22:24 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning hassio_cli application
23-04-18 18:22:25 INFO (SyncWorker_1) [supervisor.docker.cli] Starting CLI ghcr.io/home-assistant/amd64-hassio-cli with version 2022.11.0 - 172.30.32.5
23-04-18 18:22:25 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-dns with version 2022.04.1
23-04-18 18:22:25 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
23-04-18 18:22:25 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning hassio_dns application
23-04-18 18:22:25 INFO (SyncWorker_0) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/amd64-hassio-dns with version 2022.04.1 - 172.30.32.3
23-04-18 18:22:25 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
23-04-18 18:22:25 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-audio with version 2022.07.0
23-04-18 18:22:25 INFO (MainThread) [supervisor.plugins.audio] Starting Audio plugin
23-04-18 18:22:25 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning hassio_audio application
23-04-18 18:22:26 INFO (SyncWorker_1) [supervisor.docker.audio] Starting Audio ghcr.io/home-assistant/amd64-hassio-audio with version 2022.07.0 - 172.30.32.4
23-04-18 18:22:26 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-observer with version 2021.10.0
23-04-18 18:22:26 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/amd64-hassio-multicast with version 2022.02.0
23-04-18 18:22:26 INFO (MainThread) [supervisor.plugins.multicast] Starting Multicast plugin
23-04-18 18:22:26 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning hassio_multicast application
23-04-18 18:22:26 INFO (SyncWorker_1) [supervisor.docker.multicast] Starting Multicast ghcr.io/home-assistant/amd64-hassio-multicast with version 2022.02.0 - Host
23-04-18 18:22:26 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
23-04-18 18:22:26 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 1 Home Assistant secrets
23-04-18 18:22:26 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/qemux86-64-homeassistant with version 2023.4.5
23-04-18 18:22:26 INFO (MainThread) [supervisor.os.manager] Detect Home Assistant Operating System 10.0 / BootSlot B
23-04-18 18:22:27 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/5c53de3b repository
23-04-18 18:22:27 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/core repository
23-04-18 18:22:27 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/a0d7b954 repository
23-04-18 18:22:27 INFO (MainThread) [supervisor.store] Loading add-ons from store: 69 all - 69 new - 0 remove
23-04-18 18:22:27 INFO (MainThread) [supervisor.addons] Found 2 installed add-ons
23-04-18 18:22:27 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/amd64-addon-ssh with version 9.6.1
23-04-18 18:22:27 INFO (SyncWorker_2) [supervisor.docker.interface] Attaching to homeassistant/amd64-addon-configurator with version 5.5.0
23-04-18 18:22:27 INFO (MainThread) [supervisor.backups.manager] Found 5 backup files
23-04-18 18:22:27 INFO (MainThread) [supervisor.discovery] Loaded 0 messages
23-04-18 18:22:27 INFO (MainThread) [supervisor.ingress] Loaded 0 ingress sessions
23-04-18 18:22:27 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.SETUP
23-04-18 18:22:27 INFO (MainThread) [supervisor.resolution.check] System checks complete
23-04-18 18:22:27 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
23-04-18 18:22:27 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-04-18 18:22:27 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not running - CoreState.SETUP
23-04-18 18:22:27 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
23-04-18 18:22:27 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-04-18 18:22:27 INFO (MainThread) [__main__] Running Supervisor
23-04-18 18:22:27 INFO (MainThread) [supervisor.os.manager] Rauc: B - marked slot kernel.1 as good
23-04-18 18:22:27 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons
23-04-18 18:22:27 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' starting 0 add-ons
23-04-18 18:22:27 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SERVICES' starting 1 add-ons
23-04-18 18:22:27 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_core_ssh application
23-04-18 18:22:28 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-ssh with version 9.6.1
23-04-18 18:22:33 INFO (MainThread) [supervisor.core] Start Home Assistant Core
23-04-18 18:22:33 INFO (SyncWorker_3) [supervisor.docker.interface] Starting homeassistant
23-04-18 18:22:33 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
23-04-18 18:22:36 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.STARTUP
23-04-18 18:22:36 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-04-18 18:22:37 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
23-04-18 18:22:37 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
23-04-18 18:22:37 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
23-04-18 18:22:38 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
23-04-18 18:22:38 INFO (MainThread) [supervisor.store] Loading add-ons from store: 69 all - 0 new - 0 remove
23-04-18 18:22:38 INFO (MainThread) [supervisor.store] Loading add-ons from store: 69 all - 0 new - 0 remove
23-04-18 18:23:09 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
23-04-18 18:23:09 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.APPLICATION' starting 1 add-ons
23-04-18 18:23:09 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_core_configurator application
23-04-18 18:23:09 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on homeassistant/amd64-addon-configurator with version 5.5.0
23-04-18 18:23:14 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
23-04-18 18:23:14 INFO (MainThread) [supervisor.core] Supervisor is up and running
23-04-18 18:23:14 INFO (MainThread) [supervisor.host.info] Updating local host information
23-04-18 18:23:14 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_IPV6_ERROR/ContextType.DNS_SERVER
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_FAILED/ContextType.DNS_SERVER
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.MULTIPLE_DATA_DISKS/ContextType.SYSTEM
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.NO_CURRENT_BACKUP/ContextType.SYSTEM
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.module] Create new suggestion SuggestionType.CREATE_FULL_BACKUP - ContextType.SYSTEM / None
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.module] Create new issue IssueType.NO_CURRENT_BACKUP - ContextType.SYSTEM / None
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.IPV4_CONNECTION_PROBLEM/ContextType.SYSTEM
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.check] System checks complete
23-04-18 18:23:14 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
23-04-18 18:23:15 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
23-04-18 18:23:15 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
23-04-18 18:23:15 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
23-04-18 18:23:15 INFO (MainThread) [supervisor.host.services] Updating service information
23-04-18 18:23:15 INFO (MainThread) [supervisor.host.network] Updating local network information
23-04-18 18:23:15 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
23-04-18 18:23:15 INFO (MainThread) [supervisor.host.manager] Host information reload completed
```
### Anything in the Host logs that might be useful for us?
```txt
Apr 18 16:22:27 homeassistant bluetoothd[2232]: Bluetooth daemon 5.66
Apr 18 16:22:27 homeassistant systemd[1]: Started Bluetooth service.
Apr 18 16:22:27 homeassistant bluetoothd[2232]: Starting SDP server
Apr 18 16:22:27 homeassistant kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Apr 18 16:22:27 homeassistant kernel: Bluetooth: BNEP filters: protocol multicast
Apr 18 16:22:27 homeassistant kernel: Bluetooth: BNEP socket layer initialized
Apr 18 16:22:27 homeassistant bluetoothd[2232]: Bluetooth management interface 1.22 initialized
Apr 18 16:22:27 homeassistant os-agent[104]: INFO: 2023/04/18 16:22:27 main.go:94: Diagnostics is now true
Apr 18 16:22:27 homeassistant systemd[1]: var-lib-docker-overlay2-2eaf0ad15fa660ee1b2604082b0b49856c12481a72f486c60fa2a9d809f4a7ed\x2dinit-merged.mount: Deactivated successfully.
Apr 18 16:22:27 homeassistant systemd[1]: mnt-data-docker-overlay2-2eaf0ad15fa660ee1b2604082b0b49856c12481a72f486c60fa2a9d809f4a7ed\x2dinit-merged.mount: Deactivated successfully.
Apr 18 16:22:27 homeassistant systemd[1]: var-lib-docker-overlay2-2eaf0ad15fa660ee1b2604082b0b49856c12481a72f486c60fa2a9d809f4a7ed-merged.mount: Deactivated successfully.
Apr 18 16:22:27 homeassistant systemd[1]: mnt-data-docker-overlay2-2eaf0ad15fa660ee1b2604082b0b49856c12481a72f486c60fa2a9d809f4a7ed-merged.mount: Deactivated successfully.
Apr 18 16:22:27 homeassistant kernel: hassio: port 6(vethf8c4077) entered blocking state
Apr 18 16:22:27 homeassistant kernel: hassio: port 6(vethf8c4077) entered disabled state
Apr 18 16:22:27 homeassistant kernel: device vethf8c4077 entered promiscuous mode
Apr 18 16:22:27 homeassistant NetworkManager[319]: <info> [1681834947.8072] manager: (vethba72fe7): new Veth device (/org/freedesktop/NetworkManager/Devices/17)
Apr 18 16:22:27 homeassistant NetworkManager[319]: <info> [1681834947.8085] manager: (vethf8c4077): new Veth device (/org/freedesktop/NetworkManager/Devices/18)
Apr 18 16:22:27 homeassistant systemd[1]: Started libcontainer container 585c29bcc7be293d23741540dbb4cc2af1bd3a22b3685bc4f02f04248e9b9f09.
Apr 18 16:22:28 homeassistant kernel: eth0: renamed from vethba72fe7
Apr 18 16:22:28 homeassistant kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf8c4077: link becomes ready
Apr 18 16:22:28 homeassistant kernel: hassio: port 6(vethf8c4077) entered blocking state
Apr 18 16:22:28 homeassistant kernel: hassio: port 6(vethf8c4077) entered forwarding state
Apr 18 16:22:28 homeassistant NetworkManager[319]: <info> [1681834948.0849] device (vethf8c4077): carrier: link connected
Apr 18 16:22:33 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-13b89612a676908649a9c53efe151781e6267309bfde99934415abd8ec969c83-runc.mHMj5m.mount: Deactivated successfully.
Apr 18 16:22:33 homeassistant systemd[1]: Started libcontainer container 13b89612a676908649a9c53efe151781e6267309bfde99934415abd8ec969c83.
Apr 18 16:22:33 homeassistant kernel: kauditd_printk_skb: 128 callbacks suppressed
Apr 18 16:22:33 homeassistant kernel: audit: type=1334 audit(1681834953.354:193): prog-id=49 op=LOAD
Apr 18 16:22:33 homeassistant kernel: audit: type=1300 audit(1681834953.354:193): arch=c000003e syscall=321 success=yes exit=15 a0=5 a1=c00018d7f8 a2=78 a3=0 items=0 ppid=2520 pid=2531 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
Apr 18 16:22:33 homeassistant kernel: audit: type=1327 audit(1681834953.354:193): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F31336238393631326136373639303836343961396335336566
Apr 18 16:22:33 homeassistant kernel: audit: type=1334 audit(1681834953.355:194): prog-id=50 op=LOAD
Apr 18 16:22:33 homeassistant kernel: audit: type=1300 audit(1681834953.355:194): arch=c000003e syscall=321 success=yes exit=17 a0=5 a1=c00018d590 a2=78 a3=0 items=0 ppid=2520 pid=2531 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
Apr 18 16:22:33 homeassistant kernel: audit: type=1327 audit(1681834953.355:194): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F31336238393631326136373639303836343961396335336566
Apr 18 16:22:33 homeassistant kernel: audit: type=1334 audit(1681834953.355:195): prog-id=50 op=UNLOAD
Apr 18 16:22:33 homeassistant kernel: audit: type=1334 audit(1681834953.356:196): prog-id=49 op=UNLOAD
Apr 18 16:22:33 homeassistant kernel: audit: type=1334 audit(1681834953.356:197): prog-id=51 op=LOAD
Apr 18 16:22:33 homeassistant kernel: audit: type=1300 audit(1681834953.356:197): arch=c000003e syscall=321 success=yes exit=15 a0=5 a1=c00018da50 a2=78 a3=0 items=0 ppid=2520 pid=2531 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
Apr 18 16:22:37 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Apr 18 16:22:54 homeassistant systemd[1]: systemd-timedated.service: Deactivated successfully.
Apr 18 16:22:54 homeassistant kernel: kauditd_printk_skb: 1 callbacks suppressed
Apr 18 16:22:54 homeassistant kernel: audit: type=1334 audit(1681834974.177:198): prog-id=26 op=UNLOAD
Apr 18 16:22:54 homeassistant kernel: audit: type=1334 audit(1681834974.177:199): prog-id=25 op=UNLOAD
Apr 18 16:22:54 homeassistant kernel: audit: type=1334 audit(1681834974.177:200): prog-id=24 op=UNLOAD
Apr 18 16:22:57 homeassistant systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Apr 18 16:22:57 homeassistant kernel: audit: type=1334 audit(1681834977.264:201): prog-id=14 op=UNLOAD
Apr 18 16:22:57 homeassistant kernel: audit: type=1334 audit(1681834977.264:202): prog-id=13 op=UNLOAD
Apr 18 16:22:57 homeassistant kernel: audit: type=1334 audit(1681834977.264:203): prog-id=12 op=UNLOAD
Apr 18 16:23:09 homeassistant systemd[1]: var-lib-docker-overlay2-7d815f3ad31630b9e27b12657d4e783170bec95b305873ed51056f3844933e1f\x2dinit-merged.mount: Deactivated successfully.
Apr 18 16:23:09 homeassistant systemd[1]: mnt-data-docker-overlay2-7d815f3ad31630b9e27b12657d4e783170bec95b305873ed51056f3844933e1f\x2dinit-merged.mount: Deactivated successfully.
Apr 18 16:23:09 homeassistant systemd[1]: var-lib-docker-overlay2-7d815f3ad31630b9e27b12657d4e783170bec95b305873ed51056f3844933e1f-merged.mount: Deactivated successfully.
Apr 18 16:23:09 homeassistant systemd[1]: mnt-data-docker-overlay2-7d815f3ad31630b9e27b12657d4e783170bec95b305873ed51056f3844933e1f-merged.mount: Deactivated successfully.
Apr 18 16:23:09 homeassistant NetworkManager[319]: <info> [1681834989.5172] manager: (vethaf7f565): new Veth device (/org/freedesktop/NetworkManager/Devices/19)
Apr 18 16:23:09 homeassistant kernel: hassio: port 7(vethe13a13f) entered blocking state
Apr 18 16:23:09 homeassistant kernel: hassio: port 7(vethe13a13f) entered disabled state
Apr 18 16:23:09 homeassistant kernel: device vethe13a13f entered promiscuous mode
Apr 18 16:23:09 homeassistant kernel: audit: type=1700 audit(1681834989.517:204): dev=vethe13a13f prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
Apr 18 16:23:09 homeassistant kernel: audit: type=1300 audit(1681834989.517:204): arch=c000003e syscall=44 success=yes exit=40 a0=c a1=c000a38690 a2=28 a3=0 items=0 ppid=1 pid=397 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj=unconfined key=(null)
Apr 18 16:23:09 homeassistant kernel: audit: type=1327 audit(1681834989.517:204): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D636F6E7461696E6572643D2F72756E2F636F6E7461696E6572642F636F6E7461696E6572642E736F636B
Apr 18 16:23:09 homeassistant NetworkManager[319]: <info> [1681834989.5216] manager: (vethe13a13f): new Veth device (/org/freedesktop/NetworkManager/Devices/20)
Apr 18 16:23:09 homeassistant systemd[1]: Started libcontainer container 481308628ffcd074969046225f8a9435aea56255ad7b6d1eb690b2e3f270004e.
Apr 18 16:23:09 homeassistant kernel: audit: type=1334 audit(1681834989.625:205): prog-id=52 op=LOAD
Apr 18 16:23:09 homeassistant kernel: audit: type=1334 audit(1681834989.625:206): prog-id=53 op=LOAD
Apr 18 16:23:09 homeassistant kernel: audit: type=1300 audit(1681834989.625:206): arch=c000003e syscall=321 success=yes exit=16 a0=5 a1=c00018d7f8 a2=78 a3=0 items=0 ppid=2881 pid=2890 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
Apr 18 16:23:09 homeassistant kernel: audit: type=1327 audit(1681834989.625:206): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F34383133303836323866666364303734393639303436323235
Apr 18 16:23:09 homeassistant kernel: audit: type=1334 audit(1681834989.625:207): prog-id=54 op=LOAD
Apr 18 16:23:09 homeassistant kernel: audit: type=1300 audit(1681834989.625:207): arch=c000003e syscall=321 success=yes exit=18 a0=5 a1=c00018d590 a2=78 a3=0 items=0 ppid=2881 pid=2890 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="runc" exe="/usr/bin/runc" subj=unconfined key=(null)
Apr 18 16:23:09 homeassistant kernel: audit: type=1327 audit(1681834989.625:207): proctitle=72756E63002D2D726F6F74002F7661722F72756E2F646F636B65722F72756E74696D652D72756E632F6D6F6279002D2D6C6F67002F72756E2F636F6E7461696E6572642F696F2E636F6E7461696E6572642E72756E74696D652E76322E7461736B2F6D6F62792F34383133303836323866666364303734393639303436323235
Apr 18 16:23:09 homeassistant kernel: eth0: renamed from vethaf7f565
Apr 18 16:23:09 homeassistant kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe13a13f: link becomes ready
Apr 18 16:23:09 homeassistant kernel: hassio: port 7(vethe13a13f) entered blocking state
Apr 18 16:23:09 homeassistant kernel: hassio: port 7(vethe13a13f) entered forwarding state
Apr 18 16:23:09 homeassistant NetworkManager[319]: <info> [1681834989.7906] device (vethe13a13f): carrier: link connected
Apr 18 16:23:14 homeassistant kernel: kauditd_printk_skb: 29 callbacks suppressed
Apr 18 16:23:14 homeassistant kernel: audit: type=1334 audit(1681834994.860:219): prog-id=56 op=LOAD
Apr 18 16:23:14 homeassistant kernel: audit: type=1334 audit(1681834994.861:220): prog-id=57 op=LOAD
Apr 18 16:23:14 homeassistant kernel: audit: type=1334 audit(1681834994.861:221): prog-id=58 op=LOAD
Apr 18 16:23:14 homeassistant systemd[1]: Starting Hostname Service...
Apr 18 16:23:14 homeassistant systemd[1]: Started Hostname Service.
Apr 18 16:23:15 homeassistant kernel: audit: type=1334 audit(1681834995.000:222): prog-id=59 op=LOAD
Apr 18 16:23:15 homeassistant kernel: audit: type=1334 audit(1681834995.001:223): prog-id=60 op=LOAD
Apr 18 16:23:15 homeassistant kernel: audit: type=1334 audit(1681834995.001:224): prog-id=61 op=LOAD
Apr 18 16:23:15 homeassistant systemd[1]: Starting Time & Date Service...
Apr 18 16:23:15 homeassistant systemd[1]: Started Time & Date Service.
Apr 18 16:23:45 homeassistant systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Apr 18 16:23:45 homeassistant kernel: audit: type=1334 audit(1681835025.038:225): prog-id=58 op=UNLOAD
Apr 18 16:23:45 homeassistant kernel: audit: type=1334 audit(1681835025.038:226): prog-id=57 op=UNLOAD
Apr 18 16:23:45 homeassistant kernel: audit: type=1334 audit(1681835025.038:227): prog-id=56 op=UNLOAD
Apr 18 16:23:45 homeassistant systemd[1]: systemd-timedated.service: Deactivated successfully.
Apr 18 16:23:45 homeassistant kernel: audit: type=1334 audit(1681835025.161:228): prog-id=61 op=UNLOAD
Apr 18 16:23:45 homeassistant kernel: audit: type=1334 audit(1681835025.161:229): prog-id=60 op=UNLOAD
Apr 18 16:23:45 homeassistant kernel: audit: type=1334 audit(1681835025.161:230): prog-id=59 op=UNLOAD
Apr 18 16:32:42 homeassistant dropbear[3091]: [3091] Apr 18 16:32:42 Child connection from 192.168.0.12:50710
Apr 18 16:32:42 homeassistant dropbear[3091]: [3091] Apr 18 16:32:42 Pubkey auth succeeded for 'root' with ssh-rsa key SHA256:5KG9InxtuSAC5RtRQ/pdqJU5u4duuGFcXq+KRToAnQc from 192.168.0.12:50710
Apr 18 16:37:22 homeassistant systemd[1]: Starting Cleanup of Temporary Directories...
Apr 18 16:37:22 homeassistant systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Apr 18 16:37:22 homeassistant systemd[1]: Finished Cleanup of Temporary Directories.
Apr 18 16:37:22 homeassistant systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
Apr 18 16:37:38 homeassistant kernel: audit: type=1334 audit(1681835858.696:231): prog-id=62 op=LOAD
Apr 18 16:37:38 homeassistant systemd-timesyncd[1197]: Network configuration changed, trying to establish connection.
Apr 18 16:37:38 homeassistant systemd-timesyncd[1197]: Contacted time server 192.168.0.254:123 (192.168.0.254).
Apr 18 16:37:38 homeassistant systemd[1]: Started Journal Gateway Service.
Apr 18 16:37:38 homeassistant systemd-journal-gatewayd[3113]: microhttpd: MHD_OPTION_EXTERNAL_LOGGER is not the first option specified for the daemon. Some messages may be printed by the standard MHD logger.
```
### System information
`## System Information
version | core-2023.4.5
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
user | root
virtualenv | false
python_version | 3.10.10
os_name | Linux
os_version | 6.1.24
arch | x86_64
timezone | Europe/Paris
config_dir | /config
<details><summary>Home Assistant Community Store</summary>
GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4975
Installed Version | 1.32.1
Stage | running
Available Repositories | 1274
Downloaded Repositories | 3
</details>
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 10.0
-- | --
update_channel | stable
supervisor_version | supervisor-2023.04.0
agent_version | 1.5.1
docker_version | 23.0.3
disk_total | 30.8 GB
disk_used | 3.9 GB
healthy | true
supported | true
board | ova
supervisor_api | ok
version_api | ok
installed_addons | Terminal & SSH (9.6.1), File editor (5.5.0)
</details>
<details><summary>Dashboards</summary>
dashboards | 2
-- | --
resources | 1
views | 5
mode | storage
</details>
<details><summary>Recorder</summary>
oldest_recorder_run | 12 avril 2023 à 19:39
-- | --
current_recorder_run | 18 avril 2023 à 18:22
estimated_db_size | 179.41 MiB
database_engine | sqlite
database_version | 3.38.5
[</details>`](url)
### Additional information
_No response_
I then switched to HA Supervised in the same VirtualBox VM and everything has run absolutely flawlessly since that moment. The flexibility and control I have with HA Supervised is so much better than with HA OS and so is also the CPU usage.
I know many say that HA Supervised is supposed to be complicated, but for me, it has been extremely easy and rock solid. I hate to be forced to go back. And I’m sure I’m not alone.
Please reconsider the decision to not support HA Supervised any more!
3 Likes
Would this break on HAOS upgrade? Based on partitioning .
francisp
(Francis)
June 12, 2025, 12:58pm
287
The boot partition is typically a FAT partition and contains system-specific content to enable booting.
That’s the boat I’m in I will keep running supervised in my case.