I first thought this issue was due to something was currupt but after several updates it still persisted.
Then yesterday my SD card failed and I installed on a SSD today but to my surprise I still have this issue.
Everytime a state changes my frontend still shows the previous stat until I reload the page.
This is the same on all my devices (four androids and two laptops).
See this video how it keeps the old state and only update it after a reload.
And this ‘previous stat’ is kept for hours, it’s not like it updates eventually.
Which installation guide did you follow then? What does it say under your server info on the HA dashboard? You have to get that information.
I don’t understand what you mean: Did you upgrade to 2021.8.8 several times, or did upgrade several times historically from one version to another and the last one was to .8? Did this problem exist on other versions too?
I have upgraded several times from one version to another during two-three months and the problem has still persisted.
I found one entity (script) that is probably deleted in customize.yaml, it was for our alarm in the previous apartment. I deleted that and found nothing else in customize.
I looked at the dashboards and there seemed to be one card in panelmode that was not working. I could not edit it so I deleted it from the raw configuration.
When I saved I got a warning about resources. Noticed I had a legacy resource in the yaml file.
Deleted that and made sure it was in UI.
Restarted and now it seems to work as expected.
So something of the above was probably the problem.
If I should guess it was the card in panel mode or the resource.
Probably should have mentioned it in the first post.
Like koying pointed out, you’re using Custom UI which is a custom integration providing certain additional UI features (like control over icons and their color). Custom UI reads the contents of customize.yaml and uses the parts that apply to it.
Custom UI was originally created to extend the capabilities of States UI which was the predecessor to Lovelace UI. When Lovelace UI was introduced, States UI was allowed to co-exist. Eventually States UI was eliminated and that’s when many features in Custom UI became non-functional (and its author abandoned it).
Mariusthvdb modified Custom UI so that some of its features work with Lovelace UI. If you are using his version of Custom UI, you should report any errors you encounter in his repo.
My choice of quotation could have been better but specifically that you have been using a custom integration that affects the UI for several versions. If you have UI problems, it helps to explain what custom cards or custom integrations you may have that affect the UI’s appearance.
You said it seemed to be related to customize.yaml is true because that’s where Custom UI reads its instructions for customizing the appearance of the UI.
