Skip to content

Fresh HAOS Installation on Raspberry Pi 5 Stuck Due to Incorrect System Date #4041

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
datoml opened this issue Apr 27, 2025 · 0 comments
Open

Fresh HAOS Installation on Raspberry Pi 5 Stuck Due to Incorrect System Date #4041

datoml opened this issue Apr 27, 2025 · 0 comments
Labels
bug

Comments

@datoml
Copy link

datoml commented Apr 27, 2025 •
edited
Loading

Describe the issue you are experiencing

I recently received my new Raspberry Pi 5 and installed HAOS 15.2 using the Raspberry Pi Imager, following the official installation guide.
After booting up the system, HAOS was unable to download the latest Home Assistant image due to the following log message:

2024-05-27 21:50:34.360 WARNING (MainThread) [supervisor.utils.whoami] Whoami service failed with SSL verification: Cannot connect to host services.home-assistant.io:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1028)')]

This resulted in an endless loop where the system attempted to download the image every 30 seconds:

2024-05-27 23:50:40.865 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not healthy - setup
2024-05-27 23:51:10.793 WARNING (MainThread) [supervisor.jobs] 'Updater.fetch_data' blocked from execution, no supervisor internet connection
2024-05-27 23:51:10.793 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec
2024-05-27 23:51:40.939 WARNING (MainThread) [supervisor.jobs] 'Updater.fetch_data' blocked from execution, no supervisor internet connection

Additionally, I noticed the timestamps in the logs were incorrect.

To investigate further, I created a CONFIG USB stick with an SSH public key to gain SSH access.
Running the date command confirmed that the system date was incorrect, and hwclock also showed the wrong time.

Further investigation showed that the system was unable to synchronize with the NTP service.
I assume the incorrect date was causing SSL certificate validation to fail.

After setting the date and hwclock manually and rebooting the device HAOS was able to download the image.
The installation still was stuck caused by the Home Assistant observer to show that it was not in a healthy state.
So I ran the ha supervisor restart command using SSH and finally it was working.

I attempted a fresh installation again using the Raspberry Pi Imager, and the same issue occurred.
It seems there is a recurring problem where HAOS cannot retrieve the correct date/time during the initial setup, leading to SSL errors and blocking the installation.

Is this issue caused by some fautly configuration in HAOS or is it recommanded to add the battery extension to PI5 to store the RTC value?

I also noticed in host logs that my Fritz.Box is not able to provide correct time settings.

Update

After testing the NTP feature of my fritz.box it returned the following message:

w32tm /monitor /computers:192.168.178.1
192.168.178.1[192.168.178.1:123]:
    ICMP: 0ms Verzögerung
    NTP: Fehler ERROR_TIMEOUT - Keine Rückmeldung vom Server seit 1000ms

I found a reply from my ISP that there was / is a bug with fritz.box and I need to enter the IP for the timeserver.
After changing the setup I get now this response:

w32tm /monitor /computers:192.168.178.1
192.168.178.1[192.168.178.1:123]:
    ICMP: 0ms Verzögerung
    NTP: -2.0639349s Offset von lokaler Zeit
        RefID: (nicht angegeben / nicht synchronisiert) [0x00000000]
        Stratum: 0

What operating system image do you use?

rpi5-64 (Raspberry Pi 5 64-bit OS)

What version of Home Assistant Operating System is installed?

15.2

Did the problem occur after upgrading the Operating System?

No

Hardware details

Raspberry Pi 5 16GB

Steps to reproduce the issue

  1. Install latest version of HOAS (15.2) using Raspberry Pi Imager
  2. Power up PI5
  3. System is not able to connect to online services caused by SSL certificate not valid yet.

Anything in the Supervisor logs that might be useful for us?

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/udev.sh
[21:50:31] INFO: �[32mUsing udev information from host�[0m
cont-init: info: /etc/cont-init.d/udev.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun supervisor (no readiness notification)
services-up: info: copying legacy longrun watchdog (no readiness notification)
[21:50:31] INFO: �[32mStarting local supervisor watchdog...�[0m
s6-rc: info: service legacy-services successfully started
�[32m2024-05-27 21:50:33.937 INFO (MainThread) [__main__] Initializing Supervisor setup�[0m
�[32m2024-05-27 21:50:33.950 INFO (MainThread) [supervisor.docker.network] Can't find Supervisor network, creating a new network�[0m
�[32m2024-05-27 21:50:34.131 INFO (MainThread) [supervisor.coresys] Setting up coresys for machine: raspberrypi5-64�[0m
�[32m2024-05-27 21:50:34.136 INFO (MainThread) [supervisor.docker.supervisor] Attaching to Supervisor ghcr.io/home-assistant/aarch64-hassio-supervisor with version 2025.04.0�[0m
�[32m2024-05-27 21:50:34.136 INFO (MainThread) [supervisor.docker.supervisor] Connecting Supervisor to hassio-network�[0m
�[32m2024-05-27 21:50:34.261 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state initialize�[0m
�[32m2024-05-27 21:50:34.263 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete�[0m
�[32m2024-05-27 21:50:34.264 INFO (MainThread) [__main__] Setting up Supervisor�[0m
�[32m2024-05-27 21:50:34.435 INFO (MainThread) [supervisor.api] Starting API on 172.30.32.2�[0m
�[32m2024-05-27 21:50:34.483 INFO (MainThread) [supervisor.hardware.monitor] Started Supervisor hardware monitor�[0m
�[32m2024-05-27 21:50:34.484 INFO (MainThread) [supervisor.dbus.manager] Connected to system D-Bus.�[0m
�[32m2024-05-27 21:50:34.484 INFO (MainThread) [supervisor.dbus.agent] Load dbus interface io.hass.os�[0m
�[32m2024-05-27 21:50:34.485 INFO (MainThread) [supervisor.dbus.hostname] Load dbus interface org.freedesktop.hostname1�[0m
�[32m2024-05-27 21:50:34.485 INFO (MainThread) [supervisor.dbus.logind] Load dbus interface org.freedesktop.login1�[0m
�[32m2024-05-27 21:50:34.485 INFO (MainThread) [supervisor.dbus.network] Load dbus interface org.freedesktop.NetworkManager�[0m
�[32m2024-05-27 21:50:34.486 INFO (MainThread) [supervisor.dbus.rauc] Load dbus interface de.pengutronix.rauc�[0m
�[32m2024-05-27 21:50:34.486 INFO (MainThread) [supervisor.dbus.resolved] Load dbus interface org.freedesktop.resolve1�[0m
�[32m2024-05-27 21:50:34.486 INFO (MainThread) [supervisor.dbus.systemd] Load dbus interface org.freedesktop.systemd1�[0m
�[32m2024-05-27 21:50:34.486 INFO (MainThread) [supervisor.dbus.timedate] Load dbus interface org.freedesktop.timedate1�[0m
�[32m2024-05-27 21:50:34.643 INFO (MainThread) [supervisor.host.services] Updating service information�[0m
�[32m2024-05-27 21:50:34.647 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information�[0m
�[33m2024-05-27 21:50:34.651 WARNING (SyncWorker_2) [supervisor.host.sound] Can't update PulseAudio data: Failed to connect to pulseaudio server�[0m
�[32m2024-05-27 21:50:34.790 INFO (MainThread) [supervisor.host.network] Updating local network information�[0m
�[32m2024-05-27 21:50:34.818 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}�[0m
�[33m2024-05-27 21:50:34.978 WARNING (MainThread) [supervisor.utils.whoami] Whoami service failed with SSL verification: Cannot connect to host services.home-assistant.io:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1028)')]�[0m
�[32m2024-05-27 21:50:34.978 INFO (MainThread) [supervisor.core] Whoami service SSL error�[0m
�[33m2024-05-27 23:50:35.021 WARNING (MainThread) [supervisor.core] System time/date shift over more than 3 days found!�[0m
�[32m2024-05-27 23:50:35.021 INFO (MainThread) [supervisor.host.control] Setting new host datetime: 2025-04-26T20:02:05+00:00�[0m
�[31m2024-05-27 23:50:35.025 CRITICAL (MainThread) [supervisor.core] Fatal error happening on load Task <coroutine object Core._adjust_system_datetime at 0x7f90157790>: Automatic time synchronization is enabled�[0m
�[32m2024-05-27 23:50:35.029 INFO (MainThread) [supervisor.docker.monitor] Started docker events monitor�[0m
�[32m2024-05-27 23:50:35.038 INFO (MainThread) [supervisor.docker.interface] Found ghcr.io/home-assistant/aarch64-hassio-cli versions: [<AwesomeVersion CalVer '2025.04.0'>]�[0m
�[32m2024-05-27 23:50:35.042 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-cli with version 2025.04.0�[0m
�[32m2024-05-27 23:50:35.068 INFO (MainThread) [supervisor.plugins.cli] Starting CLI plugin�[0m
�[32m2024-05-27 23:50:35.886 INFO (MainThread) [supervisor.docker.cli] Starting CLI ghcr.io/home-assistant/aarch64-hassio-cli with version 2025.04.0 - 172.30.32.5�[0m
�[32m2024-05-27 23:50:35.916 INFO (MainThread) [supervisor.docker.interface] Found ghcr.io/home-assistant/aarch64-hassio-dns versions: [<AwesomeVersion CalVer '2025.02.0'>]�[0m
�[32m2024-05-27 23:50:35.921 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-dns with version 2025.02.0�[0m
�[32m2024-05-27 23:50:35.961 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin�[0m
�[32m2024-05-27 23:50:36.875 INFO (MainThread) [supervisor.docker.dns] Starting DNS ghcr.io/home-assistant/aarch64-hassio-dns with version 2025.02.0 - 172.30.32.3�[0m
�[32m2024-05-27 23:50:36.876 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf�[0m
�[32m2024-05-27 23:50:36.904 INFO (MainThread) [supervisor.docker.interface] Found ghcr.io/home-assistant/aarch64-hassio-audio versions: [<AwesomeVersion CalVer '2025.02.0'>]�[0m
�[32m2024-05-27 23:50:36.912 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-audio with version 2025.02.0�[0m
�[32m2024-05-27 23:50:36.959 INFO (MainThread) [supervisor.plugins.audio] Starting Audio plugin�[0m
�[32m2024-05-27 23:50:38.062 INFO (MainThread) [supervisor.docker.audio] Starting Audio ghcr.io/home-assistant/aarch64-hassio-audio with version 2025.02.0 - 172.30.32.4�[0m
�[32m2024-05-27 23:50:38.093 INFO (MainThread) [supervisor.docker.interface] Found ghcr.io/home-assistant/aarch64-hassio-observer versions: [<AwesomeVersion CalVer '2025.02.0'>]�[0m
�[32m2024-05-27 23:50:38.098 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-observer with version 2025.02.0�[0m
�[32m2024-05-27 23:50:38.166 INFO (MainThread) [supervisor.plugins.observer] Starting observer plugin�[0m
�[32m2024-05-27 23:50:39.334 INFO (MainThread) [supervisor.docker.observer] Starting Observer ghcr.io/home-assistant/aarch64-hassio-observer with version 2025.02.0 - 172.30.32.6�[0m
�[32m2024-05-27 23:50:39.349 INFO (MainThread) [supervisor.docker.interface] Found ghcr.io/home-assistant/aarch64-hassio-multicast versions: [<AwesomeVersion CalVer '2025.02.0'>]�[0m
�[32m2024-05-27 23:50:39.354 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/aarch64-hassio-multicast with version 2025.02.0�[0m
�[32m2024-05-27 23:50:39.379 INFO (MainThread) [supervisor.plugins.multicast] Starting Multicast plugin�[0m
�[32m2024-05-27 23:50:40.438 INFO (MainThread) [supervisor.docker.multicast] Starting Multicast ghcr.io/home-assistant/aarch64-hassio-multicast with version 2025.02.0 - Host�[0m
�[32m2024-05-27 23:50:40.440 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 0 Home Assistant secrets�[0m
�[32m2024-05-27 23:50:40.455 INFO (MainThread) [supervisor.docker.interface] No version found for ghcr.io/home-assistant/raspberrypi5-64-homeassistant�[0m
�[32m2024-05-27 23:50:40.455 INFO (MainThread) [supervisor.homeassistant.core] No Home Assistant Docker image ghcr.io/home-assistant/raspberrypi5-64-homeassistant found.�[0m
�[32m2024-05-27 23:50:40.460 INFO (MainThread) [supervisor.docker.interface] Attaching to ghcr.io/home-assistant/raspberrypi5-64-homeassistant with version landingpage�[0m
�[32m2024-05-27 23:50:40.460 INFO (MainThread) [supervisor.homeassistant.core] Using preinstalled landingpage�[0m
�[32m2024-05-27 23:50:40.485 INFO (MainThread) [supervisor.homeassistant.core] Starting HomeAssistant landingpage�[0m
�[32m2024-05-27 23:50:40.523 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulse�[0m
�[32m2024-05-27 23:50:41.416 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/raspberrypi5-64-homeassistant with version landingpage�[0m
�[32m2024-05-27 23:50:41.449 INFO (MainThread) [supervisor.os.manager] Detect Home Assistant Operating System 15.2 / BootSlot A�[0m
�[33m2024-05-27 23:50:41.451 WARNING (MainThread) [supervisor.jobs] 'GitRepo.clone' blocked from execution, no supervisor internet connection�[0m
�[31m2024-05-27 23:50:41.451 ERROR (MainThread) [supervisor.store] Can't add repository https://github.com/hassio-addons/repository due to 'GitRepo.clone' blocked from execution, no supervisor internet connection�[0m
�[32m2024-05-27 23:50:41.451 INFO (MainThread) [supervisor.resolution.module] Create new suggestion execute_reload - store / a0d7b954�[0m
�[32m2024-05-27 23:50:41.452 INFO (MainThread) [supervisor.resolution.module] Create new issue fatal_error - store / a0d7b954�[0m
�[33m2024-05-27 23:50:41.452 WARNING (MainThread) [supervisor.jobs] 'GitRepo.clone' blocked from execution, no supervisor internet connection�[0m
�[31m2024-05-27 23:50:41.452 ERROR (MainThread) [supervisor.store] Can't add repository core due to 'GitRepo.clone' blocked from execution, no supervisor internet connection�[0m
�[32m2024-05-27 23:50:41.452 INFO (MainThread) [supervisor.resolution.module] Create new suggestion execute_reload - store / core�[0m
�[32m2024-05-27 23:50:41.452 INFO (MainThread) [supervisor.resolution.module] Create new issue fatal_error - store / core�[0m
�[33m2024-05-27 23:50:41.452 WARNING (MainThread) [supervisor.jobs] 'GitRepo.clone' blocked from execution, no supervisor internet connection�[0m
�[31m2024-05-27 23:50:41.452 ERROR (MainThread) [supervisor.store] Can't add repository https://github.com/esphome/home-assistant-addon due to 'GitRepo.clone' blocked from execution, no supervisor internet connection�[0m
�[32m2024-05-27 23:50:41.452 INFO (MainThread) [supervisor.resolution.module] Create new suggestion execute_reload - store / 5c53de3b�[0m
�[32m2024-05-27 23:50:41.452 INFO (MainThread) [supervisor.resolution.module] Create new issue fatal_error - store / 5c53de3b�[0m
�[33m2024-05-27 23:50:41.452 WARNING (MainThread) [supervisor.jobs] 'GitRepo.clone' blocked from execution, no supervisor internet connection�[0m
�[31m2024-05-27 23:50:41.453 ERROR (MainThread) [supervisor.store] Can't add repository https://github.com/music-assistant/home-assistant-addon due to 'GitRepo.clone' blocked from execution, no supervisor internet connection�[0m
�[32m2024-05-27 23:50:41.453 INFO (MainThread) [supervisor.resolution.module] Create new suggestion execute_reload - store / d5369777�[0m
�[32m2024-05-27 23:50:41.453 INFO (MainThread) [supervisor.resolution.module] Create new issue fatal_error - store / d5369777�[0m
�[32m2024-05-27 23:50:41.457 INFO (MainThread) [supervisor.store] Loading add-ons from store: 0 all - 0 new - 0 remove�[0m
�[32m2024-05-27 23:50:41.457 INFO (MainThread) [supervisor.addons.manager] Found 0 installed add-ons�[0m
�[32m2024-05-27 23:50:41.459 INFO (MainThread) [supervisor.backups.manager] Found 0 backup files�[0m
�[32m2024-05-27 23:50:41.459 INFO (MainThread) [supervisor.discovery] Loaded 0 messages�[0m
�[32m2024-05-27 23:50:41.459 INFO (MainThread) [supervisor.ingress] Loaded 0 ingress sessions�[0m
�[32m2024-05-27 23:50:41.459 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state setup�[0m
�[32m2024-05-27 23:50:41.459 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system�[0m
�[32m2024-05-27 23:50:41.459 INFO (MainThread) [supervisor.resolution.checks.base] Run check for detached_addon_removed/addon�[0m
�[32m2024-05-27 23:50:41.460 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disabled_data_disk/system�[0m
�[32m2024-05-27 23:50:41.460 INFO (MainThread) [supervisor.resolution.checks.base] Run check for detached_addon_missing/addon�[0m
�[32m2024-05-27 23:50:41.460 INFO (MainThread) [supervisor.resolution.check] System checks complete�[0m
�[32m2024-05-27 23:50:41.460 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state setup�[0m
�[32m2024-05-27 23:50:41.460 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete�[0m
�[32m2024-05-27 23:50:41.461 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not healthy - setup�[0m
�[32m2024-05-27 23:50:41.461 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state setup�[0m
�[32m2024-05-27 23:50:41.461 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete�[0m
�[32m2024-05-27 23:50:41.462 INFO (MainThread) [__main__] Running Supervisor�[0m
�[31m2024-05-27 23:50:41.463 CRITICAL (MainThread) [supervisor.core] System is running in an unhealthy state and needs manual intervention!�[0m
�[32m2024-05-27 23:50:41.515 INFO (MainThread) [supervisor.os.manager] Rauc: slot A - activated slot kernel.0, marked slot kernel.0 as good�[0m
�[32m2024-05-27 23:50:41.522 INFO (MainThread) [supervisor.addons.manager] Phase 'initialize' starting 0 add-ons�[0m
�[32m2024-05-27 23:50:41.533 INFO (MainThread) [supervisor.addons.manager] Phase 'system' starting 0 add-ons�[0m
�[32m2024-05-27 23:50:41.533 INFO (MainThread) [supervisor.addons.manager] Phase 'services' starting 0 add-ons�[0m
�[32m2024-05-27 23:50:41.536 INFO (MainThread) [supervisor.core] Skipping start of Home Assistant�[0m
�[32m2024-05-27 23:50:41.536 INFO (MainThread) [supervisor.addons.manager] Phase 'application' starting 0 add-ons�[0m
�[32m2024-05-27 23:50:41.548 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled�[0m
�[32m2024-05-27 23:50:41.548 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant setup�[0m
�[33m2024-05-27 23:50:41.549 WARNING (MainThread) [supervisor.jobs] 'Updater.fetch_data' blocked from execution, no supervisor internet connection�[0m
�[33m2024-05-27 23:50:41.549 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retrying in 30sec�[0m
�[32m2024-05-27 23:50:41.549 INFO (MainThread) [supervisor.host.info] Updating local host information�[0m
�[33m2024-05-27 23:50:41.549 WARNING (MainThread) [supervisor.jobs] 'Updater.fetch_data' blocked from execution, no supervisor internet connection�[0m

Anything in the Host logs that might be useful for us?

2024-05-27 21:50:19.829 homeassistant systemd-resolved[521]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 192.168.178.1.
2024-05-27 21:50:19.846 homeassistant dropbear[689]: [689] May 27 21:50:19 Generated hostkey /etc/dropbear/dropbear_ed25519_host_key, fingerprint is SHA256:iJdbfNwd+K1PuVCwYXE0v1Ii3otDk8FMMvxSwOjR/N4
2024-05-27 21:50:23.184 homeassistant dropbear[689]: [689] May 27 21:50:23 Pubkey auth succeeded for 'root' with ssh-rsa key SHA256:sSnBtwOcZjd9o4tdvjV+s9euwGP/SBHaVbxKB68LZrU from 192.168.178.50:55145
2024-05-27 21:50:23.621 homeassistant systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
2024-05-27 21:50:23.795 homeassistant systemd-timesyncd[685]: Timed out waiting for reply from 192.168.178.1:123 (192.168.178.1).
2024-05-27 21:50:28.545 homeassistant systemd[1]: systemd-time-wait-sync.service: start operation timed out. Terminating.
2024-05-27 21:50:28.546 homeassistant systemd-time-wait-sync[679]: Exit without adjtimex synchronized.
2024-05-27 21:50:28.559 homeassistant systemd[1]: systemd-time-wait-sync.service: Failed with result 'timeout'.
2024-05-27 21:50:28.559 homeassistant systemd[1]: Failed to start Wait Until Kernel Time Synchronized.
2024-05-27 21:50:28.560 homeassistant systemd[1]: Reached target System Time Synchronized.

System information

System Information

version core-2025.4.4
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.13.2
os_name Linux
os_version 6.6.74-haos-raspi
arch aarch64
timezone Europe/Vienna
config_dir /config
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 15.2
update_channel stable
supervisor_version supervisor-2025.04.0
agent_version 1.7.2
docker_version 28.0.4
disk_total 28.5 GB
disk_used 8.9 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized false
virtualization
board rpi5-64
supervisor_api ok
version_api ok
installed_addons Studio Code Server (5.19.2)
Dashboards
dashboards 2
resources 0
views 0
mode storage
Network Configuration
adapters lo (disabled), end0 (enabled, default, auto), docker0 (disabled), hassio (disabled), vethc568e6f (disabled), veth3a4582a (disabled), veth3216bcd (disabled), veth3a3742b (disabled), veth506db9b (disabled), veth1c049e9 (disabled)
ipv4_addresses lo (127.0.0.1/8), end0 (192.168.178.35/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), vethc568e6f (), veth3a4582a (), veth3216bcd (), veth3a3742b (), veth506db9b (), veth1c049e9 ()
ipv6_addresses lo (::1/128), end0 (fd05:6b35:7874:a445:d5f9:2d9b:7271:ee1d/64, fe80::4828:3a56:cb35:8515/64), docker0 (fe80::74ea:18ff:fe91:16c0/64), hassio (fe80::8c05:6eff:fee4:f721/64), vethc568e6f (fe80::a07e:67ff:fe58:f6ba/64), veth3a4582a (fe80::84ef:47ff:fef6:2635/64), veth3216bcd (fe80::38ea:e2ff:fe4c:d815/64), veth3a3742b (fe80::c80c:1dff:fe54:8756/64), veth506db9b (fe80::8e1:6dff:fe3c:da2d/64), veth1c049e9 (fe80::44ba:40ff:fe74:8fb6/64)
announce_addresses 192.168.178.35, fd05:6b35:7874:a445:d5f9:2d9b:7271:ee1d, fe80::4828:3a56:cb35:8515
Recorder
oldest_recorder_run 26. April 2025 um 20:21
current_recorder_run 26. April 2025 um 22:21
estimated_db_size 5.68 MiB
database_engine sqlite
database_version 3.48.0

Additional information

No response
@datoml datoml added the bug label Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@datoml