Skip to content

fix: register the card as a dashboard resource - #12

Merged
owenvoke merged 1 commit into
mainfrom
bugfix/card-registration
Sep 25, 2026
Merged

owenvoke merged 1 commit into
mainfrom
bugfix/card-registration

Conversation

@owenvoke

Copy link
Copy Markdown
Owner

Pages served while Home Assistant was still starting didn't include the card, as it was only added as an extra frontend module, which isn't picked up after a page loads. Dashboards then showed "Custom element doesn't exist: airtrail-card" until refreshed.

The card is now also registered as a Lovelace resource (in storage mode), which dashboards load themselves. It's kept up to date as the card changes, and removed along with the last AirTrail entry.

Please check the CONTRIBUTING document for more information.

Pages served while Home Assistant was still starting didn't include the
card, as it was only added as an extra frontend module, which isn't
picked up after a page loads. Dashboards then showed "Custom element
doesn't exist: airtrail-card" until refreshed.

The card is now also registered as a Lovelace resource (in storage mode),
which dashboards load themselves. It's kept up to date as the card
changes, and removed along with the last AirTrail entry.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@owenvoke
owenvoke merged commit 1c2dfc4 into main Sep 25, 2026
6 checks passed
@owenvoke
owenvoke deleted the bugfix/card-registration branch September 25, 2026 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant