WTH Can we have it automatically reload the frontend when there is an update?

Month of "What the heck?!"
1

After HA updates the front end typically after a short while (but not immediately) to informl me there is an update and click on the reload button. Why can’t it do it for me such as;

  • a check box or option that will automatically reload it on future updates without interaction (per web browser/session?)
  • An indication after x seconds it will automatically reload

Seems like there is a way to do it with browser mod (Automatic frontend reload or trigger on Lovelace update? - Configuration / Frontend - Home Assistant Community) , but having it to do it automatically without extras would be nice!

2

You mean refreshing the cache? Like ctrl+f5? I’m assuming it isn’t as straight forward as you’re assuming, otherwise it would be implemented already. Or possibly because it is such a minimal thing, no one has thought to implement it.

Is it really a sore point for you to refresh your open dashboard tabs after a frontend component update?

3

This is a great suggestion.

Refreshing /clearing the cache is a PITA to do on mobile especially when in kiosk mode.

1 Like
4

I was wondering if it tells me I need to click on the reload button that appears why it doesn’t do itself? When you have multiple devices it’s just one more thing to do when updating is to do the update on each. If there’s a browser mod does that imply that it could do it technically without anything client side?

5

That’s one of things I love about the Fully Kiosk browser and integration. I have an automation to refresh all my devices after a restart of HA.

6

What happens on desktop when you have X tabs open to your dashboard? Or any tab open to Hass? How will it know which tabs to actually refresh? What if one of those tabs is open on an automation that you’re working on and haven’t saved? Or editing dashboards, etc.

That is an example of things to consider besides just 1 use case. As another poster pointed out, you can setup automations to remedy your use case.

7

Not sure why you are asking me about desktop - I was referring only to mobile.

8

Because your chiming in on a feature request that isn’t specifically for mobile, lol.

9

I don’t see the problem with my post but I’ve voted for this and will now bow out.

1 Like
10

Never said there was a problem, I am merely pointing out that there are more things to consider besides 1 use case.

11

why? how? what happens if I don’t? what if multiple people are using the system, do they all need to clear their cache? How would they know?

Please don’t explain to me how to do it. I just shouldn’t have to, cache-busting is a well-known topic.

12
1 Like