Closed emme1444 closed 3 years ago
Yes, the Supervisor monitors the API port. But some HTTP config on Home Assistant is not compatible and if you use them, it makes that the Supervisor can't work with Home Assistant. I.e. don't assign Home Assistant to a Network interface or if you do that, make sure it is listening on the Supervisor virtual Network too.
EDIT. It has also issues on the landing page, so it is something on your system which protects us to check the port on the home assistant. I hope this info helps you to find the problem.
Yes, the Supervisor monitors the API port. But some HTTP config on Home Assistant is not compatible and if you use them, it makes that the Supervisor can't work with Home Assistant. I.e. don't assign Home Assistant to a Network interface or if you do that, make sure it is listening on the Supervisor virtual Network too.
What exactly do you mean with not assigning Home Assistant to an interface? Do you mean the container? The supervisor starts the Home Assistant container automatically? I have, to that container, not done anything.
EDIT. It has also issues on the landing page, so it is something on your system which protects us to check the port on the home assistant. I hope this info helps you to find the problem.
Do you have any idea of what this could be. Could this have something to do with the fact that I'm running this on a Raspberry Pi? Like, dhcpcd
?
I will try with reflashing the operating system. I have a feeling that might fix it, and hope so. Thanks anyway for the reply!
Home Assistant release with the issue:
Operating environment (HassOS/Generic):
Supervisor logs:
# docker logs hassio_supervisor
Description of problem: Really there are 2 problems, although they go hand in hand. The first one, which can be seen in the
hassio_supervisor
logs, is that the supervisor is reporting not being able to starthomeassistant
. However, there seems to be nothing wrong, for what I can tell but I'm not an expert, with thehomeassistant
container. (logs for this can be found down below)I originally discovered this because I was trying to access the
homeassistant
instance via a browser, but constantly got a timed out response. Which I guess meanshomeassistant
is there but not responding?The logs report using different timezones:
hassio_supervisor
: UTChomeassistant
: UTC+2i live in Sweden, so UTC+2 is the correct one if anyone cares.
Any pointers are appreciated. Extra logs can be found down below.
Thanks in advance!
Logs I used the
homeassistant/supervised_install
install script. Here is the log from the scripts:# curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s -- -m raspberrypi4 -d "/home/pi/homeassistant/config"
Here are the logs from the
homeassistant
container:# docker logs homeassistant