Another HA having this issue here. Last night it happened again, only a hard restart brings it back to life again.
So, My hardware consists of a raspberry PI 3B (V1.2), a zzh (CC2652R Stick) zigbee stick and a 32 GB Micro SD card.
Integrations:
Agent DVR, 2x FRITZ!Box (router), HACS, Meteorologisk Institutt, Mobile App, MQTT mosquitto broker, Philips HUE, Raspberry pi power supply checker, IKEA, TUYA
Hacs integrations:
Afvalwijzer (waste scheduling), SONOFF LAN, Fritz!box tools, Yahoo finance.
Add-ons:
Check HA config, DuckDNS, file editor, mosquitto broker, Samba share, terminal @SSH, Wireguard, zigbee2MQTT.
So again one with the waste scheduling but that might be a coincidence.
It is excessive, but as far as I can see from the documentation it cannot be turned down. It’s local push and only the entity updates can be slowed down. (when I set it up that option was not yet available I believe and had to exclude the readings from the recorder and only include filtered entities to avoid flooding the database)
On the other hand, I do not think that this is causing the crashes, since I’ve been using for about a year without any problems.
192.168.178 is my home network indeed. I’m not having any VLANs (AFAIK) and to be honest I do not even know what that exactly are, nor do I exactly know what subnets are. It seems to me that the 172. addresses are some kind home assistant internal addresses. I’m quite sure I have no duplicate IP address allocations.
Last Monday and Tuesday were really bad. Home assistant crashed after 1 or 2 hours of operation every time. Tuesday evening I did a fresh re-install on a brand new SD card and restored my snapshot of Sunday evening. Within one hour it crashed again, but after a restart is has been running stable so far. I’m curious what will happen Monday morning.
It crashed again last night @Harmpert, Thanks for your list of hardware, integrations and add-ons. The Items you have and I also have are: raspberry PI 3B, HACS, Mobile App(both android and iOS in my case), Philips HUE, DuckDNS, file editor, Samba share, terminal & SSH
Another Monday crash for me too, this time slightly earlier than usual. The last log/history entries I can see are for 00:10 (usually it’s more like 01:30).
In terms of what I’ve got installed in common with Plevuus above, it’s a Pi 3B, HACS, Mobile App, file editor, Samba and SSH.
For my network, I have an Asus modem/router (I mention this as the issues started happening at about the same time I bought it.) I’ve not setup up any VLANs or special subnets (just using standard 255.255.255.0)
I struggle to believe that any of the above are causing the issue otherwise there’s be a lot more people complaining!
Just crashed again too - probably something corrupted due to having to pull the plug this morning.
I’ve changed the system in the meantime and now use OH3. For me, home automation has to run reliably and not stop every week. But I still read with interest because I think HA is very nice
Yep, Mine also crashed again last night. There was no useful info from the log. This time HA frontend was still available and even the history graphs were showing (latest update 2:38 am). Supervisor page was not working and also SSL and Samba were down.
Last week I did some improvements in the network setup (port forwarding, removal of depreciated base_url from configuration.yaml), switched for the general setup (location, time-zone, URL, etc) from configuration.yaml to UI and made some other improvements in configuration.yaml, so that no configuration related warnings showed up in the log anymore. It didn’t solve the issue.
@Plevuus@nelsonamen ,mine crashed last night too, last update around 1:52 AM.
@tom_l, would you have any suggestions on this? Might there be an addon/integration that is doing someting for the week startup/cleanup of the last week?
We can rule out the automations, I don’t have one running at that time,
We do not have the same routers (mine is a fritz!box 7590).
@tom_l, question to you as a moderator. Would it make sense to officially report this issue?
Multiple users have this issue and it seems we’ve done what we can do ourselves. At least I did.
The only option I see left for myself is to start again from scratch with a new installation and slowly week by week build up my system again and notice when the issue re-occurs. By doing it like that it will take weeks and quite likely it will not re-occur at all. In that case the other users will still be stuck with this issue.
@Plevuus
I don’t think, an issue would do good at this time. Your (all of you) error isn’t specific enough, nor described enough.
Let’s try it in a different way, good old support and error finding. If we cn pinpoint the issue, that would be the time to post an issue at github.
So let’s get to work and find something.
These are questions to all of you, who have that problem:
what system are you running? (HassOS, python venv, supervised install) In short, how did you install HA?
what is the exact hardware you are running? Pi4 with 2GB? Pi 3B+? Please don’t forget to mention all things apart from the standard, eg. are you using an SSD or the microSD?
if you’re running a Pi, what power source are you using? We need the values here like Volt and Ampere from the power source.
are there any outside things that could cause this? Maybe the cat laying on your Pi every Monday?
Can someone provide a somewhat exact timeline of the issue? What I can see here, it seems not always to be the exact same time, but the better one of you could tell, when this happens, the easier we can find something.
Router could be an issue, so please provide the model. I personally don’t think it is, so this not a necessary information.
Just to note: I’m not a developer of HA, I can’t guarantee any solutions, but I’ll try my best, maybe someone steps in if we can narrow things down. So no guarantees!
And last but not least, my guess goes straight to some OS level things that are done automatically. Monday morning is kind of a good date for any tasks you would like to run on a weekly basis.
So let’s see where we are getting at with this, seems interesting to find out.
@tom_l is on a boat somewhere in the ocean atm and won’t be back for a few months. As for that issue, it’s lacking any information, the likely hood of anything comming out of that is low. Please follow through with @paddy0174’s questions and use that information in the issue.
If we cn pinpoint the issue, that would be the time to post an issue at github. 
