Hi, After updating one of my Pi’s to HA 106.1 I had trouble using Duckdns, so reinstalled that, unfortunately couldn’t reach the instance through the duckdns address still. So, thought Id restart the instance completely.
Which I shouldn’t have done: I can see the log in the smb (which apparently still works) but it wont go past:
2020-02-21 14:50:53 INFO (MainThread) [homeassistant.setup] Setting up hassio
2020-02-21 14:50:53 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 2.2 seconds.
2020-02-21 14:50:53 INFO (MainThread) [homeassistant.setup] Setup of domain hassio took 0.1 seconds.
2020-02-21 14:50:53 INFO (MainThread) [homeassistant.setup] Setting up logbook
2020-02-21 14:50:53 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.0 seconds.
2020-02-21 14:50:54 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2020-02-21 14:50:54 INFO (MainThread) [homeassistant.core] Timer:starting
managed to do so, but no idea what I should be looking for. I can see things are happening, so the Pi is still working, only no frontend…
ony 3 errors in the log:
well, that’s a possibility, but then we wont be able to find anything no use debugging the components that work fine is there? If we must, we must, but if we can narrow it down a bit, that would be nicer.
The frontend isn’t loading so we need to figure out what’s broken
Maybe even a docker logs -f <container ID> would be useful in case pip is installing somethings.
Tinkerer
(aka DubhAd on GitHub)
Split this topic
9
well, the oddest thing:
For my 3 HA instances I have shortcuts on my iPhone. Loading the this instance went without hiccups at all… While the Safari Mac refused to load it completely.
Firing up Firefox on the Mac showed the HA instance immediately. Of course I had tried to clear and reload cache in Safari, but that didn’t help.
I then closed Safari completely, restarted with an empty page, again cleared and refreshed cache (Developer menu, empty cache) after which I could load my HA instance again!
So, it was a Safari Mac issue, not a HA 106.x beta issue.
thanks for helping and thinking along!