frontend icon indicating copy to clipboard operation
frontend copied to clipboard

Persistent Notification Count on Restart

Open woodmj74 opened this issue 1 year ago • 13 comments

Checklist

  • [X] I have updated to the latest available Home Assistant version.
  • [X] I have cleared the cache of my browser.
  • [X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

When HA is restarted, the count of Persistent Notifications is not reset without a page refresh - this is different behavior to earlier releases

Describe the behavior you expected

The bell icon counter should represent the actual number of persistent notifications without the need to refresh the page

Steps to reproduce the issue

1: System running with 3 persistent notifications, the bell icon shows a count of 3 2: Restart HA (existing persistent notifications are cleared as part of this) 3: HA now shows a count of 3 but sliding the notification panel out no persistent notifications are present 4: Add a persistent notification, count increases to 4 but the panel only shows 1

What version of Home Assistant Core has the issue?

2023.7.0b3

What was the last working version of Home Assistant Core?

2023.5.x

In which browser are you experiencing the issue with?

Chrome Version 114.0.5735.199 (Official Build) (64-bit), Edge Version 114.0.1823.67 (Official build) (64-bit)

Which operating system are you using to run this browser?

W11

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

woodmj74 avatar Jul 01 '23 18:07 woodmj74

Same issue but upgraded from 2023.5.x to 2023.6.2

Kisty avatar Jul 01 '23 18:07 Kisty

I have exactly the same issue. Version 2023.07.1

henkhoekema avatar Jul 09 '23 14:07 henkhoekema

It's not updating the count when you dismiss them via an automation and the page hasn't refreshed in a while. If the page has refreshed in the past ~5 minutes, the automation will clear the count.

Refreshing the page updates to the proper count.

Petro31 avatar Jul 13 '23 12:07 Petro31

It's not updating the count when you dismiss them via an automation and the page hasn't refreshed in a while. If the page has refreshed in the past ~5 minutes, the automation will clear the count.

There's no automation in play here. Its a straight forward restart - all PN's are cleared as part of this process but the visual counter doesn't update this.

Refreshing the page updates to the proper count.

Fully agree it does. I was raising the change in behavior since persistent notifications were changed in 2023.06 (I think).

woodmj74 avatar Jul 13 '23 13:07 woodmj74

There's no automation in play here. Its a straight forward restart - all PN's are cleared as part of this process but the visual counter doesn't update this.

I'm adding to the issue. I'm saying that this is also an issue. It's all related. I have an automation and this is occurring.

Petro31 avatar Jul 13 '23 13:07 Petro31

has been on/off since a long time (not saying this is the exact same thing) and when I filed this over a year ago, it was said maybe not Frontend? https://github.com/home-assistant/frontend/issues/17137

also maybe related: seeing my evening theme still being used when I open the next morning, and the day theme should have been loaded. Somehow there is a more generic issue with the frontend not auto-updating. I did set the relevant configuration option in the profile settings to Not disconnect hoping that would influence this erratic behavior, but it doesnt.

Mariusthvdb avatar Jul 21 '23 08:07 Mariusthvdb

I think this is a browser cache issue. When I tried in an incognito tab, I didn't see the problem

Kisty avatar Jul 27 '23 12:07 Kisty

Tried to clear browser data/cache, same issue with "Steps to reproduce" as described.

domolys avatar Aug 05 '23 14:08 domolys

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Nov 03 '23 15:11 github-actions[bot]

Issue retested on 2023.11 and still present

woodmj74 avatar Nov 03 '23 16:11 woodmj74

It's still happening to me on 2023.12 as well.

finity69x2 avatar Jan 17 '24 15:01 finity69x2

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Apr 16 '24 17:04 github-actions[bot]

Still an issue!

VDRainer avatar Apr 16 '24 17:04 VDRainer

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Jul 15 '24 19:07 github-actions[bot]

keep

Mariusthvdb avatar Jul 15 '24 20:07 Mariusthvdb

Keep +1

henkhoekema avatar Jul 15 '24 20:07 henkhoekema

Will be fixed by #21405

karwosts avatar Jul 16 '24 00:07 karwosts