Host_internet: true, supervisor_internet: false

mikekehrli · June 25, 2025, 2:53pm

I’m trying to install a new version of the RPI4/Home Assistant OS. I keep running into the same issue. The host_internet is always true, but the supervisor_internet is always false. The time is wrong - off by a month which will play hell with ssl certificates. However, when I try to use the login command and fix the time, I am unable to do so. So, that may be all I need. How do I fix the time? But for sure, I have a problem with the supervisor having internet access - probably a docker translation issue. Any ideas?

mikekehrli · June 25, 2025, 3:41pm

I fixed it. I fixed the date. I was not doing it right and it was silently failing, so I didn’t know. If you put in the date correctly, it will then echo the new date. Here’s how to do it:

from the HA prompt, enter “login”
from the login prompt enter “bash”
then date -s ‘2025-06-25 13:34:56’ (use the current date/time)
it will then echo the correct date.
enter ‘exit’ ‘exit’ to return to the HA prompt.
“host reboot”

After the reboot, it came up with supervisor_internet: true, after which the web interface was able to complete it’s initialization and everything worked.

deviantintegral · June 27, 2025, 8:33pm

I’m seeing this on one install as well. In particular, it happens after a power outage if the Pi is booted before the internet comes up. Worse, it seems to break HA Cloud access too.

I wonder if this is a regression, because this install had been working fine for quite some time, even with semi-frequent power outages.

Floriszz · June 27, 2025, 8:35pm

I tried in ssh add-in on Homeassistant on Raspberry PI, but get the following error.
How to use bash? And is bash required to be able to set the date?

mikekehrli · July 5, 2025, 5:15pm

to use bash, from the ha prompt, give the command: login

mikekehrli · July 5, 2025, 5:23pm

If you lose power, you lose the time. There is no clock chip in a pi before pi5. I think pi5 might have one. But I keep my pi on a UPS so its unlikely to lose power.

If it does, you have to go back to the my fix above and re-set it again. It will be messed up after the power loss. But reboots will retain the time. Its just actual power off that causes it to lose its time.

mikekehrli · July 5, 2025, 5:28pm

Edit: Make sure your time zone settings are correct before doing these steps. Or after setting your time zone in Settings → System → General, come back and do the date -s command again. I like using the “Advanced SSH & Web Terminal” add on.

Floriszz · July 5, 2025, 5:51pm

next hurdle…

This is with the official ssh server add-on.
I would like to switch the “Advanced SSH & Web Terminal” , but as long this is issue is, no option to download or update anything😥

deviantintegral · July 5, 2025, 5:52pm

Based on my conversations with Nabu Casa support, it seems like what I’m experiencing is a regression since Home Assistant 2025.6. There were supposed to be fixes in 2025.7, but they aren’t helping my case.

The date / time aspect was a red herring and doesn’t seem to be an issue at all.

Here’s the components for debug logging, which surprisingly I couldn’t find elsewhere:

logger:
  default: info
  logs:
    homeassistant.components.cloud: debug
    hass_nabucasa: debug
    acme: debug
    snitun: debug

The logs show where the internet is down still (and DNS fails), and then some clearly incorrect detection of my subscription status after the internet comes back up:

2025-07-04 18:07:46.724 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'tag', 'stream', 'homekit', 'utility_meter', 'wake_on_lan', 'sonarr', 'zwave_js', 'go2rtc', 'delete', 'input_datetime', 'input_boolean', 'smartthinq_sensors', 'waqi', 'esphome', 'min_max', 'zone', 'plex', 'battery_notes', 'timer', 'input_text', 'adaptive_lighting', 'input_number', 'airthings_ble', 'threshold', 'prometheus', 'scene', 'lennoxs30', 'environment_canada', 'hacs', 'hardware', 'counter', 'switch', 'input_button', 'mqtt', 'sun', 'amcrest', 'application_credentials', 'ontario_energy_board', 'automation', 'notify', 'apple_tv', 'switch_as_x', 'template', 'webostv', 'wled', 'tasmota', 'schedule', 'analytics', 'unifi', 'mobile_app', 'input_select', 'powercalc', 'default_config', 'person', 'cover', 'system_health', 'proximity', 'season', 'auto_backup', 'nut', 'script', 'recollect_waste'} | {'binary_sensor', 'ffmpeg', 'bluetooth', 'group', 'backup', 'cloud', 'frontend', 'network', 'media_player', 'hassio', 'logger', 'light', 'tts', 'http'}
Dependencies: {'bluetooth_adapters', 'camera', 'image_upload', 'homeassistant_alerts', 'energy', 'media_source', 'device_tracker', 'trace', 'my', 'blueprint', 'history', 'logbook', 'select'} | {'dhcp', 'websocket_api', 'group', 'ssdp', 'frontend', 'search', 'recorder', 'webhook', 'lovelace', 'diagnostics', 'persistent_notification', 'assist_pipeline', 'device_automation', 'system_log', 'network', 'file_upload', 'repairs', 'usb', 'auth', 'light', 'http', 'onboarding', 'api', 'media_player', 'stt', 'tts', 'ffmpeg', 'bluetooth', 'wake_word', 'config', 'cloud', 'zeroconf', 'backup', 'conversation', 'intent', 'hassio'}
2025-07-04 18:08:00.789 WARNING (MainThread) [hass_nabucasa] Could not get subscription info
  File "/usr/local/lib/python3.13/site-packages/hass_nabucasa/__init__.py", line 464, in _async_get_billing_plan_type
  File "/usr/local/lib/python3.13/site-packages/hass_nabucasa/cloud_api.py", line 75, in check_token
    return await func(cloud, *args, **kwargs)
  File "/usr/local/lib/python3.13/site-packages/hass_nabucasa/cloud_api.py", line 329, in async_subscription_info
    resp = await cloud.websession.get(
aiohttp.client_exceptions.ClientConnectorDNSError: Cannot connect to host accounts.nabucasa.com:443 ssl:default [DNS server returned general failure]
2025-07-04 18:08:00.799 ERROR (MainThread) [hass_nabucasa] No subscription found
2025-07-04 18:08:00.801 INFO (MainThread) [hass_nabucasa] Subscription expired at 2025-12-27, waiting 3 hours for activation
2025-07-04 18:09:27.679 DEBUG (MainThread) [homeassistant.components.cloud.google_config] async_initialize
2025-07-04 18:09:27.679 DEBUG (MainThread) [homeassistant.components.cloud.google_config] async_initialize on_hass_start
2025-07-04 18:09:27.679 DEBUG (MainThread) [homeassistant.components.cloud.google_config] async_initialize on_hass_started
2025-07-04 18:09:47.742 DEBUG (MainThread) [hass_nabucasa.cloud_api] Fetched https://accounts.nabucasa.com/payments/subscription_info (200)
2025-07-04 18:09:47.742 DEBUG (MainThread) [hass_nabucasa.cloud_api] Found disconnected account with valid subscription, connecting

Floriszz · July 5, 2025, 6:06pm

It really has nothing to do with your nabu casa!
I have nabu casa as well, my subscription renewal is not there jet.
But you will see, that every package will give this dns error when you try to download/update.
All used to work fine in my setup, but from one day to the other I got the DNS error.

Floriszz · July 5, 2025, 6:25pm

I thought maybe the wifi adapter of the raspberry pi is seen as second NIC, although I don’t use the wifi and it is not configured, I read elsewhere that multiple NIC could be giving problems.
So I disabled the wifi adapter through editing the config.txt file.
But even after reboot this was to no avail.
After setting the config.txt file back to what it was I noticed the timestam was 2 hours off(18:16), while my time was at the moment GMT+1 Amsterdam DST(20:16)
I can imagine that the Host OS is in Zulu time(18:16), but I miss an hour of the DST(day light saving time).