F1 Sensor – v4.1.0-beta.2
⚠️ This is a beta release intended for testing.
New features
-
Add experimental 30-second replay catch-up controls
Replay Mode now includes experimental Back 30 seconds and Forward 30 seconds controls to help you manually catch up with delayed broadcaster replays. When you jump, the integration replays the events inside that window so track status, Race Control, and other replay-driven states land in the correct state at the new position. This is a Version 1 experimental feature and may be refined further as real-world feedback comes in. -
Add RGB color attributes to driver and tyre sensors
Sensors that expose team or tyre compound colors now include a companion RGB attribute alongside the existing hex value. The new attributes, team_color_rgb and compound_color_rgb, return the color as a list of three integers such as [220, 0, 0], which can be passed directly to light entities in automations and scripts without any template conversion. Existing attributes are unchanged.
Bug fixes
-
Clear live mode sensors when a session officially ends
Overtake and related live mode sensors now clear as soon as a session is officially finished, so stale race states no longer remain visible after the end of a session. The integration still follows the official timing feed and will not force Overtake mode to OFF unless that status is actually published. This keeps post-session behavior consistent without inventing states that do not exist upstream. -
Improve delayed live timing updates for Top 3 and other fast race data
This improves how fast-changing live session data appears when live delay is enabled, so Top 3 updates are surfaced more promptly and delayed race data is less likely to appear stuck. The existing delayed delivery model for dense live updates is preserved, keeping the integration aligned with the official timing feed instead of inventing fallback states. Team Radio continues to follow the upstream feed only when that data is actually present. -
Keep fastest lap data consistent across live timing cards
Fastest lap values now stay aligned between the driver timing and tyre statistics views, even when official lap updates arrive through different live timing streams in a different order. This fixes brief mismatches and value flapping during race incidents while keeping the integration faithful to the original Formula 1 data feed. -
Keep qualifying session states consistent during Q1/Q2/Q3 breaks
Qualifying breaks are now treated as part of the same session instead of being handled as if qualifying had already ended. This keeps Session Status in break for the full gap between Q1, Q2, and Q3, while Current Session continues to show Qualifying or Sprint Qualifying until the session is truly over. The result is more reliable live behavior and avoids sensors briefly falling back to unknown between qualifying segments. -
Prevent formation start from triggering after the race
Formation start now only turns on during the pre-start window for race and sprint sessions. This prevents late activations after the session has already gone live or ended, which could otherwise trigger race-start automations at the wrong time. The sensor stays aligned with official timing data and no longer backfills a retroactive marker once the event has passed. -
Prevent stale VSC and Safety Car status after session end
Safety Car and Track Status now clear cleanly when a session is actually over, so they no longer keep or restore stale VSC or Safety Car states during the post-session live window or after a reload. This improves reliability without inventing missing upstream data, and it also preserves the correct qualifying-break behavior so Q1 and Q2 pauses do not trigger false resets. -
Prime race lap count when live timing reconnects during an active race
Race lap count now becomes available immediately when the integration starts or reconnects during an active race, instead of staying unknown until the next lap update arrives. The integration now reads the current official lap count snapshot when live timing connects, which makes reloads and reconnects more reliable without changing the underlying feed behavior. -
Remove false log warning about incomplete season results pagination
The integration logged a warning about incomplete season data at the start of a new season, even when all available data had been fetched correctly. This happened because the warning incorrectly compared the number of completed races to the total count of individual driver result entries. The warning no longer appears under normal conditions and will only fire if a genuine data retrieval failure occurs. -
Correct live session timers around starts, restarts, and finish
Live session timers now follow the official timing data more reliably during session starts, qualifying segment changes, red-flag interruptions, and after the chequered flag. Session time remaining and elapsed no longer carry over incorrect values between qualifying segments, and race timers no longer continue changing after the session has reached its terminal state. This improves correctness for the new live timer sensors introduced in 4.0.0 without inventing start times from advisory race control messages. -
Keep delayed live streams updating instead of stalling
Live delay now applies a fixed offset to incoming live data instead of behaving like a debounce on busy streams. This prevents affected sensors from getting stuck, turning unknown, or only recovering when delay is reset to 0. The fix also keeps delayed clock data updating correctly while preserving the existing brief reload during delay calibration. -
Restore the Safety Car binary sensor name and entity ID
The Safety Car binary sensor is now exposed correctly again after the 4.0.0 naming regression. Home Assistant will no longer register it under a Session-style fallback name, which restores the expected binary_sensor.f1_safety_car entity for dashboards and automations. This improves consistency across languages and makes the sensor easier to find and use after setup or upgrade. -
Update circuit maps to use the new 2026 track images
Circuit map URLs now use the new official 2026 track images where they are available, including support for the new Madrid circuit. This gives users the updated layouts with the latest sector and straight mode visuals while keeping the existing circuit_map_url attribute unchanged. Older or historic circuits continue to fall back to the previous map images so existing setups keep working reliably.
☕ Support This Project
If you find F1 Sensor useful, consider supporting its development