Home assistant on a Rasberry PI, running in a docker

Configuration
1

Hi guys.
I noticed that since about a month ago my Node red integration has stopped loading. I checked HA configuration before I rebooted it yesterday, Node red was still not working. And then today I did a full Rasberry PI reboot, now Home assistant goes into “The site cannot be reached” error message.
Do you know what the heck could have happened?
I didn’t do any configurational changes since months now.
What can I do, please?
Thanks

PS: I just checked the command output “docker events” and I see when it tries to start the container, it eventually dies.

2

Connect your OS and check sudo ha core info and sudo ha core logs

First command will tell you status of core, maybe it is working but SSL or reverse proxy is broken.

Second command will show you the logs of running core. You can also access it directly in home_assistant.log file

3

The container is not running, as I presumed:

image
image2856×180 23.3 KB

The last lines of home-assistant.log are about the Vailant integration:

image
image3141×497 44.9 KB

Interesting fact is, I am not aware of any auto-update feature, I can reach the Vailant IP module through its own app, and it’s working. I have no clue what has broken this.
Any pointers how could I disable the Vailant integration? Just zip the content of the dir on the customer integrations dir? I didn’t find anything related to Vaillant in the home assistant configuration.yaml file.
Thanks.

4

Vaillant integration might be a problem but (under normal circumstances) should not break your HA (or stop docker).

Why don’t you try sudo ha core start

5

The above command exection failed by saying the container is not running.
“Error response from daemon: Container 99880ac1aba1a43b37bccfe2681726085a0d2a47f847d95fc236cb7b8a0705f5 is not running”

PS: I just did “docker start homeassistant” and now it’s back online.
It has some errors though:

image
image1441×673 34.5 KB

image
image2988×1343 300 KB

But the configuration seems to be fine:

image
image2074×1180 93.5 KB

I really don’t understand what the problem is?
Thanks

6

I restarted the linux again. Docker container won’t start by itself. If I start it up like above, many things don’t work. Ex. I cannot get Server health, Observer is running, Supervisor is not reachable. :frowning:

7

You can check systemd, there are many tasks (supervisor and hassio) to be started at startup, maybe they are disabled or removed by mistake