So make the small ammount of confusiion for companion app users only. And not confuse everyone instead.
I will add one key, but missing, bit of info on clearing the frontend cache: Ensure that the frontend has the item-to-be-cleared-from-the-frontend-cache loaded. If not, and instead you have your frontend cache new tab defaults loaded or something akin to https://duckduckgo.com loaded rather than a frontend entity containing your item of interest loaded, the item you want to clear from cache will not be cleared from cache. If you are in a hurry, with your F12 tools visible, CTRL+F5 should get it done. Also with F12 tools open, right-clicking your frontend app rendererās reload button can, for some renderers of frontend apps, also bring up a context-menu with a āclear cache & reloadā option. ![]()
EDIT: This is old information from an old hu-man. Things might have changed since these options last worked for me.
This is the way. Even with the lack of a dedicated shortcut to do this, itās the only option I trust to fully clear the cache.
25+ years of using computers, is it too late to ask what is a ācacheā? ![]()
25+ years around computers one way or another. Yeah, after educating myself about āfrontend cacheā, I just had to sign the guestbook. ![]()
Thanks for this - Iām currently experiencing the "āerror while loading page ā¦ā message in the Android companion app and found my way here.
Only issue is I canāt get to the Troubleshooting page - I get the error when I try to get the the settings page.
The change to clear cache is not live yet, it has been implemented but not released. But you need to access that page to enable WebView debugging. Did you try to clear the App cache from the App Info?
Ahh. Didnāt notice that itās only just been merged.
TBH, I hadnāt tried clearing app cache due to the number of comments Iāve seen saying it didnāt work (survivor bias?). So Iām going to contribute against that and advise that clearing the app cache probably did fix the issue for me - so even though thereās plenty of people saying it didnāt work, try it anyway!
My issue actually cropped up when I rolled back the 2025.3 update (due to the loss of the Roborock Map card) by going back to 2025.2. I was planning on waiting for 2025.4 but this error was becoming a headache so today I updated Core back to 2025.3. Not 100% sure if I tried the updated Core before I cleared the app cache, so the fix could have been one, the other or both. I suspect it was clearing the app cache, but.
It is always good to try all the options. Clearing the App cache can fix several issues, but most of the time it doesnāt solve issues related to front-end code because it is stored in the WebView cache which is not deleted with the former.
But glad to hear that you have solved it.
All jokes aside, web servers typically cache frontend content. Any frontend cache for HA is part of HAās web server, meaning HA users search all the settings for a clicker labeled as āclear frontend cacheā
Client cache is the wording I would use for the cache in apps and web browsers, as apps and web browsers are both āclients.ā
So, I read the I need to update the rpiboot on my HA Yellow CM5 which cannot boot from USB anymore once HA is installed and also lacks an SD card slot and also lacks any HDMI or even VGA slot.
So I cleared my browser cache. Update to HAOS 15.1 finally complete!
J/K⦠i wishā¦
15+ years in OT application support, another dozen years before that on SCADA systems integration.
Came to sign the guest-book on wtf is a āfrontend cacheā and how do I clear it?
![]()
`I do want to say āthank youā to the person who wrote instructions using the words āfrontend cacheā rather than client cache for the client cache. It is how I find this message board now for any/all HA related issues.
My bonnet is off to you sir or maāam.
Contributing by proposing YOUR corrections for docs is more productive than silly sarcasm.
So, yes, we all know it is browser cache, but, how do i clear the cache ON THE APP???
It would be nice to have a convenient link next to messages, where possible, that jumps you to the relevant location to reset your cache.
Anyone know of a deeplink to that command on the iOS client?
For anyone using the app on Android.
- Open the app
- Go to settings ā companion app
- Scroll way down to troubleshooting
- At the bottom you should see āreset frontend cacheā
This worked for me to get pages loading that had āerror while loading pageā
Hahahah. The IT Pro Shame Honeypot. ![]()
This is what it needs to be done.
A little message after the update saying āyou need to clear your CLIENT cacheā with a link to the right place to clear it. Either the app section in the companion app or to browser instructions.
To those saying that they use confusing/fuzzy wording because there is the companion app⦠all native wrappers offer you a way to know if your frontend is running in a browser or the native app. Then you can easily adjust the wording to match whatever client you are on. It is not a big deal, it just requires to care about your user experience
Or just restart the phone.
Thatās too much of a sledge hammer approach