v5.5.0-beta.2

F1 Sensor – v5.5.0-beta.2

⚠️ This is a beta release intended for testing.

New features

• Add a unified Weekend Hub for session analysis
  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.
• Add favorite driver entities and automation triggers
  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.
• Automatically bind bundled cards to F1 entities
  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.
• Improve F1 Sensor and live data card accessibility, localization, 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.
• Complete F1 Sensor security and quality hardening

Bug fixes

• Connect F1TV Token Helper reliably from Home Assistant Container 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.
• Prevent misleading tyre data warnings after compounds arrive
  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.

Maintenance

• Correct Linux visual baselines
• Enforce the coverage floor consistently in CI
• Fix Phase 5 workflow compatibility
• Make conflict checks resilient
• Stabilize coverage across CI environments
• Stabilize Phase 5 frontend checks
• Update artifact upload action runtime
• Weekend hub improments

☕ Support This Project

If you find F1 Sensor useful, consider supporting its development