jpettitt/weather-radar-card v3.7.0-alpha1

v3.7.0-alpha1 — first exercise of viewer-state framework (adjustable playback speed)

on GitHub

⚠️ Alpha pre-release. First user-visible consumer of the per-user state framework that shipped dormant in 3.6.5 (#175). Two weeks of feedback expected before promotion through beta / rc / stable, matching the 3.6.1-rc1 → 3.6.1 cadence.

Not recommended for production dashboards — install only if you want to exercise the persistence path and report findings. HACS users: you'll only see this in your update list if you've enabled "Show beta versions" in HACS settings.

What's new

Adjustable playback speed (#157) — contributed by @genericJE, their third contribution after #155 and #172. Toolbar button cycles ¼× / ½× / 1× / 2× / 4×; editor dropdown sets the YAML default. Built on top of the viewer-state framework from #175.

Sparse-storage convention: a user's runtime override clears automatically when the chosen value matches the YAML default. The practical effect — an admin editing the YAML default propagates the new value to every viewer who hasn't explicitly overridden via the toolbar.

viewer_layer_control admin toggle — new editor toggle in the Animation section. Opt-in to per-user, per-card preference persistence via Home Assistant's frontend storage. Off by default; when off the toolbar speed button still works but the value is session-only.

type: 'custom:weather-radar-card'
show_playback: true          # exposes the toolbar speed button
playback_speed: 1            # YAML default; users can override via toolbar
viewer_layer_control: true   # admin opt-in to persist overrides per-user across browsers/devices

When viewer_layer_control is first enabled, the card auto-mints a _layer_state_id nonce into the card YAML — the per-card storage key that lets a single user have different preferences across different cards on the same dashboard.

Internal changes

First end-to-end exercise of the per-card identity nonce + ViewerState hydrate path introduced in 3.6.5's framework. The WS hydrate round-trip races against the toolbar's first paint — on a fresh page load with a non-1× override stored, the speed button label briefly shows the YAML default then snaps to the override once HA's frontend/get_user_data resolves (typically one render frame). Documented for awareness; alpha audience can confirm whether this single-frame flicker is acceptable.

How to report feedback

Open an issue at https://github.com/jpettitt/weather-radar-card/issues — particularly interested in:

• Per-user persistence working correctly across devices when logged into HA
• Cross-card preference isolation (set different speeds on two cards on the same dashboard)
• The hydrate-race flicker — perceptible / acceptable / not?

Full Changelog: v3.6.5...v3.7.0-alpha1