Skip to content

Improve frontend cache message - #5019

Closed
fdmarcin wants to merge 2 commits into
hacs:mainfrom
fdmarcin:patch-1
Closed

Improve frontend cache message#5019
fdmarcin wants to merge 2 commits into
hacs:mainfrom
fdmarcin:patch-1

Conversation

@fdmarcin

@fdmarcin fdmarcin commented Jan 5, 2026

Copy link
Copy Markdown

When I ran across this, I was confused and found that other people are too: https://community.home-assistant.io/t/how-to-clear-the-frontend-cache/670491

This change uses "browser or app" because clearing a browser cache is known to more users (and more easily searchable).

Previous effort:

When I ran across this, I was confused and found that other people are too:
https://community.home-assistant.io/t/how-to-clear-the-frontend-cache/670491

This change uses "browser or app" because clearing a browser cache
is known to more users (and more easily searchable).
@ludeeus

ludeeus commented Jan 5, 2026

Copy link
Copy Markdown
Member

This needs more effort, see previous attempt #4788

@ludeeus
ludeeus marked this pull request as draft January 5, 2026 20:04
@fdmarcin

fdmarcin commented Jan 5, 2026

Copy link
Copy Markdown
Author

@ludeeus thanks for linking that. What would you say the previous attempt was missing?

As an aside, I think that if we only modify this message, it will already be an improvement. If you think this will confuse people the other way round because the apps still say "frontend cache", we could tweak to "browser or app frontend cache".

@ludeeus

ludeeus commented Jan 6, 2026

Copy link
Copy Markdown
Member

It should be consistent.
Or just removed.

@fdmarcin

fdmarcin commented Jan 11, 2026

Copy link
Copy Markdown
Author

@ludeeus Thanks. I'm guessing you're also saying the change in HACS depends on the apps' UI text.

@bgoncal @TimoPtr @jpelgrom @dshokouhi
Hi! I've read through the previous attempt in iOS and Android repos.
Would y'all be okay with this rename? I'm not fixated on "app cache" specifically, but I think "client" or "frontend" are less helpful here, because it's not how a non-developer user thinks about this. I think the HACS message can be expanded if the cost of brevity is that users are confused.

Mobile apps: button renamed to:

- "Reset client cache"
+ "Reset app cache"

Then HACS integration update message:

- "You need to manually clear the client cache after updating."
+ "You need to manually clear the browser or app cache after updating."

cc @nethershaw

@bgoncal

bgoncal commented Jan 11, 2026

Copy link
Copy Markdown

The button is inside companion app settings > debugging... so, if the user is there usually it is not the average user, it's the admin/more technical user.

Inside the debugging I prefer to have things more explicit, so I wouldn't call it "app cache", since it is not cache generate by the app and could lead people to think this would clean other type of caches that the app really have, perhaps "Reset web view cache" or "Reset browser cache".

@bgoncal

bgoncal commented Jan 11, 2026

Copy link
Copy Markdown

Would creating a deeplink to ask the app to clean web view cache be something interesting? Then any link could trigger that app action

@fdmarcin

fdmarcin commented Jan 11, 2026

Copy link
Copy Markdown
Author

The button is inside companion app settings > debugging... so, if the user is there usually it is not the average user, it's the admin/more technical user.

@bgoncal Yup, this is a good point. I forgot that while I don't consider myself a HA pro, I was doing admin stuff when I came across that message.

In this case, a minimum viable change approach here would be to keep the app button labels, and only edit the HACS message to:

- "You need to manually clear the client cache after updating."
+ "You need to manually clear the browser cache or mobile app client cache after updating."

@ludeeus Would this work for you?

@fdmarcin

Copy link
Copy Markdown
Author

Alright, closing ¯\_(ツ)_/¯

@fdmarcin fdmarcin closed this Feb 26, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators Feb 27, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants