Releases: Nicxe/f1_sensor
v3.0.0
F1 Sensor – v3.0.0
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:
v2.4.0
F1 Sensor – v2.4.0
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_entryto 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.
Your support keeps the project alive and moving forward. Thank you 🙌
v2.3.3
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!
Your support means a lot and helps keep the project alive and growing. Thank you! 🙌
v2.3.2
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_progressionsensor.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! 🏎️💨

v2.3.1
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_progressionsensor.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! 🏎️💨

v2.3.0
🏁 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_progressionsensor.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! 🏎️💨

v2.2.2
v2.2.2
Bugfix for #122
🏁 F1 Sensor v2.2.0
🚀 New Sensors
Version 2.2.0 introduces two new sensors powered by the F1 Live API, bringing richer and more dynamic real-time data to Home Assistant.
sensor.f1_current_session
Provides complementary information to sensor.f1_session_status.
While f1_session_status shows if a session is live, this sensor tells you which session is currently running — for example Practice 1, Qualification, or Race.
Ideal for dashboards and automations that adapt to the active session type.
sensor.f1_driver_list
A new sensor listing all drivers of the current season directly from the Live API.
Each driver includes key details such as:
- racing_number – driver’s race number
- team_color – hex color of the team (great for custom cards and charts)
- headshot_small / headshot_large – driver portrait URLs
- name / tla / team – driver name, abbreviation, and team
Perfect for building custom cards and dynamic dashboards showing live driver and team data.
🧩 Improvements
- Optimized Live API update logic for faster and more stable data refresh.
- Improved session transition handling for smoother updates.
- Enhanced error handling and data validation for better reliability.
🐛 Bug Fixes
- Fixed initialization issues and Live API reconnection errors.
- Corrected inconsistent data types and improved log clarity.
- Better recovery when API responses are missing or delayed.
🔧 Other
This release lays the foundation for future real-time features such as live driver timing, enhanced race tracking, and improved visual components for dashboards.
v2.2.1
v2.2.1
Bugfix for handle async issue
🏁 F1 Sensor v2.2.0
🚀 New Sensors
Version 2.2.0 introduces two new sensors powered by the F1 Live API, bringing richer and more dynamic real-time data to Home Assistant.
sensor.f1_current_session
Provides complementary information to sensor.f1_session_status.
While f1_session_status shows if a session is live, this sensor tells you which session is currently running — for example Practice 1, Qualification, or Race.
Ideal for dashboards and automations that adapt to the active session type.
sensor.f1_driver_list
A new sensor listing all drivers of the current season directly from the Live API.
Each driver includes key details such as:
- racing_number – driver’s race number
- team_color – hex color of the team (great for custom cards and charts)
- headshot_small / headshot_large – driver portrait URLs
- name / tla / team – driver name, abbreviation, and team
Perfect for building custom cards and dynamic dashboards showing live driver and team data.
🧩 Improvements
- Optimized Live API update logic for faster and more stable data refresh.
- Improved session transition handling for smoother updates.
- Enhanced error handling and data validation for better reliability.
🐛 Bug Fixes
- Fixed initialization issues and Live API reconnection errors.
- Corrected inconsistent data types and improved log clarity.
- Better recovery when API responses are missing or delayed.
🔧 Other
This release lays the foundation for future real-time features such as live driver timing, enhanced race tracking, and improved visual components for dashboards.
v2.2.0
🏁 F1 Sensor v2.2.0
🚀 New Sensors
Version 2.2.0 introduces two new sensors powered by the F1 Live API, bringing richer and more dynamic real-time data to Home Assistant.
sensor.f1_current_session
Provides complementary information to sensor.f1_session_status.
While f1_session_status shows if a session is live, this sensor tells you which session is currently running — for example Practice 1, Qualification, or Race.
Ideal for dashboards and automations that adapt to the active session type.
sensor.f1_driver_list
A new sensor listing all drivers of the current season directly from the Live API.
Each driver includes key details such as:
- racing_number – driver’s race number
- team_color – hex color of the team (great for custom cards and charts)
- headshot_small / headshot_large – driver portrait URLs
- name / tla / team – driver name, abbreviation, and team
Perfect for building custom cards and dynamic dashboards showing live driver and team data.
🧩 Improvements
- Optimized Live API update logic for faster and more stable data refresh.
- Improved session transition handling for smoother updates.
- Enhanced error handling and data validation for better reliability.
🐛 Bug Fixes
- Fixed initialization issues and Live API reconnection errors.
- Corrected inconsistent data types and improved log clarity.
- Better recovery when API responses are missing or delayed.
🔧 Other
This release lays the foundation for future real-time features such as live driver timing, enhanced race tracking, and improved visual components for dashboards.
v2.1.0
🚀 Release 2.1.0
This release introduces new live data sensors, extended attributes, and a critical fix for incomplete season results.
✨ New Features
Live Data Enhancements
-
Added
sensor.f1_track_weather
Provides current on-track weather during an active session. Updates approximately every minute with attributes such as:- Air temperature
- Track temperature
- Rainfall
- Wind speed
-
Added
sensor.f1_race_lap_count
Shows the current lap number during an active race.
(Note: does not update during practice or qualifying sessions) -
Added Race Control messages as events
Published underf1_sensor_race_control_event.
Examples include:- Flag changes (CLEAR, YELLOW, RED, SC, VSC)
- Steward notes
- Incident reports
🐛 Bug Fixes
- Fixed #62 — Season results now correctly include all completed races for the current season. Previously, only partial results were shown.
🔧 Improvements
- Extended attributes for
sensor.f1_last_race_results(#92)
Now includes more detailed race result information, making it easier to build automations and dashboards.
📌 Notes
- Live sensors only update shortly before, during, and shortly after a session (practice, qualifying, sprint, race). Outside of these times, they will not update.
- Race Control is currently only available as events, but will in the future also be published to a sensor.
Thanks to everyone who tested, reported, and contributed! 🙌