✨ New Features & 🐛 Bug fixes

⏱️ History Playback Scrubber

Replay where your people (and vehicles, flights, anything with a trail) were, over time — right on the map. A new control button opens a timeline bar at the bottom: press play and every tracked entity's marker glides along its own history while its trail draws itself in; drag the slider to scrub to any moment; pick a speed (1× / 2× / 4× / 8×). The bar shows the exact date & time you're looking at.

It replays the history the card has already loaded, so it adds no API calls and costs nothing. Multiple entities play back together on one shared timeline, so you can watch how everyone moved in relation to each other. When you've picked a date range (via the date-picker or a preset), the timeline spans exactly that range; otherwise it covers the rolling Hours to Show window.

Turn it on in the editor's Controls tab (History Playback), or in YAML:

show_playback_button: true
# optional: where the button sits
show_playback_button_position: TOP_RIGHT

Then tap the ⏱️ button on the map, and use the bottom bar:

• ▶ / ⏸ — play or pause
• slider — scrub to any point in time (pauses playback)
• 1× / 2× / 4× / 8× — playback speed
• × — close and return to the live map

While playback is open the map is frozen on the replay; closing it snaps straight back to live positions and full trails. If an entity has no loaded history yet, set its Hours to Show (or a date range) first.

---

🐛 Fixed: map flickering (reported since v5.1.4)

The map could redraw itself several times a second, on every platform (iOS, macOS, desktop browsers). It only hit some setups, which made it hard to pin down — the trigger was having two or more entities with follow: true whose positions sit close together.

What happened: to keep every followed entity in view the card re-fits the camera, which zooms in past your configured zoom:; a clamp then pulled the zoom back. Each of those camera moves re-triggered the marker pass, which re-fitted, which clamped… a loop that redrew the whole map continuously. (v5.1.3 escaped it by accident — a side effect there switched follow off after the first move.)

Now the fit is capped while it happens, so it lands directly on your configured zoom in a single camera move — no overshoot, no snap-back, no loop. You can keep follow: true on as many entities as you like. If you worked around this by turning follow off, you can turn it back on.

🌗 "Auto" theme now actually follows Home Assistant's light/dark

The Auto theme option (also the state when no theme_mode is set) used to be a misnomer — it quietly applied a fixed dark theme and never sensed anything. Now it tracks Home Assistant's light/dark mode: your map uses Dark Blueish Night while HA is dark and Light Blueish Day while HA is light, and it switches live the moment HA flips (e.g. a scheduled day/night theme). Pick any specific theme by name to opt out and pin it.

Heads-up for upgraders: if you never set theme_mode, your map was always the dark Dark Blueish Night. With this change it will now match HA — so on a light HA theme the map turns light. Want the old always-dark look? Set theme_mode: "Dark Blueish Night" explicitly. (Themes style raster maps only; vector maps use color_scheme as before.)