Skip to content

Releases: Nicxe/f1_sensor

v4.0.0

21 Feb 08:01
12131b0

Choose a tag to compare

F1 Sensor – v4.0.0

GitHub Downloads (all assets, specific tag)

"Good morning, good afternoon, good evening, wherever you are watching us from, it is finally time, all of the questions we’ve asked will get an answer. Welcome to Melbourne"

It’s been a long winter, and the last two weeks have been packed with testing and improvements during pre season. This is the final update before lights out in Melbourne.

Live Data Card, Blueprints, and a lot of improvements

This release brings improved live sync with lap identification, support for brand new live data cards, and official blueprints for automations.

📚 F1 Sensor documentation - https://nicxe.github.io/f1_sensor/


☕ Support This Project

If you find F1 Sensor useful and want to support continued development, you can do so via Buy Me a Coffee. Your support helps fund ongoing maintenance, new features, and long term improvements.

Buy Me A Coffee


Better live delay sync with mid race lap identification

A new calibration reference, Lap sync (race/sprint), lets you sync live delay at any point during a race or sprint.

Official blueprints, now clearer and more controllable

Two fully supported blueprints are included:
• Race Control notifications
• Track Status lights and notifications

New calendar entity for the full F1 season schedule

The full season schedule is now available as a native Home Assistant calendar entity.
Each session appears as a separate calendar event with accurate start times, location, and description, including practice, qualifying, sprint qualifying, sprint, and race.

Experimental 2026 regulation sensors

Two new live sensors are added to reflect 2026 regulation changes replacing DRS:
Straight Mode with states normal grip, low grip, disabled
Overtake Mode binary sensor for track wide energy boost availability

These are based on pre season observations and should be considered experimental

New device structure and automation triggers

F1 Sensor is now split into six dedicated sub devices, making everything easier to browse and automate: Race, Championship, Session, Drivers, Officials, and System.

You also get nineteen new device automation triggers directly in the Home Assistant automation editor

⚠️ BREAKING CHANGE
The previous single F1 Sensor device is replaced by six sub devices. Entity IDs do not change, but anything organized by device in dashboards, plus device based conditions or actions in automations, must be updated to the new structure.

placeholder_cards_overview

F1 Sensor Live Data Cards

Full changelog

New features

  • Add beta session timer sensors for elapsed and remaining F1 time
    This release introduces new session timer sensors that expose time remaining and time elapsed for live F1 sessions, with logic aligned to official timing streams and session start events instead of local restart time. The feature also includes race three-hour cap timing and improved fallback handling so timer values stay useful during reconnects and restarts. This is a beta feature and has not been fully validated across all race control scenarios yet, so behavior may still be adjusted as more real-world sessions are tested.

  • Add experimental Straight Mode and Overtake Mode sensors for 2026 regulations
    Two new live sensors are added to reflect the 2026 regulation changes that replace DRS. The Straight Mode sensor shows whether the active aerodynamic system is permitted on track, with three possible states: normal grip, low grip, and disabled. The Overtake Mode binary sensor shows whether the track-wide energy deployment boost is currently available. Both sensors are based on data observed during 2026 pre-season testing and should be considered experimental until confirmed against live race conditions. The exact messaging format from Formula 1 may be adjusted in a future update once the first race weekend has been evaluated.

  • Add F1 season calendar entity with per-session events
    The full Formula 1 season schedule is now available as a native Home Assistant calendar entity. Each session, including practices, qualifying, sprint qualifying, sprint, and race, appears as a separate calendar event with accurate start times, location, and description. This makes it possible to view the entire season in the Home Assistant calendar panel and to create automations that trigger based on session times. The existing season sensor is not affected.

  • Add mid-race lap sync for live delay calibration
    A new "Lap sync (race/sprint)" option is now available in the live delay reference selector, allowing users to synchronize their live delay at any point during a race or sprint session. When armed, the system captures the next completed lap as a reference point. The user then presses "Match live delay" when they see that same lap complete on their TV broadcast, and the delay is set automatically. This is especially useful for users who join a broadcast mid-race or need to recalibrate a drifted delay without waiting for the next session.

  • Enable all sensors by default and auto-enable new sensors on update
    All sensors are now enabled by default when setting up the integration. Previously, users had to manually select which sensors to activate, and new sensors added in updates required reconfiguration to appear. The integration now stores which sensors the user has explicitly disabled rather than which ones are enabled, so any new sensor introduced in a future update is automatically available without requiring reconfiguration. The sensor multi-select remains available for users who want to disable specific sensors they do not need. Existing installations will have all new sensors enabled automatically on the next update, while previously disabled sensors remain unchanged.

  • Split F1 Sensor into dedicated sub-devices and add automation triggers
    All entities are now organized across six dedicated devices: Race, Championship, Session, Drivers, Officials, and System. All entity IDs remain unchanged, so automations and dashboard cards that reference entities by their ID will continue to work without any modifications. Any automation that referenced the device itself, rather than individual entities, will need to be reviewed and updated to point to the correct new sub-device.

  • Switch weather forecast provider to Open-Meteo for improved global accuracy
    The weather sensor now uses Open-Meteo instead of the previous provider to fetch forecasts for upcoming race locations. Open-Meteo automatically selects the best available weather model based on the circuit's geographic location, which means forecasts for races in Bahrain, Saudi Arabia, Japan, Singapore, the Americas, and other regions are significantly more accurate. All existing weather attributes remain unchanged, and three new attributes are now available for both current conditions and race start forecasts: wind gusts, visibility, and a standardized weather condition code.

Bug fixes

  • Apply live delay to session elapsed and remaining timers
    Session Time Remaining and Session Time Elapsed now respect the configured live delay, so their values stay aligned with delayed live data. If live delay is set to 30 seconds, both timer sensors are delayed by 30 seconds as well. This keeps dashboard timing consistent across all live sensors.

  • Entity names now display in the language configured in Home Assistant
    Entity names previously appeared in English regardless of which language was set in Home Assistant, because the built-in translation system was not being used. Names are now resolved from the active language and update automatically when the language preference is changed.

  • Exclude high-frequency timer sensors from activity history logging
    Track Local Time, Session Time Remaining, and Session Time Elapsed are now excluded from activity history to prevent unnecessary per-second log noise. This reduces database churn and makes activity timelines easier to read while keeping the sensors fully available for dashboards and automations.

  • Exclude race three-hour timer from live Activity logging
    This update fixes an issue where the race three-hour limit timer could still generate frequent Activity entries in the sensor view. The timer is now excluded the same way as the other high-frequency session timers, including live Logbook streaming and recorder filtering. This prevents per-second Activity spam while keeping the current state visible and accurate in the UI.

  • Improve default sensor friendly names without changing existing entity IDs
    Sensor and binary sensor names now use cleaner, human-friendly labels such as Track status instead of underscored internal keys, and the redundant F1 prefix is removed from default friendly names. Existing user customizations are preserved, so manually renamed entities are not overwritten. Entity IDs remain stable through suggested object IDs, which avoids breaking dashboards and automations while improving naming for new or non-customized entities.

  • Keep F1 Sensor available when a reload cannot complete cleanly
    This update improves rel...

Read more

v3.1.1

18 Feb 11:29
b02c527

Choose a tag to compare

F1 Sensor – v3.1.1

GitHub Downloads (all assets, specific tag)

Bug fixes

  • Keep live timing active when the primary session index is outdated
    When the primary live schedule index is behind and does not include a newly started session, the integration now checks a secondary schedule source instead of staying idle. This allows live timing to connect during active sessions even when index updates are delayed. Session status parsing was also hardened for streamed responses, reducing false negatives that could otherwise stop live detection.

☕ Support This Project

If you find F1 Sensor useful, consider supporting its development

Buy Me A Coffee GitHub Sponsors

v3.1.0

11 Feb 17:08
1883a4e

Choose a tag to compare

F1 Sensor – v3.1.0

GitHub Downloads (all assets, specific tag)

Replay mode and expanded race intelligence

F1 Sensor 3.1 introduces Replay Mode, making it possible to replay historical Formula 1 sessions in real time directly in Home Assistant. Combined with a large set of new live sensors and reliability improvements, this release significantly expands both analysis and automation possibilities during race weekends.

If you find F1 Sensor useful and want to support continued development, you can do so via Buy Me a Coffee. Your support helps fund ongoing maintenance, new features, and long-term improvements.

Buy Me A Coffee


Replay Mode

Replay Mode lets you replay historical F1 sessions while keeping all live sensors synchronized with the original session timeline.

  • Replay races, sprints, and practice sessions in real time
  • Live sensors update during playback, including race control, track status, weather, timing, and driver positions
  • Pause, resume, and stop playback at any time
  • Replay data is automatically cleaned up when playback stops

A dedicated Replay media player entity provides timeline controls and correct time handling while paused. For race and sprint sessions, playback can optionally start from the formation lap marker to better align with TV broadcasts.

Driver positions and timing

New and expanded timing data provides deeper insight into race progression.

  • New Driver Positions sensor with grid position, current position, and lap times
  • Pit in, pit out, and retirement status per driver
  • Fastest lap details per driver, including lap number and lap time
  • Indicator for the overall fastest lap of the session

Incidents, penalties, and track limits

Race control information is now exposed in more detail and with improved resilience.

  • Track limits sensor with total counts and per-driver breakdowns
  • Deleted lap times, warnings, and penalties per driver
  • Investigations sensor showing active investigations, decisions, and historical outcomes
  • Incident and track-limit data is preserved across Home Assistant restarts and cleared predictably when sessions end

Tire performance and strategy

Live tire data makes it easier to understand pace and strategy during sessions.

  • New Tire Statistics sensor with aggregated tire performance data
  • Top three fastest lap times per tire compound
  • Total laps driven and tire sets used per compound
  • Delta comparison between compounds
  • Pit delta time showing total time loss compared to a normal race lap

Circuit and session context

Additional metadata improves context before and during sessions.

  • Circuit map image URLs available in race sensors
  • Country flag URLs for race and season sensors
  • New sensor showing the current local time at the circuit, including time zone and UTC offset
  • Extended session metadata available before sessions go live
  • Improved handling of track grip status from race control messages

☕ Support This Project

If you find F1 Sensor useful, consider supporting its development

Buy Me A Coffee GitHub Sponsors

F1-card 2

"F1-sensor live data cards" comming soon

Full changelog

New features

  • Add a replay media player with timeline controls
    Adds a dedicated Replay media player entity so you can play, pause, stop, and scrub through historical sessions with a progress bar and time display. It keeps the timeline accurate by pausing time while playback is paused and resetting to zero when stopped.

  • Add circuit map image URL to race sensors
    The Next Race and Current Season sensors now include a new attribute called circuit_map_url. This attribute provides a direct link to the official Formula 1 circuit layout image

  • Add country flag URLs to race sensors
    The current season and next race sensors now include country flag information for each circuit location.

  • Add driver positions sensor with lap-by-lap timing
    Introduces a new Driver Positions sensor that exposes grid position, current position, and lap times per driver for dashboards and automations.

  • Add fastest lap details to driver positions
    Driver positions now include the overall fastest lap with the driver, lap number, and time, plus a per‑driver indicator you can use to highlight the fastest lap in dashboards and lists.

  • Add pit and retirement status to driver positions attributes
    Driver positions sensor now expose clear status fields for pit in/out and retirements

  • Add pit delta time to pit stops
    The pit stops sensor now reports pit delta, showing the total time loss from entering the pits, stopping, and rejoining compared to a normal race lap. This complements pit stop time and pit lane time so you can see the full impact of each stop in dashboards and automations.

  • Add replay mode for watching historical F1 sessions
    You can now play back past F1 sessions synchronized with TV replays or on-demand viewing. Select a session from the dropdown, load it, and press play when the session on your broadcast starts. All live sensors including race control messages, track status, weather data, timing, and driver positions update in real time during playback. Pause and resume as needed to stay in sync with your broadcast. When you stop the replay, cached data is automatically removed to save disk space.

  • Add Saturday as a race week start option
    You can now set Saturday as the first day of race week in the integration settings. This makes the race week sensor better match regions that start the week on Saturday. Existing setups keep their current setting unless you change it.

  • Add session metadata attributes to session status sensor
    The session status sensor now includes attributes such as meeting name, location, country, circuit name, time zone offset, and session start and end times. Previously this information was only available during live sessions through the current session sensor. With this change, the data is accessible as soon as the session enters the pre-session window, typically 60 minutes before the scheduled start. This allows dashboards and automations to display and act on upcoming session details before the session goes live.

  • Add tire statistics sensor for live tire performance analysis
    A new sensor called Tire Statistics is now available under live timing sensors. It provides aggregated tire performance data during sessions, including the top three fastest lap times per tire compound with driver names, total laps driven and tire sets used for each compound, and a delta comparison showing which compound is fastest and how much slower the others are.

  • Add track limits, investigations, and track grip sensors
    Three new live timing features are now available. The Track Limits sensor shows the total number of track limit violations during a session, with detailed per-driver breakdowns including deleted lap times, black and white flag warnings, and any resulting penalties. The Investigations sensor tracks steward investigations and penalties throughout a race, showing active investigations, their outcomes, and a complete history grouped by driver. The Session Status sensor now includes a track grip attribute that indicates whether low grip conditions have been declared by race control, useful for detecting wet or slippery track situations. All three features can be used to build dashboards showing live race incidents or to trigger automations when specific drivers receive warnings or penalties.

  • Add track time sensor showing current local time at the circuit
    A new sensor displays the current time at the race track location, making it easy to understand what time it is for drivers and teams at the circuit. Attributes include timezone name, UTC offset, and the time difference from your local time, helping you quickly compare track time to your own.

  • Let you choose the first day of race week
    You can now select whether race week starts on Sunday or Monday in the integration settings. This makes the race week sensor match local expectations instead of assuming a single global start day. Existing setups keep their current behavior unless you change the setting.

  • Add a formation start marker for race and sprint sessions
    A new formation start marker helps you sync broadcasts with a reliable pre‑start reference, and it is exposed as a binary sensor for automations. Replay playback now starts from this marker when available so you can see the full build‑up. Live delay calibration can also use the formation start marker as an optional reference instead of session live.

Bug fixes

  • Improve event-tracker fallback recovery when upstream schedule responses are partial or updated
    This update makes the live timing fallback more robust when Index.json is unavailable. The event-tracker schedule lookup now continues to alternate timetable sources if one source is present but empty, so valid sessions are still discovered. Retry behavior after 401/403 now uses refreshed endp...
Read more

v3.0.1

14 Jan 14:52
651c6eb

Choose a tag to compare

F1 Sensor – v3.0.1

GitHub Downloads (all assets, specific tag)

Bug fixes

  • Bump tzfpy to >=1.1.0 to fix install on armhf #227
  • Update manifest.json

Documentation

  • Update with missing Championship Prediction sensors

Maintenance

  • Improve stability and future compatibility of the integration
    Network requests now have a timeout to prevent the integration from hanging if an external service is slow or unresponsive. The integration now uses updated date-time handling for better compatibility with future Python versions.

☕ Support This Project

If you find F1 Sensor useful, consider supporting its development:

Buy Me A Coffee GitHub Sponsors

v3.0.0

11 Jan 18:30

Choose a tag to compare

F1 Sensor – v3.0.0

GitHub Downloads (all assets, specific tag)

What’s New?

This is a major release with powerful new capabilities, improved live timing support, and many quality and reliability improvements under the hood.

🆕 Highlights

Live Delay Calibration

Sync live timing with your TV/stream effortlessly:

  • Manual delay setting
  • Guided TV match calibration

Make dashboards and automations align with what you see on screen.

📊 New Optional Sensors

Enable these in integration options to expand your dashboards and automations:

  • Championship Prediction (drivers & teams projection)
  • Pit Stops / Pit Stop Series
  • Team Radio with rolling history
  • Current Tyres
  • Top Three (P1/P2/P3)
  • Race Control messages
  • Sprint Results
  • FIA Decision Documents

🔧 Improvements

  • More robust live timing (SignalR) handling and reconnects
  • Timezone compatibility fixes for tricky environments
  • Next race grace period: “next_race” stays stable for 3h after lights out

🐛 Bug Fixes

Includes multiple fixes discovered during beta testing: manifest adjustments, classification fixes, API enhancements, TTL caching improvements, and more.

For detailed information about all sensors, live data, events, and future updates, please refer to the full documentation.

☕ Support This Project

If you find F1 Sensor useful, consider supporting its development:

Buy Me A Coffee GitHub Sponsors

v2.4.0

24 Nov 18:23
e7dec9f

Choose a tag to compare

F1 Sensor – v2.4.0

GitHub Downloads (all assets, specific tag)

This update brings refinements to the integration as the 2025 Formula 1 season approaches its conclusion. With only two races remaining, we have seen a year full of twists, momentum shifts and unexpected drama. Version 2.4.0 is likely the final update before development shifts toward the 2026 season.

A new and improved documentation site is now available for the integration. See the updated wiki for guides, details and examples: https://nicxe.github.io/f1_sensor/

🔧 Improvements

  • Improved ingestion and parsing of data from the Jolpica F1 API for greater stability
  • Optimised all internal coordinators by passing the config_entry to each one, preventing ContextVar-related runtime issues

🚀 Roadmap for Season 2026

The unofficial F1 Live Timing system exposes a large set of data streams not yet fully used by the integration. Many of these will shape the development focus for the next season.

You can follow or contribute to the ongoing roadmap discussion for the 2026 season here: #159

Race Control & Messaging

  • More robust handling of Race Control messages
  • Providing access to FIA Decision documents for automations and notifications

Timing & Race Dynamics

  • Deeper integration of TimingData (gaps, intervals, sector performance)

Tyres, Stints & Strategy

  • Access to tyre and stint data through

Team Radio & Media Events

  • Direct integration with TeamRadio metadata including audio file URLs

Position & Telemetry

  • Support for compressed feeds such as:
    CarData (speed, RPM, gear, throttle, brake, DRS status)
    Position (real-time car positions on track)

Analytics & Prediction

  • Potential to use advanced series such as
    OvertakeSeries, ChampionshipPrediction, TopThree

And maybe… pitstop analytics

  • Exploring access to DHL pitstop standings for automation and dashboards

2026 will open up even more possibilities for automation, live visualisation and deeper insights inside Home Assistant.


⭐ Support F1 Sensor

If you enjoy using F1 Sensor and want to support its continued development with more live data for the 2026 season, consider buying me a coffee or becoming a GitHub Sponsor.

Buy Me A Coffee
GitHub Sponsors

Your support keeps the project alive and moving forward. Thank you 🙌

v2.3.3

13 Nov 17:40
2c34500

Choose a tag to compare

F1 Sensor v2.3.3

All changes on this release

  • fix: VSC Ending missing #134
  • Normalize Race Control payloads when 'Messages' is a numeric-keyed map #140
  • Improved weather precipitation forecast logic

⭐ Support F1 Sensor

If you enjoy using F1 Sensor and want to support its continued development with more live data for season 2026, consider buying me a coffee, or becoming a GitHub Sponsor!

Buy Me A Coffee GitHub Sponsors

Your support means a lot and helps keep the project alive and growing. Thank you! 🙌

v2.3.2

26 Oct 10:27
316e39d

Choose a tag to compare

v3.3.2 - Bugfixes


🏁 Version 2.3.0

I absolutely love when users from the community reach out with ideas or questions about how to visualize Formula 1 in Home Assistant. That’s exactly what happened this weekend.

I hadn’t planned to release a new version right now, but this one was just too fun to resist — so I’m happy to introduce two brand new sensors:

  • sensor.f1_driver_points_progression
  • sensor.f1_constructor_points_progression

These sensors provide the full dataset (as attributes) needed to create charts and dashboards that show how the points evolve throughout the season — perfect timing as the championship battle heats up.

You’ll find example configurations for both season progression charts (drivers and constructors) in the README file.
Can’t wait to see what you build with them! 🏎️💨

image image

v2.3.1

21 Oct 06:01

Choose a tag to compare

v2.3.1 - Bugfix

🏁 Version 2.3.0

I absolutely love when users from the community reach out with ideas or questions about how to visualize Formula 1 in Home Assistant. That’s exactly what happened this weekend.

I hadn’t planned to release a new version right now, but this one was just too fun to resist — so I’m happy to introduce two brand new sensors:

  • sensor.f1_driver_points_progression
  • sensor.f1_constructor_points_progression

These sensors provide the full dataset (as attributes) needed to create charts and dashboards that show how the points evolve throughout the season — perfect timing as the championship battle heats up.

You’ll find example configurations for both season progression charts (drivers and constructors) in the README file.
Can’t wait to see what you build with them! 🏎️💨

image image

v2.3.0

20 Oct 18:10
ce0458e

Choose a tag to compare

🏁 Version 2.3.0

I absolutely love when users from the community reach out with ideas or questions about how to visualize Formula 1 in Home Assistant. That’s exactly what happened this weekend.

I hadn’t planned to release a new version right now, but this one was just too fun to resist — so I’m happy to introduce two brand new sensors:

  • sensor.f1_driver_points_progression
  • sensor.f1_constructor_points_progression

These sensors provide the full dataset (as attributes) needed to create charts and dashboards that show how the points evolve throughout the season — perfect timing as the championship battle heats up.

You’ll find example configurations for both season progression charts (drivers and constructors) in the README file.
Can’t wait to see what you build with them! 🏎️💨

image image