Notification Badge isn't cleared upon restart

[dimaguy]

Checklist

• I have updated to the latest available Home Assistant version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

When I restart home assistant with unread/non-dismissed notifications, the unread badge remains in place until I refresh the page even if notifications are cleared on the server side.
This happens on both mobile and browser

Describe the behavior you expected

When home assistant is restarting, the frontend should reload the notifications section in order to clean the badge

Steps to reproduce the issue

1. Restart home assistant with a non-dismissed notification
2. Look at the notifications button
3. Notice the badge is still there

What version of Home Assistant Core has the issue?

core-2024.4.0

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Firefox 125.0b8

Which operating system are you using to run this browser?

Windows 11

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

This issue affects both web and mobile app

[github-actions]

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.

[dimaguy]

This is still an issue

[github-actions]

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.

[karwosts]

Fixed this a couple releases back with #21405