I am able to access the system. Just don’t like it that it is taking the vlan IP. There must be a way to set the default network adaptor. I can see the settings, just could not find a way to update it. 
Would be happy if anyone knows how to do it.
Thanks.
Same here. In the browser on the 'normal pages it’s a bit intermitted. Sometimes it work ok, sometimes not. ctrl+f5 makes it work for while. In the ‘entity pop-ups’ it’s consistently not looking good. Yesterday I reverted to 2021.5.5 an’d everything looked fine. After updating to 2021.6.0 it was malfunctioning again. Today I fiddled around with the themes a bit, but that made not difference so far. I did also check my database, because I had some issues with corrupted databases in the past, but the database was OK. I also removed 2 custom cards from the front-end, but that also had no effect. I’m bit lost on this for now, so any help is appreciated.
Yes, refreshing the page does the trick (most of the times, sometimes it is required to make it 2~3 times), but this is not the point… Until ~2011.6 it worked perfectly without refrehing…
Has anyone written up an issue with detailed logs? Or is everyone just reporting here expecting someone else to do it?
Problem is that there is nothing in the log… After each restart and encountering this issue I review the logs, but there is nothing there that could even remotely point to source of issue. As far as I managed to learn how to read HA logs, I see all the warnings or errors being related to components I can identify (mostly network connection issues or timeouts for these). So no good starting point to troubleshoot
The lines are still there, but the entity is gone.
You should show what your logs are telling you.
I upgraded to the lates version of hassio, os and supervisor. Restarted the host and my hassio doesn’t boot at all. My hassio is on a raspberry pi 3b+ and hassio is on ssd without an sd card.
I reinstalled everything again from the latest image version, restored snapshot, restarted host and same issue
Just reinstalled again. Restarted host and it doesn’t boot if I restart host.
Core-2021.6.6
Supervisor-2021.06.06
host 6.1
Unplugged it and plugged it in again and it does boot what was not the case when I had my snapshot restored.
There is no hassio so your post makes sense.
What errors are in the logs?
no errors in the logs
with the last test is was just the image of the install without any addons or configuration
Sure you have the correct ip or hostname & domain?
Well, as @mirekmal already pointed out, there seems to be no relevant lines at all in the logs. I just set the default log level to debug and rebooted. Witin a few minutes the log file was 8MB and contained >3000 lines. I scanned through and the only possibly related lines I could find were:
2021-06-26 08:29:30 DEBUG (SyncWorker_2) [homeassistant.util.json] JSON file not found: /config/.storage/frontend_theme
2021-06-26 08:35:24 DEBUG (SyncWorker_3) [homeassistant.components.recorder.util] querying 607 rows took 0.076864s
2021-06-26 08:35:24 DEBUG (SyncWorker_3) [homeassistant.components.recorder.history] get_significant_states took 0.078310s
2021-06-26 08:35:24 DEBUG (SyncWorker_3) [homeassistant.components.recorder.util] querying 1 rows took 0.004000s
2021-06-26 08:35:24 DEBUG (SyncWorker_3) [homeassistant.components.recorder.history] getting 1 first datapoints took 0.004676s
2021-06-26 08:35:24 DEBUG (SyncWorker_3) [homeassistant.components.recorder.pool.RecorderPool] Connection <sqlite3.Connection object at 0x67a27350> being returned to pool
2021-06-26 08:35:24 DEBUG (SyncWorker_3) [homeassistant.components.recorder.pool.RecorderPool] Connection <sqlite3.Connection object at 0x67a27350> rollback-on-return
2021-06-26 08:35:24 DEBUG (SyncWorker_3) [homeassistant.components.recorder.pool.RecorderPool] Closing connection <sqlite3.Connection object at 0x67a27350>
2021-06-26 08:35:24 DEBUG (SyncWorker_3) [homeassistant.components.history] Extracted 608 states in 0.109773s
2021-06-26 08:35:24 DEBUG (MainThread) [homeassistant.components.http.auth] Authenticated 192.168.178.1 for /api/history/period/2021-06-25T06:35:24.135Z using bearer token
2021-06-26 08:35:24 DEBUG (MainThread) [homeassistant.components.http.view] Serving /api/history/period/2021-06-25T06:35:24.135Z to 192.168.178.1 (auth: True)
As a layman, I do not see an obvious error here.
I was expecting/hoping that we as users together could figure out the cause and solve it without bothering the developers with it. I guess that is (partially) what this community is about. I’m obviously not the only one with this issue. By now it seems that finding a solution ourselves is not working out. So, I guess @mirekmal and I can create a concise and to the point issue.
For now I set up my logger like this trying to catch usefull messages:
logger:
default: warning
logs:
homeassistant.components.history: debug
homeassistant.components.recorder: debug
homeassistant.components.http: debug
Any tips what other components to take along?
Does the .storage/frontend_theme JSON file exist? Good troubleshooting tries to resolve the first error found. Many times other ones are also resolved.
I tried to do the same and enabled debug level of logging…
Well, after first few minutes after restart my log was 200,000+ messages, being added faster than I can review them. I tried to look for some key words, but whatever I choose it was repeating thousands of times in the log, so very little use. I gave up.
There should be better way to track this issue down, perhaps someone has some suggestions how to configure recorder to recorder only potentially relevant information (e.g. to force to record data from history graph card only, or from history panel)?
[supervisor.docker.interface] Can’t install ghcr.io/home-assistant/raspberrypi3-homeassistant:2021.6.6: 404 Client Error for http+docker://localhost/v1.41/images/ghcr.io/home-assistant/raspberrypi3-homeassistant:2021.6.6/json: Not Found (“no such image: ghcr.io/home-assistant/raspberrypi3-homeassistant:2021.6.6: No such image: ghcr.io/home-assistant/raspberrypi3-homeassistant:2021.6.6”)
404 generally indicates the disk is full
404 from git source means, that image for RPI3 are not present… from mine POV
