Just swipe down on the page in iOS. Completely resetting the cache is rarely needed. Otherwise it’s in the debugging menu in the iOS app settings.
Why? It works and cleans up any other lingering unneeded cache stuff.
Another +30 IT Pro bumped in this honeypot. And yes, +1 for ‘clear client cache’ 
2 Likes
So for people that want a bit more specificity, because it still took me a while to figure out what folks were talking about in the app…
When in the Home Assistant App - select settings in the sidebar. Then Select Companion App from the list of options
Then you will see debugging option…
then you will see clear frontend cache option…
3 Likes
I’m just loving this thread!
In Healthcare IT since 1988, straight out of college, first ‘computer’ used was a RML 380Z back in 1981 at school.
Like others, I still got caught by this warning message, mine was with a recent Mushroom Cards update!
AR
1 Like
I’ve been in IT for 25 years (mostly in tech support) and I wasn’t sure what exactly it was asking for either. Compounding the issue, browsers make it hard to even find an option to clear the cache (except for an overkill ‘clear everything all at once’ button in the settings).
1 Like
Open developer tools in your browser and leave it open (F12 for most browsers).
Right click the refresh icon of the browser > Empty cache and hard reload
I use Wallpanel Android on two Samsung tablets mounted to the wall. How does one “clear the frontend cache” on that?
Unfortunately the only “foolproof” solution I have found is to reboot the tablets, which is a PITA, and decidedly sub-optimal to describe to my significant other when I’m not there.
This is complicated, of course, by slightly buggy code on the devices which as often as not refuse to connect to my wi-fi because the “password is incorrect”???
cheers
I have been programming for 43 years now. Back then I made a disassembler for the TRS-80.
Now I have finally understood what is meant by a frontend cache, but I am still looking for this setting for my brand new TI-30 
Hey there. You seem to be fond of throwing the “go fix it yourself then” line at people but you don’t seem to have examined what would actually be required.
I’ve found all of the localization strings for the iOS and Android mobile clients, and I will do the find/replace and submit a PR for those – but I am struggling to find the string for the native frontend.
Edit: I found it (actually, I had to ask an AI to find it, which positively disgusts me). The notification I’m looking for is actually in the HACS/integration repository. This mistake is sprawling, and has memetically infected even third-party repositories in their attempts to be consistent with upstream. It’s like a bloody infohazardous SCP. I feel like I am cleaning up after a biological event.
Maybe you shouldn’t be so cavalier about how much time it takes to submit a proper pull request to a repository you’ve never had to be familiar with – especially when there’s probably a developer sitting right here on these forums who could at least tell us where to find it and spare everyone who might try the wasted effort.
The complaint comes in – and is valid – when ultimately it comes to pass that someone has done the work and the PR is either ignored or rejected anyway. I anticipate my effort to be answered in this way, judging from the fact that it isn’t considered important enough for HA to fix themselves. So I expect you, being so very keen on people doing more than silly sarcasm, will do your own part and support both the PR set and the feature request which will link to it.
More edits: considering how many parties will likely have to agree on the fact and nature of all of this stupidity, I am sure I have an uphill battle to fight. Yes, yes; to contribute by “proposing YOUR corrections” is “more productive” indeed. How easy for you to say.
1 Like
You want to know the most frustrating thing? Spelunking through the code, you can find many many examples – especially in documentation markdown – of HA developers calling this thing by its correct name. Internally, and in any situation where it is discussed with any detail at all, HA refers to the thing as the “browser cache” or the “client cache.” In the XML for localizing strings on Android platforms, the proper cache to clear is referred to explicitly as the “webview cache.” These people know what the proper distinction is, but one individual made the decision to dumb it down for some imagined audience and, in so doing, made it worse.
The mistake only appears wherever a particular toast or notification must be displayed, and this is where the misleading shorthand is always introduced.
Cleaning up others’ messes. Story of my life.
3 Likes
Someone is a bit restless here. 
I will still use the term frontend. 
1 Like
Also found this by Google search as was looking through various settings in HA. Thankfully many many others were confused by this. Jeez why can’t developers just think about the end users and KISS!
1 Like
Although I’ve known how to clear the cache I came here after a search just to see if I could get insight on why the term was used.
For giggles (and frowns) I tried the Companion App > Debug > Reset Frontend Cache option. (Normally I go to Android app settings, force the app to quit and clear the cache).
The problem with the Debug option (on Android at least) is that it must clear cookies too, as it disassociated Browser Mod from my device. There were a ton of settings I had to reconfigure as I couldn’t figure out how to match an old device config with a new “browser”.
This is what preprocessor directives are for!
#if COMPANION-APP
browser == FString("Reset Frontend Cache"),
#else
browser == FString("Reset Browser Cache")
But since its not cpp and therefore no compile-time switches, Python might be something like:
COMPANION_APP = True # or False
if COMPANION_APP:
browser = "Reset Frontend Cache"
else:
browser = "Reset Browser Cache"
Pretty trival to implement, must be a design decision for consistency and readability.
Oh snap, I should’ve read the whole thread. There’s the reason lol
How would you clear the cache when using a Safari PWA on macOS?
Also googled and learnt that “You need to manually clear the frontend cache after updating.” means clear browser cache.
Because F1 isn’t available on Android keyboards and the frontend documentation didn’t provide any clues either, I started searching after I got the famous “You need to clear the frontend cache” warning.
So here I am, after more than 25 years in IT and started fiddling around with computers in the late '80’s.
Who wants a drink?
BTW. For those who can’t find this feature in the Android app, please follow these steps: Go to Settings > Companion app > Troubleshooting (almost completely down at the bottom) > Reset frontend cache
1 Like