[Bug - Minor] History log overwritten by last card instance

[Breizh3122]

Hello,

Thank you again for the threshold support! I've found a minor issue when running multiple instances of the card in a vertical-stack-in-card.

The Issue:
The history log for all card instances is being overwritten by the history of the very last card defined in the YAML.

Observed Behavior:
If I have separate blocks (Doors, Ink, Batteries), the Doors and Ink blocks do not show their own history. Instead, they both display the history entries belonging to the Batteries block (the final instance). It appears the history object is global and is being hijacked by whichever instance was initialized last.

Example Configuration:

type: custom:vertical-stack-in-card
cards:
  - type: custom:alert-ticker-card
    alerts:
      - entity: binary_sensor.door_contact
  - type: custom:alert-ticker-card
    alerts:
      - entity: sensor.ink_level
  - type: custom:alert-ticker-card
    alerts:
      - entity: sensor.battery_level

Expected Behavior:
Each card instance should maintain and display an independent history log scoped only to its own configured entities.

Thank you for your work on this card!

[djdevil]

Hi @Breizh3122 👋

Great catch — you diagnosed it perfectly. The history was stored under a single hardcoded localStorage key (atc-history) shared by every card instance on the page. The last instance to initialize would overwrite everyone else's log on every save.

Fix in v1.2.5:
Each card instance now generates its own unique storage key derived from its sorted entity IDs:

atc-history-cover.portone|sensor.battery|sensor.ink
_loadHistory and _saveHistory both use this instance-scoped key, so cards with different entity sets are completely independent and never interfere with each other.

One-time note: on first update to v1.2.5 the old shared atc-history key is silently abandoned — existing history is lost once, no action needed after that.

Thanks for the detailed report and the YAML example, it made the root cause immediately obvious!

[djdevil]

Hi,
The feature/fix you requested is now available in AlertTicker Card v1.2.5

Please update the card via HACS (or manually) and let me know if everything works as expected on your end. If you run into any issues or the behavior is not what you had in mind, feel free to reply here and I'll take a look.

Thanks for your patience and for helping improve the card!

[Breizh3122]

Hi,

I’ve installed and tested version 1.2.5, and everything is working correctly on my end.

Thanks for addressing this so quickly.