Acknowledge/snooze on one display propagates to all displays

[OldSmurf56]

What problem does this solve?

I am still enjoying this great piece of software. I have two 12" displays in my house. In case of an alert, this will show on both - and of course also on my laptop and mobile device. I have noticed that even though I snooze/acknowledge an alert in one place, I have to do this on all other devices as well.
Am I doing something wrong or is this an impossible feature to implement?

Best regards

Proposed solution

I am not the programmer ... sorry :-(

Alternatives you have considered

No response

Before submitting

• I searched existing issues and discussions and could not find a similar request.

[djdevil]

Hi @OldSmurf56 👋

You're not doing anything wrong — that's a real limitation of how the card was built. Snooze / dismiss state lives in each browser's own localStorage, so every wall panel, laptop and mobile app has its own isolated copy. Ack on one → the others still see the alert until you ack there too. Annoying with 4 displays!

Fixed in the next release (v1.3.9.9.5).

When you snooze, dismiss, or clear a persistent alert on any device, the card now broadcasts the change over Home Assistant's WebSocket event bus (a custom event called alertticker_sync). All other card instances connected to the same HA instance are subscribed and update their local state in real time.

Result: ack on one → all displays clear the alert instantly, without you having to touch each one.

No configuration required — it just works out of the box. If you're the only user in the house, all your 2 wall panels + laptop + mobile will stay in sync automatically.

Small caveat: if a device is completely off/closed at the moment you ack (e.g. laptop lid closed), it won't magically catch up when you reopen it — its old local state is still there until the next real-time sync event or the alert re-triggers. For the "always-on" wall panels + phone Companion + open laptop scenario you described, this is a non-issue.

I'll ping this thread the moment the release is live. Thanks for the report — it was a genuinely useful piece of feedback that clarified a real UX gap. 🙏

[djdevil]

🎉 Released in v1.3.9.9.5!

Update all your displays (wall panels, laptop, mobile Companion) via HACS and clear the browser cache. From this version onwards, snoozing or dismissing an alert on any device propagates in real time to all the others.

Would love to hear if it works as expected in your 4-display setup. Enjoy! ✅

[OldSmurf56]

Hi @djdevil
Sorry about the late feedback .. I have been busy doing other stuff. I finally tested this fix today - several times and starting from different screens. But unfortunately no luck - postponing for e.g. 1 hour won't clear the Warning on other devices which are always on. But I still enjoy your AlertTicker :)

[djdevil]

Hi @OldSmurf56 👋

No worries about the delay, and thanks for the honest feedback — better a real-world report late than never!

Sorry to hear it's not working in your setup. There's one likely explanation I should have flagged earlier in the original write-up: the cross-device sync currently only works if every device is logged into Home Assistant with an admin user account.

The reason is a Home Assistant security policy — the WebSocket API restricts custom fire_event calls (and their subscriptions) to admin users only. If any of your always-on displays is signed in with a non-admin HA user (e.g. a dedicated "wallpanel" user without admin privileges, which is a common security-hardening choice), that display silently skips the sync and stays out of the loop.

Quick check

For each of your 4 devices (both wall panels, laptop, mobile):

1. HA → Settings → People
2. Look at the user account each device is logged in as
3. Check whether Administrator is enabled for that user

If any of them is a non-admin, that's the culprit. Two options to fix it:

• Grant admin to that user (simplest, but weakens the security-hardening you may have done on purpose)
• Wait for a proper fix: I can rework the sync mechanism to use an HA input_text helper instead of custom events — that path works for all users regardless of role. It's a bigger change but it removes this limitation entirely. Happy to prioritize it if this is your case.

If everything IS admin

Then something else is going on and I'd love to dig in. Could you:

1. On one of the always-on wall panels, open the browser DevTools (F12) → Console tab
2. Snooze/postpone an alert on a different device
3. Screenshot anything that shows up in the Console at that moment

That'll tell me whether the sync event is being delivered but ignored, or not delivered at all.

Reopening this so we track it properly. Thanks for testing again! 🙏

[No-DNS]

would also love to see non-admin users would sync. when running fully kiosk / kiosk_mode, it is conveniant to set user as non-admin to hide stuff.
Keep it up, doing good! ;)