yea amazon does its own thing there and unfortunately updating webview is not an option there, you have to wait for amazon to push that update.
Does the WebView version I’m running yield any clues? As added context, it’s a fully up-to-date Pixel so it should both be as vanilla and as current as anything Android can be.
the only times ive seen issues with webview is when its outdated, I have not seen issues when its up to date. Personally I would start by disabling custom cards one by one to see if one is the culprit. You should also check open issues with each custom card as well in case someone already reported it.
In terms of investigating on your own you can try using Chrome Remote Debugging to see if it gives any clues
Same problem here
So I’ve found a few other tidbits.
1. I left one of my smallest dashboards with only 2 standard cards ‘open’ in the background. I got the same error but it recovered almost immediately.
2. I left one of my larger dashboards ‘open’ and got the same error, but purposefully let it sit for a while. Took maybe 30+ seconds but it also recovered eventually (guess I wasn’t ever patient enough before).
Edit: Seems I spoke too soon. Tried to recreate it all a few more times and everytime it acted a little different. Recovered a time or two, but not always and the size of the dashboard didn’t seem to have an impact.
@dshokouhi Do you think the potential problem custom card would need to be on the last viewed dashboard to cause the issue? That was the purpose of my initial test, as I’ve got quite a few custom cards installed and REALLY don’t want to have to try disabling them one-by-one…
custom cards actually get loaded in the browser as soon as you load the HA frontend IIRC they dont even have to be in use in any dashboard as long as they are added as a resource the code will load. In the past we had seen an issue where just loading card-mod would interfere with the apps more-info pop-up code.
alternatively you could always list your custom cards to see if others who have this issue may show the same custom cards. But I think if you just started the process of elimination since you can reproduce it quite easily it wont take as long, unless you had a hundred or some odd cards.
There’s a GitHub issue that’s been raised. Probably more likely to get attention from the developers than this forum, so I’d recommend posting there as well if you have the issue.
2 Likes
Thanks for the info/background.
Finally had some time to sit down and make a proper list of all my custom cards, etc. Going to follow your advice and remove them one at a time and wait for the error to pop up again (as a side-benefit, I think I have several installed that I don’t currently use, so I guess I can do some housekeeping while I’m at it too).
Plan is to remove each card one at a time and restart HA each time (but not the host machine). I assume this is the correct procedure to fully flush them from the system?
actually now that you found the frontend bug that matches your screenshot…check the comments to see if you see the same logs/experiences others do. Might be something else entirely different than my original assumption.
Unfortunately it’s the same general info as mentioned in this forum (i.e. nothing). Nothing to really go on; some folks seem to have something in their HA log and other don’t (such as myself).
Went through each of my custom cards and verified none of them are the cause. Hopefully something comes of the GitHub issue raised.
As I note in github, personally I have been able to significantly reduce the number of times I’m seeing the error on my mobile & tablet by reducing the number of events happening on my network to below 100 per minute. So until the root cause is fixed, for the short term I’m suggesting going into developer tools/events, subscribe to “*” and see how many events are happening in your network on average every minute. If there is something chattering away that’s not required, try stopping that and seeing if it helps at all. It might not help, but it’s worth a try.
Unfortunately this isn’t really doable for me. I have WELL over that many events under normal conditions, on the order of a couple thousand a minute.
1 Like
Yowza. Ah well, fingers crossed something comes from the GitHub issue.
Having this also since the update to 2023.6 and only on Android, whenever i try to access on the iphone i see no issues (but i am not using the iphone on a regular basis).
Poco F1 - Android 13
My wife has the Poco x3 and doesn’t seem to have the issue, at least she didn’t tell me.
I found I had the issue on android, iphone and ipad - significantly reduced now I’ve been able to reduce the number of events being broadcast on the network but still not great. If you close the app after using it then you’ll never see the problem. If you leave it running in the background and/or your device goes to sleep then you will most likely see it when you try to go back to the app.
1 Like
The same here.
The problem happens every time I use the app, no matter if I’m accessing internal or external.
If I use chrome (android) this doesn’t happen.
This is happening to me post adding motion sensor data to my dashboard. These are esp32 based mmwave presence sensors which probably are generating too many data points or logs for the UI to get refreshed and handle the load.
Same problem here. It started when I updated to HA 2026.6.0. I’m sure it’s not the app as the app got updated 2 days later. I changed nothing in my network config. It must be the HA Core then. This is extremly frustrating!
And the same workaround works for me - close the app and relaunch.
This happens after at least 5 minutes of having the app running in background. After 5 minutes the app kills the background connection and when you open the app again - it tries to reconnect and we all see this ‘Reload UI’ button.
I will post an issue in Guthub and will give the link here, so you could add your comments and bring the devs’ attention.
All, there seems to be a potential solution to this issue assuming the root cause was identified correctly.
This is described in 2023.6 Home Assistant UI reload Icon appearing · Issue #16854 · home-assistant/frontend · GitHub. There are several duplicates of this issue in Github, but this one seems the most relevant and some fixes were applied to HA Core beta channel to address this.
If you guys are comfortable with switching to the beta channel and installing the latest beta 2023.7 then let’s get this tested this way. If you do install the beta - please post your comments in this Github issue with your results.
1 Like