Is there something else on your network that does something about that time?
Just before your crash it looks like homeassistant suddenly loses a network connection and can’t update various things, I’m just wondering if you are having your local network flooded by something else and it’s ddos-ing homeassistant at the same time?
It could be DHCP leases going haywire when renewing.
So my first and second power supply were bad. These little guys are so finicky when it comes to power.
Looks to be stable after just building one with good components.
So It looks like the power supply wasn’t the issue. I’m still getting freezes. I swear it’s almost exaclty 24 hours from when I unplugged it. Does this happen to anyone else? I’m using Gargoyle Firmware on a TP-Link c7 Archer.
Kinda making me a little crazy. Haha. Is there a way to send some kind of log to a remote location or a way to monitor sources up until the freeze. I can’t ssh or anything. Lights are on, but no one is home.
So I think I figured it out. I don’t know if this is a bug or what, but I think it has to do with lease time set on a router.
Mine was set to 12 hours by default. I upped it to 48 hours and have made it past 24 hours for the first time.
Does that sound like a software issue? None of my other devices freeze
Set your Pi to a static IP via your router. If I recall they fixed the dhclient in the latest version of Raspbian.
I am suffering for similar problem, in the past couple of days my HA service stopped (only the HA service) every 12 hours in same intervals (12:00-13:00 & 00:00-01:00)
The log file is deleted because HA is reset, so i can’t look for any information about the problem, i have tried to search for something in the history tab but i only see the HA stop and start after 3 minutes.
I think it related to the new update, it happen after update from 0.81 to 0.81.6
I went around and around and around fixing problems. New sd card. A really expensive power supply setup for a rasp pi. Haha
The only thing that worked was the lease change in my router settings. Are yours set to 12hrs?
It’s been rock solid for the last 2 days. I’ll report in the next few if someone wants me to, but I’m hoping this was the resolution. It was maki g me crazy.
I had pi hole for 8 months prior to getting into home automation and the thing ran for the entire 8 months. So i know it’s not the hardware.
Oh and I use static’s for all of my devices in my house.
I use 1440 min lease times, my Xbox One would start acting up like a Pi without a longer lease time too.
Ah ha!! Well then. Maybe that was my issue. I think I was having problems with my fire TVs as well. Hopefully this solves it all.
I’ve now set mi e to 48 hours. But my router reboots daily.
Most routers normally don’t change your dynamic IP’s on reboot. On the other hand, why is your router rebooting?
i don’t have this option in my router (Google Wifi)
maybe i will downgrade to 0.81 and see if it is a HA problem
Just don’t do DHCP. Give it a static IP setup.
it is a static IP from the beginning
Then why the hell do you suspect DHCP?
I just have a reboot everyday to freshen it. I guess to avoid having to do it manually.
When I just had it up all the time every now and then it would mess up. I have my 24 hr pc reboot as well. Just to get a fresh start I guess.
All my devices have been rock solid. I don’t remember the last time I had to do the inevitable unplug the router gig. Haha
You shouldn’t do that. Routers are built to run uninterruptedly. Rebooting it will interrupt all communication. That’s really REALLY bad for Home Assistant. If a single or few devices go offline it’s acceptable. But if everything goes down it’s no wonder your setup is unstable.
it think i have found the reason for this problem, i have found that the SSL Renewal is making this , i have a automation to new the ssl cert when it is under 29 days left , so this make sense because it start happened couple days ago ,
the problem with the SSL Renewal was that the shell_command was incorrect after they change the option to use the “tls-sni-01” commend , the solution was to use “~/certbot/certbot-auto renew --no-self-upgrade --standalone --preferred-challenges http-01”
i am 90% sure that this was the problem , i will update later
I had the exact same issue. My script to renew my SSL was failing, and as a result, Home Assistant would not boot up as the script would fail/error and just stop. It took me a while to work it out, but I figured it out. Now I have to wait another 77 days to see if I’ve fixed the issue. On a side not, I may not have to stop HA to renew my SSL anymore with this new method.