Home assistant keeps going offline

Installation
1

Mine has been rock solid for years - on a mini PC.
Was offline this morning.
Powered it off and on with the switch on the mini PC, and it came back. After 5 mins - it went offline again.
The system/logs only seem to show from the last boot.
Any ideas on this ? Can I access the other logs ?
The network port can still be pinged so something is still there.

Its times like this you realize how much you depend on it - if I can get it up, and a backup (I have them daily anyway), then I may spin up a docker container on unraid and port it all there for some high availability.

2

Hello vwkombi,

How to get to your log after restart/restore.

For more info:
The Home Assistant Cookbook - Index.

3

Well - that seems rather technical and quite a bit above my pay grade.

I have pulled the mini PC back to my desk, and connected up a monitor. It boots and says "System is ready! Use a browser or app to configure, and I am at the green ha > prompt.

I am waiting to see if anything bad happens there - while I find a keyboard I can use on it, and a long network cable - maybe easier of me to move the monitor to the device in the garage now I come to think of it!

So if I have the HA prompt, and it stays stable, is there anything I can do from in there ?

4

FYI: That’s pretty much the worst thing you can do.

Hook up a keyboard and monitor for CLI access.

https://www.home-assistant.io/common-tasks/os#home-assistant-via-the-command-line

5

None of that is more difficult than this:

6

I started on docker many years back in my HA journey - frequent USB device name changes were a pain, so I moved to a VM. Then I discovered frigate and needed a bot more power - hence the mini PC.

I have now removed the need for any USB’s so I could move back to docker - but I would worry about the frigate load.

7

ok - so I have a keyboard in the garare and a monitor, and I am at the HA promote - unfortunately I have a long way to travel between this internet connect and the garage, and cant copy from one screen to another, so have to write commands down and take them there and key in.

To an intensive purposes, it seems fine.

It is showing the correct IP address, I can ping it from all devices on lan.

No errors on the screen.

What commands can I do from the HA prompt in HAOS to fault find this ?

8

Further to this, the samba add on it working, as I can see the network shares… So I can update the backup to only an hour ago.

9

The logs after every system startup - if that helps anything :slight_smile:
2025-10-21 12:21:56.092 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration bureau_of_meteorology 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-10-21 12:21:56.093 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-10-21 12:21:56.094 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration powercalc 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-10-21 12:21:56.095 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration currentcost 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-10-21 12:21:56.095 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman 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-10-21 12:21:56.096 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration llmvision 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-10-21 12:21:56.096 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-10-21 12:21:56.097 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate 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-10-21 12:21:56.098 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tesla_custom 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-10-21 12:21:56.098 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-10-21 12:21:56.099 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartthinq_sensors 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-10-21 12:21:57.151 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-10-21 12:21:57.170 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=544 from 2025-10-21 02:18:59.875585)
2025-10-21 12:21:57.430 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=(

WM Logo
WM Logo256×256 4.66 KB
Watchman report

Missing Entities: {{ states.sensor.watchman_missing_entities.state }}

{%- for item in state_attr(“sensor.watchman_missing_entities”, “entities”) %}
<ha-icon icon=‘mdi: {%- if item.state==“missing”-%}cloud-alert’ {%- elif item.state==“unavail” -%}cloud-off-outline’ {%- else-%}cloud-question’ {%- endif -%} > {{ item.id }} [{{item.state}}] {{item.occurrences.split(‘/’)[-1].split(‘:’)[0]}}
{%- endfor %}) renders=2>
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/template/init.py”, line 494, in async_render
render_result = render_with_context(self.template, compiled, **kwargs)
File “/usr/src/homeassistant/homeassistant/helpers/template/context.py”, line 45, in render_with_context
return template.render(**kwargs)
~~~~~~~~~~~~~~~^^^^^^^^^^
File “/usr/local/lib/python3.13/site-packages/jinja2/environment.py”, line 1295, in render
self.environment.handle_exception()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File “/usr/local/lib/python3.13/site-packages/jinja2/environment.py”, line 942, in handle_exception
raise rewrite_traceback_stack(source=source)
File “”, line 1, in top-level template code
jinja2.exceptions.UndefinedError: ‘None’ has no attribute ‘state’

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/template/init.py”, line 611, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
variables, strict=strict, log_fn=log_fn, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File “/usr/src/homeassistant/homeassistant/helpers/template/init.py”, line 496, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: ‘None’ has no attribute ‘state’
2025-10-21 12:21:57.964 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=(

WM Logo
WM Logo256×256 4.66 KB
Watchman report

Missing Entities: {{ states.sensor.watchman_missing_entities.state }}

{%- for item in state_attr(“sensor.watchman_missing_entities”, “entities”) %}
<ha-icon icon=‘mdi: {%- if item.state==“missing”-%}cloud-alert’ {%- elif item.state==“unavail” -%}cloud-off-outline’ {%- else-%}cloud-question’ {%- endif -%} > {{ item.id }} [{{item.state}}] {{item.occurrences.split(‘/’)[-1].split(‘:’)[0]}}
{%- endfor %}) renders=6>
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/template/init.py”, line 494, in async_render
render_result = render_with_context(self.template, compiled, **kwargs)
File “/usr/src/homeassistant/homeassistant/helpers/template/context.py”, line 45, in render_with_context
return template.render(**kwargs)
~~~~~~~~~~~~~~~^^^^^^^^^^
File “/usr/local/lib/python3.13/site-packages/jinja2/environment.py”, line 1295, in render
self.environment.handle_exception()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File “/usr/local/lib/python3.13/site-packages/jinja2/environment.py”, line 942, in handle_exception
raise rewrite_traceback_stack(source=source)
File “”, line 1, in top-level template code
jinja2.exceptions.UndefinedError: ‘None’ has no attribute ‘state’

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/template/init.py”, line 611, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
variables, strict=strict, log_fn=log_fn, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File “/usr/src/homeassistant/homeassistant/helpers/template/init.py”, line 496, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: UndefinedError: ‘None’ has no attribute ‘state’
2025-10-21 12:22:01.110 WARNING (MainThread) [custom_components.sonoff] Can’t login in auto mode: AuthError(‘password error!’)
2025-10-21 12:22:03.515 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open with args (‘/root/.netrc’,) inside the event loop by integration ‘google_generative_ai_conversation’ at homeassistant/components/google_generative_ai_conversation/init.py, line 165: await client.aio.models.get( (offender: /usr/local/lib/python3.13/netrc.py, line 87: with open(file, encoding=“utf-8”) as fp:), please create a bug report at GitHub · Where software is built
For developers, please see Blocking operations with asyncio | Home Assistant Developer Docs
Traceback (most recent call last):
File “”, line 198, in _run_module_as_main
File “”, line 88, in _run_code
File “/usr/src/homeassistant/homeassistant/main.py”, line 229, in
sys.exit(main())
File “/usr/src/homeassistant/homeassistant/main.py”, line 215, in main
exit_code = runner.run(runtime_conf)
File “/usr/src/homeassistant/homeassistant/runner.py”, line 271, 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 2050, 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/config_entries.py”, line 906, in async_setup_locked
await self.async_setup(hass, integration=integration)
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 672, in async_setup
await self.__async_setup_with_context(hass, integration)
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 761, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
File “/usr/src/homeassistant/homeassistant/components/google_generative_ai_conversation/init.py”, line 165, in async_setup_entry
await client.aio.models.get(

2025-10-21 12:22:04.319 ERROR (Thread-7) [pychromecast.socket_client] [Master bedroom speaker(73ed4afe-cd6b-91d7-9c55-412ca810bdc6.local.):8009] Failed to connect to service MDNSServiceInfo(name=‘Google-Home-73ed4afecd6b91d79c55412ca810bdc6._googlecast._tcp.local.’), retrying in 5.0s
2025-10-21 12:22:04.381 ERROR (Thread-10) [pychromecast.socket_client] [Lounge speaker(f560494c-11ea-72c3-11a8-8cc004c91d66.local.):8009] Failed to connect to service MDNSServiceInfo(name=‘Google-Home-f560494c11ea72c311a88cc004c91d66._googlecast._tcp.local.’), retrying in 5.0s
2025-10-21 12:22:04.381 ERROR (Thread-8) [pychromecast.socket_client] [Tallons Room speaker(8f867fab-80c5-1746-d28b-e1d519fd8933.local.):8009] Failed to connect to service MDNSServiceInfo(name=‘Google-Nest-Mini-8f867fab80c51746d28be1d519fd8933._googlecast._tcp.local.’), retrying in 5.0s
2025-10-21 12:22:05.485 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=(

WM Logo
WM Logo256×256 4.66 KB
Watchman report

Missing Entities: {{ states.sensor.watchman_missing_entities.state }}

{%- for item in state_attr(“sensor.watchman_missing_entities”, “entities”) %}
<ha-icon icon=‘mdi: {%- if item.state==“missing”-%}cloud-alert’ {%- elif item.state==“unavail” -%}cloud-off-outline’ {%- else-%}cloud-question’ {%- endif -%} > {{ item.id }} [{{item.state}}] {{item.occurrences.split(‘/’)[-1].split(‘:’)[0]}}
{%- endfor %}) renders=12>
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/template/init.py”, line 494, in async_render
render_result = render_with_context(self.template, compiled, **kwargs)
File “/usr/src/homeassistant/homeassistant/helpers/template/context.py”, line 45, in render_with_context
return template.render(**kwargs)
~~~~~~~~~~~~~~~^^^^^^^^^^
File “/usr/local/lib/python3.13/site-packages/jinja2/environment.py”, line 1295, in render
self.environment.handle_exception()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File “/usr/local/lib/python3.13/site-packages/jinja2/environment.py”, line 942, in handle_exception
raise rewrite_traceback_stack(source=source)
File “”, line 1, in top-level template code
TypeError: ‘NoneType’ object is not iterable

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/template/init.py”, line 611, in async_render_to_info
render_info._result = self.async_render( # noqa: SLF001
~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
variables, strict=strict, log_fn=log_fn, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File “/usr/src/homeassistant/homeassistant/helpers/template/init.py”, line 496, in async_render
raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: TypeError: ‘NoneType’ object is not iterable
2025-10-21 12:22:06.753 ERROR (MainThread) [custom_components.frigate.api] Error fetching information from http://ccab4aaf-frigate:5000/api/stats: Cannot connect to host ccab4aaf-frigate:5000 ssl:False [Timeout while contacting DNS servers]

10

Hey, any chance you can format the logs by clicking the gear icon in your post and selecting the “performantes text” option?

At first glance I see a bunch of notifications that there is a DNS issue, that is normal since you unplugged it.

11

Common issues are IP conflicts, so check if the device is still reply to pings when it is disconnected.
Another common cause is hickups in the router, so try to restart that too.

12

I figured it all out - after building a VM, restoring to that, and while trying to get my zigbee POE network controller device added (it had issues), I got another failure on that system!

Then I assumed it may be related to the network, as there was a unifi switch and network controller update early today, and these HA servers are on my IOT vlan, so restarted those network devices, and the server (original one) - I thought that had fixed up - but about 25 minutes or so later, another crash!

So when it started next (It was restarting itself each time, but I never gave it long enough), I set all addons to not start before it had a chance to fail again, and then I methodically worked through them - FRIGATE was the issue - googled that and sure enough a few people reported the same thing. That is stopped now - and no issues for over an hour!

I have left my CCTV down for now, as its going to be dark soon and the lights will be needed.

This all brings to the forefront of a need for a semi HA (higher availability) solution as your system grows and grows and takes over your life. I will work on that Unraid VM in my spare time (only the zigbee controller was the issue
) and look at some way of keeping it updated - or at least the backups being automatically sent to its machine.

13

I’m just curious - what’s good about unraid when it comes to high availability? Also how do you plan to handle the zigbee PoE controller when you move to high availability?

14

That is a very good question. So far I’ve been using ha to play with smart lights and smart plugs to turn the “dumb” lights on and off. But I also want to automate my driveway gate and thinking about a smart lock (no way I’d settle for one without a proper keyhole as well). There have been times when ha soft bricked and i had to turn it off and back on. If I were to rely on it to control what I would consider to be “mission critical systems”, I’d want a redundant ha instance running somewhere else in the house (with its own dongles). Heck, I want one anyway lol.

It’s annoying enough when you have to restart ha to turn the lights from hot pink to a normal 2700K (or 6700K if you’re a psycho). Imagine not being able to open a gate.

Asking before I google, but is a redundant ha instance possible?

15

That depends on your choice of technologies.
F.ex. Zigbee allows only one coordinator device in the mesh network.
You can use a network Zigbee coordinator then, to move the coordinator off the HA box and maybe allow multiple network connections to it, but that network coordinator will still be a single point of failure option.
I am not certain how Z-Wave work.
WiFi can have those single point of failures too, like if you only have one AP covering the area or if WiFi requires a WiFi controller to run and that then makes the single point of failure option.

Matter over thread with multiple Thread Border Routers (TBRs) will option to move the single point of failure all the way out to the lock device, but Matter over Thread is still a bit immature, so adding multiple TBRs to a mesh is not always without problems, especially if they are from different vendors.

16

Gotcha. I stopped buying zigbee products and started going exclusively with matter over thread (don’t want any unneeded wifi devices unless there really is no other alternative). Was just waiting for the ha Matter integration to come out of beta before I hopped on the bandwagon, really. And yes, it’s still crappy as heck as an ecosystem but hopefully it’s fixable in software. I mean matter over thread was supposed to be “the” thing. I don’t really see a matter v2 happening if this flops lol.

If I do get another border router it’s likely to be another ha/otbr (want a separate dashboard for my mom and dad where they would only be able to see and control say, garden entities and not have access/don’t even see the devices in my apartment). Not sure if I can accomplish that with a single ha instance, but I’m not at that point yet anyway.

That said, redundancy and high availability should be at the top of the priorities list, imho.

17

You could. You can setup different users, and then you can setup the dashboard in a way that different users would see different things. You do not actually need to have 2 HA servers for this purpose.

I am curious - what is the metal box (make/model/spec) that you run your HA / Frigate on? I’m asking because I cannot recall ever seeing my HA stopped responding.

18

Perfect, ty. I did read into it a little while ago (on reddit I think) and it seemed like that could be the case, but it’s good to hear it actually can be done. It’s a family house, we each have our own floor and separate front doors but share the garden and the yard so this sounds perfect (I’d rather have one network for the entire house but different dashboards for different users).

As for the metal box, I’m hardly the one to speak as I’m doing everything wrong, but it’s been running on a Pi 3B+ the past two years, and over WiFi at that. Not using frigate, only been using diyHue and zha (I’ve only had four zigbee bulbs for the past two years, was waiting for Matter to come out of beta so I just expanded to some more thread devices this past month (with more on the way :D). And I also had Piper and Whisper installed (3B+ was woefully inadequate but I did manage to get the voice assist to charge the color of the lights lol. Then it would just stop processing speech with the voice assistant would give a little text error message). I also started getting Wyoming protocol failed to start up yadda yadda but I didn’t pay it much attention at the time (since I wasn’t actively using voice assist anyway). Started getting out of memory errors once I installed matter and otbr so I disabled everything but zha and matter for the time being and I’m upgrading to a Pi5 either tomorrow or sometime next week (as soon as it reaches the store :D, been told that ha needs at least 2GBs of ram to run properly and I suppose I really am overdue for an upgrade). That said, I’m already thinking about a proper metal box, especially after reading into this month’s blog post about all the voice assist updates they’ve done (just wanted a Pi5 :D).

Thing is, I was able to use the companion app even while the out of memory errors were happening after the matter/otbr addition just fine (matter just couldn’t/wouldn’t properly start or would fail after a while).

But there have been several instances where I was unable to use the companion app to connect to ha (I can’t for the life of me remember the exact errors now, but something in the lines of address unreachable or some such and a restart would fix it). I even hooked it up to my tv with HDMI to check for errors but all I would ever see was a screen full of hci0: Bluetooth frame reassembly errors that I have been getting since day 1 and they’ve only seemingly gotten worse as time went by. Hoping the Pi5 fixes that as well.

19

Pi3 indeed would be the reason why your HA keeps going offline.

For the $$ of a Pi5, and if it’s not too late, please consider a x64 Mini PC or thin client or used laptop, etc. It would give you (a lot) more headroom to run, and you might not need to consider high available any more. Search this forum for similar topics.

Also I recall there was a thread to talk about HAHA (home assistant high availability) - don’t know the status or development of that thread but something for you to consider.

20

I will probably upgrade to a Mini PC again in the near future. It’s just that I’ve been wanting a 16gig Pi for novelty’s sake since Jeff dropped the rumor on launch day. This was the perfect excuse to get one (and a stepping stone to at least a mini PC, I’m also considering something a lot more powerful for local LLM/Voice Assist). But yeah, I will probably upgrade again to a MiniPC in the near future and use the 5 for whatever else in the meantime (Edit: although I’ve read reports from ppl running ha on a pi5 for two years without so much as a hiccup so who knows).

I’ll look into HAHA when I get the chance too, thanks :slight_smile: