v0.6.8

Maintenance: manifest key ordering per hassfest; no functional changes.

v0.6.7

Fix: 'Custom element doesn't exist' on dashboards where another card loads the scoped-custom-element-registry polyfill (iCloud3, ring-tile-card, etc.). The polyfill replaces the element registry after load; busybar-card now re-asserts its definition afterward, and Lovelace rebuilds automatically.

v0.6.6

Screen mirror now renders the front display as round LED dots on black, matching the physical matrix's look and readability (back OLED mirror unchanged).

v0.6.5

Fix: screen mirror colors - the front framebuffer is 24-bit BGR (LVGL memory order), so red and blue were swapped on the card (e.g. the clock app's red calendar rendered blue).

v0.6.4

Card robustness on crowded dashboards: never throws on double-load (define guard + customCards dedupe) and prints a BUSYBAR-CARD version banner to the console so load status is visible at a glance among other cards.

v0.6.3

Fix: screen mirror now renders - the firmware sends the framebuffer base64-encoded (MG_REPLY_IMAGE), which the integration now decodes before interpreting pixels.

v0.6.2

Card fixes: entities now resolved via the HA entity registry (immune to device renames - fixes 'missing: custom, screen, mode...' on renamed devices), and the screen mirror shows the real error message instead of 'Bar unreachable'.

v0.6.1

Fix: 'Custom element doesn't exist: busybar-card' - the card is now registered as a proper Lovelace resource (with a version-busting URL) instead of relying only on extra_js_url, which browsers with a cached app shell never load. YAML-mode dashboards: add /busybar-static/busybar-card.js as a module resource manually.

v0.6.0

New custom Lovelace card (auto-registered, just add type: custom:busybar-card): live 1-second mirror of the Bar's actual LED display (front or back), mode selector, BUSY/CUSTOM toggles, screen picker, timer, brightness/volume sliders, and physical button controls, all styled as a virtual BUSY Bar.

v0.5.2

Adds in-repo brand icons (HA 2026.3+ mechanism) and CI validation (hassfest + HACS action). No functional changes.