I try to stay a stupid end user… if it is needed to activate the changes…why doesn’t this happen then automatically? Or even better make sure that it doesn’t hit the outdated version in cache.
If this just means clear the browser cache then the wording definitely needs to be changed.
Clearing the front end cache to me sounds more like clearing the web server’s public facing cache where it takes dynamically generated web pages and caches them into a version of a static page to speed up serving.
I wouldn’t consider an individual user’s browser caching to be the front end of the web server.
2 Likes
Pleas, how i could clear cache in Mozilla?
Thank you
40+ years in the industry…my cache is really old and only 64KBytes…buffer overrun years ago…I rely on Google to find the bathroom.
You all are doing fine.
In the browser it is obvious for most people what clearing the cache is, but not in the companion apps. In IOS, in the settings, there is a similarly named option to… clear the front end cache. In Android, you need to go to the Android app settings, and delete the app cache from there.
Asking a user to clear the browser cache while they are in a companion app will definitely steer most of them the wrong way. Now at least there is a chance they will figure out they should not go to Safari or Chrome.
It is annoying though that you are asked to go click somewhere else in the app when you are using in the companion app. But there’s likely a technical reason it isn’t done for you.
Perhaps “clear the client cache” would be better wording.
It’s developer speak. Happens every time Devs write error codes which are directly readable without anyone translating it to a more human-readable version along the way.
Just because I’m bored and because this thread has gone on for far too long, this is what everything means, translated in a way that even dumb-dumbs like me can understand:
-
Front end: Whatever you’re currently seeing when interacting with an application/browser. For HA, it’s the dashboard on whatever device you’ve got 2 feet in front of your eyes. Or 2 inches, depending on your vision.
-
Back end: The actual code. Anything you mess around with in yaml basically, as well as a whole bunch of other stuff you’ll never see unless you dive into GitHub. Mess around with this with the caution of a porcupine in mating season.
-
Middleware: The invisible man in the middle which makes the above two communicate between each other. Stuff like websocket messages or API aggregation. Think of it as a Rosetta-stone-holding mediator between two people on separate continents.
The above is an oversimplified explanation of the actual stuff going on in the background for every digital service you interact with.
I’ve purposely left out other services like data (the informant), because that’s a story for another day, and snitches get stitches.
Hope everything’s clearer now.
You’re telling me for 40 years, all I had to do was clear my browser cache? Ain’t no way…
Thanks, I was wondering about this one too and Google brought me here.
I also created an account just to like the OP’s realisation comment.
And since it seems a thing, 23 years IT development here 
Glad to have this be my first community interaction 
+1, started professionally in IT in 1995
2 Likes
Because of using companion app, my google journey ended here with you.
It looks like an party of IT seniors, I’m dreaming about long time - may I join? 
I’m only 20 yrs in user support and a bit shy but when you will start to share photos of your rare hardware you admire at home, I will do the same 
Anyway, thanks for minutes of laugh, you made my day.
Live long & prosper 
If you are like me and have a wireless multi-function keyboard, hold the function button (FN) and F12 then reload.