What is your network setup? Looks like you have at least three VLANs (or two, with very large subnets).
192.168.178
172.30
172.17
When things go offline, I always suspect network issues: duplicate IP address allocation, bad routing etc.
What is your network setup? Looks like you have at least three VLANs (or two, with very large subnets).
192.168.178
172.30
172.17
When things go offline, I always suspect network issues: duplicate IP address allocation, bad routing etc.
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
@Plevuus, Indeed, mine crashed again last night too. Itās behavior is at least predictable.
@DomJo, Did you have any new insights?
@captain_daveman, any similarity in your setup compared to mine or Plevuus?
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
homeassistant stop again, it works but it is not accessible in supervisor all addons stop working, hacs not accessible but addons frontend working
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:
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.
I already opened an issue HA stops work every Monday Ā· Issue #47928 Ā· home-assistant/core (github.com)
What installation of HASS do you have?
(OS, Core, Docker etc)
What type of installation are you running?
Home Assistant OS
Then I canāt help youā¦ Sorry, my thoughts were that something with crontab could be wrong
@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.
Is there a way where i can simulate sunday 00:00ā¦ Change the clock and day
Not using hassOS.
If HA is still running but the frontend is accessable, why donāt you just create an automation that reboots or restarts the systemā¦
- alias: Reboot Once A Week at 2am
trigger:
- platform: time
at: '2:00:00'
condition:
- condition: time
weekday:
- mon
action:
- service: notify.xyz
data:
message: "Rebooting..."
- service: hassio.host_reboot
Sorry to step in here, @petro, but that is just a band aid, not a solution.
If people here are interested in solving the problem, I refer to my previous post. We need to debug this, but as I can see, interest seems not overwhelming, as we now have eight replies and not one question is answeredā¦