Home assistant web interface not accessible also Companion App not accessible

Hi,

Since Yesterday I have a problem that the Web interface is not starting anymore also to HA Companion app cannot connect to the HA environment anymore. Strangely enough this happened after a clean restart of the system.
Surprisingly motion connectors are still working and activate light switches so a part of the system is still working.
No update or modifications have been installed or made recently into the system.

I allready tried clearing the cache of my browser, unfortunately without any luck.
Also checked the IP-bans.Yaml to check if my IP was blocked, also this is not the case.
Within the log file I see some errors, but in my opinion these are not errors that explain this behavior.

Hopefully someone can help out.

Thanks in advance.

Are you using http://homeassistant.local:8123/ to connect?

If you are using the actual IP address of Home Assistant, has it changed?

How are you checking log files etc?

Hi Jack,

Thnx for you reply, I always connect locally via the IP-address I also scanned my network and the IP-address for HA hasn’t changed.
Via the Explorer I checked in the config folder the home-assistant.log file.

Connecting to the observer on port 4357 on the same IP-address is working just fine.
It says Supervisor Connected and System Healthy.
Also restarted the several times unfortunately no success.

Update:
Just looked at the HomeAssistant log again after a restart, could it be that a Component is causing this issue?
Perhaps someone can read the log and point me to a possible solution?

Homeassistant.log:

2025-06-06 10:03:19.780 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration lghorizon which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-06-06 10:03:19.782 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-06-06 10:03:19.784 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration eufy_security which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-06-06 10:03:19.785 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration bold which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-06-06 10:03:19.786 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration webrtc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-06-06 10:03:19.787 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-06-06 10:03:19.788 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sonoff which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-06-06 10:03:22.242 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2025-06-06 10:03:22.276 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=459 from 2025-06-05 09:53:54.220937)
2025-06-06 10:03:27.170 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'sonoff' accesses hass.helpers.system_info, which should be updated to import functions used from system_info directly at custom_components/sonoff/system_health.py, line 60: info = await hass.helpers.system_info.async_get_system_info(). This will stop working in Home Assistant 2025.5, please create a bug report at https://github.com/AlexxIT/SonoffLAN/issues
2025-06-06 10:03:27.189 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to walk with args ('/config/custom_components/sonoff',) inside the event loop by custom integration 'sonoff' at custom_components/sonoff/core/const.py, line 33: for root, dirs, files in os.walk(path): (offender: /config/custom_components/sonoff/core/const.py, line 33: for root, dirs, files in os.walk(path):), please create a bug report at https://github.com/AlexxIT/SonoffLAN/issues
For developers, please see https://developers.home-assistant.io/docs/asyncio_blocking_operations/#walk
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 227, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 213, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 154, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 712, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 683, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.13/asyncio/base_events.py", line 2040, in _run_once
    handle._run()
  File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/setup.py", line 171, in async_setup_component
    result = await _async_setup_component(hass, domain, config)
  File "/usr/src/homeassistant/homeassistant/setup.py", line 467, in _async_setup_component
    await asyncio.gather(
  File "/usr/src/homeassistant/homeassistant/setup.py", line 469, in <genexpr>
    create_eager_task(
  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 45, in create_eager_task
    return Task(coro, loop=loop, name=name, eager_start=True)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 896, in async_setup_locked
    await self.async_setup(hass, integration=integration)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 662, in async_setup
    await self.__async_setup_with_context(hass, integration)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 751, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
  File "/config/custom_components/sonoff/__init__.py", line 185, in async_setup_entry
    await system_health.setup_debug(hass, _LOGGER)
  File "/config/custom_components/sonoff/system_health.py", line 61, in setup_debug
    info[DOMAIN + "_version"] = f"{integration.version} ({source_hash()})"
  File "/config/custom_components/sonoff/core/const.py", line 33, in source_hash
    for root, dirs, files in os.walk(path):

This morning did an update via the console, after the restart everything was accesible again.
No idea what the exact reason was for this phenomenon or behavior I’m glad it’s working again.

1 Like