Skip to content

Beta 2 - #630

Merged
Nicxe merged 17 commits into
betafrom
dev
Sep 2, 2026
Merged

Beta 2#630
Nicxe merged 17 commits into
betafrom
dev

Conversation

@Nicxe

@Nicxe Nicxe commented Sep 2, 2026

Copy link
Copy Markdown
Owner

Description

Related issue

Fixes #

Type of change

  • 🐛 Bug fix (corrects existing behavior without breaking anything)
  • 🚀 New feature (adds functionality)
  • ⚠️ Breaking change (existing automations, entities, or config will stop working or behave differently)
  • 🏎️ Bundled live data card code
  • 📋 Blueprint (new or updated blueprint)
  • 📚 Documentation only
  • 🔧 Refactoring or internal cleanup

How has this been tested?

  • Tested locally with a real Home Assistant instance
  • Existing automations and dashboards still work as expected after the change

Checklist

  • I have read CONTRIBUTING.md and am targeting the correct branch
  • Changes under custom_components/f1_sensor/www/** target dev as bundled card code, not the standalone documentation path — if applicable
  • Code is formatted and passes lint check (ruff format and ruff check) — if applicable
  • Tests have been added or updated and pass locally — if applicable
  • Translations updated if new UI strings were added — if applicable
  • No merge conflicts with the target branch

If this adds or changes a blueprint:

  • The blueprint has been imported and tested in Home Assistant
  • Triggers and conditions work as expected in a live environment

If this is a breaking change:

  • I have clearly described what will break and what users need to do to adapt

Nicxe and others added 17 commits August 25, 2026 11:35
The F1 Sensor integration now recognizes partial live tyre updates after compounds have already been received. Existing tyre data remains visible without an incorrect warning that the upstream feed is missing compounds.
The new Weekend Hub keeps the selected session, driver, spoiler setting, and gap reference aligned across supported F1 cards. It brings live and replay timelines, clean-lap strategy estimates, selected-lap telemetry comparisons, and confidence-based battle analysis into one responsive experience. Capability-aware states explain when data is still waiting or unavailable without adding raw telemetry to Home Assistant states.
…ion, and reliability**

The F1 Sensor integration and live data card now provide consistent translations with English fallback, native card actions, and improved keyboard and screen-reader support. Responsive behavior is verified across common display sizes and accessibility settings. Stronger performance, dependency, and release integrity checks make future updates more reliable without requiring changes to existing setups.
…er setups**

The F1 Sensor integration now sends tokens to the Home Assistant address currently used by the browser instead of an inaccessible container address. This allows F1TV pairing to complete reliably across container and proxy-based installations. Fixes #628.
Bundled F1 cards now discover entities from the integration registry, including renamed and suffixed entity IDs. Cards infer a configuration entry from an existing selection, preserve explicit overrides, and avoid guessing when multiple entries are ambiguous.
feat: **Automatically bind bundled cards to F1 entities**
F1 Sensor now lets users persist a favorite driver, exposes that driver’s live race and team-color data, and provides device triggers for position, pit, and retirement changes. Existing configurations remain unchanged unless the new feature is enabled.
feat: **Add favorite driver entities and automation triggers**
@Nicxe
Nicxe merged commit 9c697b2 into beta Sep 2, 2026
19 checks passed
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.

2 participants