So I need to debug what is causing this to happen. It seems to be related to whenever the power goes and comes back (although Im not entirely sure).
Ive got hassio on rpi running my ha and it all works gr8. Every now and then though, when I load my UI I get a connection refused which turns out in no ping and no listing on the router dhcp client list. The rpi already has a reserved mac-ip address configuration set on my router. But something seems to be causing issues every now and then when i just loose the rpi from the network.
The rpi is ethernet connected to the router. Other devices wirelessly connected to the router continue working just fine so I dont think its a router issue, unless the pi is doing something that the router doesnt like at some point.
How do I fix this?
Which version HA, supervisor are you on? Can you ping your RPI when this happens. I’m running a NUC but I had a strange issue where all docker containers just were killed over time. Couldn’t track it, but since I updated to the latest HA and supervisor I haven’t had this issue.
These are my settings:
System Health
|arch|armv7l|
| --- | --- |
|chassis|embedded|
|dev|false|
|docker|true|
|hassio|true|
|host_os|HassOS 3.12|
|installation_type|Home Assistant|
|os_name|Linux|
|os_version|4.19.106-v7|
|python_version|3.7.7|
|supervisor|227|
|timezone|America/Tegucigalpa|
|version|0.110.4|
|virtualenv|false|
I’ve updated python also to 3.8 because I heard 3.7 was a bunch of trouble. But in your case that is something you can’t do. Maybe someone else knows a solution.
I don’t think you can upgrade python, because it’s part of the HA OS that was installed through hass.io. But I’m no expert on that. I run Ubuntu.