v1.11.1

v1.11.1 is a backward-compatible patch release that restores reliable home-marker visibility and adds provider-isolated CARTO raster-key support.

Fixed

• Restored Leaflet's expected pane stacking and marker positioning so the home marker remains visible above loaded basemap and weather tiles through redraws. This addresses #21.
• Isolated the map's stacking context so Leaflet attribution and map controls remain below the card's playback bar, legend, and layer badge.
• Added a dedicated carto_api_key to authenticate both CARTO base and label tiles and remove the API KEY REQUIRED watermark.
• Kept CARTO credentials separate from the existing Stadia Maps and Esri basemap_api_key; credentials are never sent to another basemap provider.
• Cleared stored provider-specific keys when the basemap provider changes in the visual editor.
• Added the required OpenStreetMap credit to CARTO attribution and improved attribution readability.

CARTO key support builds on #23 by @bossanova808. Thanks to Jeremy Daalder for the original contribution.

Configuration

CARTO users should obtain a free browser key and configure it as:

basemap_provider: carto
carto_api_key: YOUR_CARTO_KEY

If you previously placed a CARTO key in basemap_api_key, move it to carto_api_key. Stadia Maps and Esri continue using basemap_api_key; BOM requires neither field.

Attribution remains an end-user setting through show_attribution. CARTO requires visible OpenStreetMap and CARTO attribution, so CARTO users should leave it enabled.

Validation

• 82/82 automated tests passed, including regression coverage for marker and control stacking, CARTO base and label URLs, key encoding and provider isolation, editor key handling, and attribution toggling.
• A real Chromium paint-order check confirmed that playback controls remain visible and interactive where CARTO attribution overlaps them, while the home marker remains visible and correctly positioned.
• GitHub Actions passed dependency auditing, tests, the production build, release-metadata checks, and committed-bundle parity on the exact tagged commit: https://github.com/AshtonAU/bom-radar-card/actions/runs/33120342315
• The live BOM upstream check passed for all 34 supported layers and 38 representative PNG tiles.

Upgrade through HACS, then hard-refresh Home Assistant so the browser replaces its cached card bundle. CARTO users should also hard-refresh after adding their key because previously watermarked tiles may remain cached.