v0.8.1 - Fix card not loading on YAML-mode dashboards
Patch release fixing a real bug that surfaced on Home Assistant cores that bootstrap Lovelace before integrations. v0.8.0 worked on most setups but broke on dashboards in YAML mode.
Fixed
- Card not loading on YAML-mode dashboards. The integration registered the card as a storage-mode Lovelace resource and then returned early on success. Storage-mode resources are only consumed by storage-mode dashboards, so dashboards with
mode: yaml(whether globally vialovelace: mode: yamlor per-dashboard) never received the script. The fix always also callsadd_extra_js_url, which injects a<script>tag on every Lovelace render regardless of dashboard mode. (#15, reported by @mcsmith1981)- Existing cards stopped rendering with a "Configuration Error" placeholder.
- The add-card dialog showed an infinite spinner on the Album Slideshow thumbnail.
- Both symptoms shared the same root cause:
album-slideshow-card.jswas never executed in the browser, socustomElements.get("album-slideshow-card")returnedundefined.
- Card banner version in the browser console now matches
manifest.json. The hardcodedVERSIONconstant inalbum-slideshow-card.jslagged behind in v0.8.0 (banner said0.7.1); the newversion-syncCI guard introduced in this release prevents future drift.
Notes
- Module loads are deduplicated by URL and the card's
customElements.define()calls are idempotency-guarded, so dashboards picking up the card via both paths is a harmless no-op. - No changes to camera entities, services, options flow, or storage schema. Upgrade is in-place.
Upgrading
- HACS → Album Slideshow Camera → 3-dot menu → Redownload (pick v0.8.1).
- Restart Home Assistant.
- Hard-refresh the dashboard (Ctrl/Cmd-Shift-R) so the browser fetches the new
album-slideshow-card.js.
Full changelog: v0.8.0...v0.8.1