F1 Sensor – v4.1.0

The opening weekend in Melbourne did not only give us racing, it also provided valuable feedback from real world use of F1 Sensor 4.0. During the race in Australia, a number of bugs and edge cases were identified in live timing, Replay Mode, and some sensors.

This update therefore focuses mainly on stability and bug fixes, while also introducing a few new features that make the integration even more flexible and useful. If you enjoy using F1 Sensor and want to support its continued development, you can do so via Buy Me a Coffee.

Highlights in 4.1

No Spoiler Mode

A new global setting makes it possible to freeze all results, live data, and standings until you choose to enable them again. Perfect if you cannot watch the race live and want to avoid spoilers on your dashboard.

Replay Mode – 30 second catch-up controls (experimental)

Replay Mode now includes experimental buttons to jump 30 seconds backward or forward. When you jump, all events within that interval are replayed so that track status, race control, and other sensors end up in the correct state.

More detailed qualifying data

The Driver Position sensor now includes more information from qualifying, including times for Q1, Q2, and Q3, segment positions, and whether a driver was eliminated in a segment. This makes it possible to display the full qualifying picture directly in dashboards.

Sector times with F1 color logic

Sector times are now available directly in the Driver Positions sensor with support for classic F1 logic.

Improved lighting automations

The Track Status blueprint can now control light groups, not just individual lights, making it easier to build race lights at home.

RGB color attributes for teams and tyres

Team and tyre colors are now also exposed as RGB values, making them easier to use directly in Home Assistant automations.

☕ Support This Project

If you find F1 Sensor useful, consider supporting its development

Full changelog

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 No Spoiler Mode to prevent F1 session results from reaching your dashboard
  A new global switch called "No Spoiler Mode" is now available under the F1 Sensor system device. When turned on, all live session data, race results, standings, and FIA documents are frozen so no spoilers can appear in your dashboard while you are waiting to watch a session. Schedule and calendar data continue to update as normal so you always know when the next race is. When you turn the mode off, all blocked data is immediately refreshed and delivered. The setting is remembered across Home Assistant restarts.

• Add qualifying segment times and elimination status to driver positions sensor
  Each driver in the driver positions sensor now includes their best lap time from Q1, Q2, and Q3 separately, along with their finishing position within each segment and whether they were eliminated at the end of that segment. A new top-level attribute shows which qualifying segment is currently active. This makes it possible to build dashboards that display the full qualifying picture, including who was knocked out in Q1 and Q2, all within a single sensor.

• Add sector times to driver positions with purple, green, and yellow classification support
  Each driver in the driver positions sensor now includes current lap sector times for all three sectors, along with flags indicating whether each sector is the session's overall fastest (purple) or the driver's personal best (green). Personal best sector times are also tracked separately, giving dashboards everything needed to display sector timing in the classic F1 color scheme. Sector times are automatically cleared during safety car and virtual safety car periods, reset between qualifying segments, and preserved after the session ends for post-race review.

• Allow the track status blueprint to control light groups
  The track status blueprint now lets you select either a single light or a light group as the target. This makes it easier to drive multiple lights from one automation without extra wrappers or duplicate automations. Existing setups that target a single light continue to behave the same way.

• 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.

Blueprints

• Add optional WLED preset support to the F1 Track Status blueprint
  The F1 Track Status blueprint can now control a single WLED light using Home Assistant preset entities while still working the same way for regular lights and groups. This makes it possible to use WLED presets for race states such as yellow, red, safety car, and virtual safety car, including any animations or segment layouts stored in those presets. The update also improves scene snapshot and restore behavior so WLED companion settings like preset, palette, intensity, and speed are restored more reliably without affecting existing setups.

• Add an option to mute blue flag notifications in the Race Control blueprint
  Blue flag messages can now be filtered out in the Race Control Notifications blueprint. This helps reduce notification spam during busy parts of a race while keeping other race control alerts active. Existing automations keep their current behavior until you enable the new filter.

• Correct condition evaluation in F1 track light and race control blueprints
  This update fixes a condition handling issue that could cause automations to behave incorrectly even when filters should block or allow actions. The track status light blueprint and the race control notification blueprint now evaluate their gating conditions reliably, so session, DND, and filter logic works as intended. As a result, notifications and light changes trigger only when the configured rules are actually met.

• Stop the track status blueprint from retriggering on session updates
  The track status light blueprint now reacts only to real track status changes and the initial transition into an active session. This prevents extra automation runs and repeated light changes when session status updates during a session, while still keeping the light in sync at session start and turning it off correctly when the session ends.

• Add optional Activation Conditions to F1 race control and track status blueprints
  Both blueprints now include a new optional Activation Condition field so advanced users can add flexible state-based logic, including combinations like state, not-state, and grouped conditions. This gives more control over when notifications and light behavior should run.

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.

• Correct Q3 knockout shading for drivers eliminated in Q2
  Drivers eliminated in Q2 could be shown incorrectly during Q3 because they were still present in the timing snapshot. This fix now follows the official qualifying data more accurately, so Q1 and Q2 eliminations are exposed correctly and qualifying timing cards dim the right drivers at the right time.

• Correct stop-and-go investigation status handling
  Investigations and penalties now update correctly when a driver receives a stop-and-go penalty and later serves it. This prevents drivers from remaining incorrectly marked as under investigation after the stewards have issued and completed the penalty, improving live race accuracy.

• 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 current session visible during qualifying replays
  The current session sensor now stays aligned with replay playback during qualifying sessions instead of falling back to Unknown after the original session end time has passed. This makes replay mode more reliable and keeps dashboards and automations based on the active session label working as expected.

• Keep F1 entity IDs stable regardless of Home Assistant language
  New F1 entities now keep predictable English entity IDs even when Home Assistant is running in another language. This fixes cases where translated names changed the generated entity IDs and made automations, examples, and support guidance harder to follow. Existing installations keep their current entity IDs and friendly names, so updating does not rename anything that is already set up.

• 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.

• Remove integration and device name prefix from entity display names
  Entity names previously appeared in dashboards and automations with a redundant prefix, such as "F1 - Race Next race" or "F1 - Championship Driver standings". They now show only the entity-specific label, for example "Next race" or "Driver standings". Any entity names you have customized manually are not affected by this change.

• Update F1 blueprints to modern automation syntax for stable trigger traces
  The Track Status Light and Race Control Notifications blueprints now use Home Assistant’s modern syntax for triggers, conditions, and actions. This fixes cases where automation traces showed trigger description errors such as the “includes” message even when the automation fired. The change improves compatibility with current Home Assistant versions while keeping the existing blueprint behavior unchanged.

• 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.

Documentation

• Add Context7 AI assistant documentation page
• Update for 4.1

Maintenance

• Improve timeout handling and require a compatible Home Assistant version
  This update moves the integration to Home Assistant’s modern timeout handling for better long-term reliability and compatibility with current core releases. The integration now declares Home Assistant 2023.8.0 as the minimum supported version.

Other changes

• Add missing translation

☕ Support This Project

If you find F1 Sensor useful, consider supporting its development