iobroker.f1
v0.1.7
Published
Formula 1 live data integration for ioBroker - race information, standings, and live session tracking
Downloads
285
Readme
ioBroker.f1
Formula 1 live data integration for ioBroker — provides race calendar, championship standings, session results, and real-time live session data via the official F1 Live Timing feed and Jolpica API.
Features
- Race Calendar — Next race & session info with countdown (days/hours)
- Full Season Calendar — All rounds of the current season as JSON
- Championship Standings — Driver and constructor standings with points and wins
- Session Results — Race, qualifying, sprint, and practice session results
- Live Session Data — Real-time data via F1 Live Timing SignalR WebSocket
- Track status (AllClear / Yellow / SafetyCar / VSC / RedFlag)
- Session status and name
- Current & total laps
- Time remaining / elapsed
- Track weather (air temp, track temp, rain, wind, humidity)
- Driver positions with gaps, lap times and tyre info
- Top 3 live leaderboard
- Race control messages
- Pit stops
- Tyre compounds per driver
- Team radio
Data Points
See the Usage section above for the complete object hierarchy and update intervals.
Data Sources
| Channel | Source | Update |
|---|---|---|
| schedule/ | Jolpica API (Ergast fallback) | Hourly |
| standings/ | Jolpica API (Ergast fallback) | Hourly + after race |
| results/ | Jolpica API (Ergast fallback) | Hourly + after session |
| live/ | F1 Live Timing SignalR WebSocket | Real-time push |
Requirements
- ioBroker >= 5.0.19
- Node.js >= 20
- Internet connection
- Stable connection to Jolpica API or fallback Ergast API
Installation & Configuration
- Install the adapter via the ioBroker Admin panel or command line
- Open the adapter settings (no user configuration required by default)
- The adapter automatically:
- Fetches the current F1 season calendar hourly
- Updates championship standings after each session
- Provides real-time live session data when sessions are active
- Optional: adjust update intervals in adapter settings if needed
Data Sources & Consistency
The adapter uses multiple data sources with automatic fallback:
| Channel | Primary | Fallback | Behavior | |---------|---------|----------|----------| | Schedule & Standings | Jolpica API | Ergast API | Updated hourly + after races | | Results | Jolpica API | Ergast API | Updated after each session | | Live Data | F1 Live Timing SignalR | OpenF1 API | Real-time push during sessions |
Note: During race weekends, upstream APIs may temporarily deliver mixed-round data (e.g., standings updated before results). The adapter includes retry logic (6 attempts, 10-minute intervals) to ensure data consistency.
Usage
Once installed and started, the adapter exposes ioBroker states under the object path f1.0:
f1.0
├── info.connection (adapter connection status)
├── schedule/
│ ├── next_race_name / round / circuit / country / date
│ ├── next_session_name / type / date / countdown_*
│ ├── weekend_json (all sessions of current weekend)
│ └── calendar (full season as JSON)
├── standings/
│ ├── drivers (JSON array with positions & points)
│ ├── teams (JSON array with constructor standings)
│ └── last_update
├── results/
│ ├── race / qualifying / sprint (JSON arrays)
│ └── last_update
└── live/ (only during session ±30 min)
├── is_live / session_status / track_status
├── laps_current / laps_total / time_remaining / time_elapsed
├── weather / race_control / top_three
├── drivers / tyres / pit_stops / team_radio
└── last_updateStates are updated:
- Hourly for schedule, standings, and results
- Per-session for result details (race, qualifying, sprint)
- Real-time for live session data (during active sessions)
Troubleshooting
"Points mismatch" during race-end window
During the first 60 minutes after a race ends, standings and results may briefly show different round numbers. This is expected behavior — the upstream API refreshes asynchronously. The adapter automatically polls for consistency (6 attempts, 10-minute intervals).
No live data appearing
- Check that a session is currently active (F1 Live Timing typically streams during practice, qualifying, and race)
- Verify internet connection
- Check adapter logs (ioBroker Admin → Instances → F1 → Logs)
- If Jolpica API is unavailable, the adapter falls back to Ergast API
Stale data
Data is cached and updated on a schedule. If data appears outdated:
- Manual trigger: restart the adapter instance
- Automatic: next hourly refresh cycle will fetch fresh data
- After a session: automatic refresh is triggered within 2 minutes of session end
0.1.7 (2026-05-03)
- (bloop) Add: post-race refresh retry logic — 6 attempts every 10 minutes to ensure Jolpica round data stabilizes after session end
- (bloop) Add:
getApiRoundStatus()monitoring function to independently track results vs standings round consistency - (bloop) Fix: points discrepancies during race-end window — verified via cross-API analysis that mixed-round data delivery originates from upstream Jolpica, not adapter mapping
- (bloop) Enhance:
handleSessionEnded()now triggers immediate Jolpica refresh followed by 6-attempt retry sequence with detailed logging
0.1.6 (2026-05-02)
- (bloop) Remove:
results.fp1,results.fp2,results.fp3states — Jolpica/Ergast API does not provide practice session results - (bloop) Remove:
results.sprint_qualifyingstate — Jolpica/Ergast API does not expose a sprint qualifying endpoint (HTTP 400)
0.1.5 (2026-05-02)
- (bloop) Fix: per-session result loading — each session is loaded independently when its scheduled time has passed
- (bloop) Fix: race result buffer increased to 180 min (was 90 min) to account for race duration + API publishing delay
- (bloop) Fix:
weekend_jsonnow shows the currently active race weekend instead of always the next upcoming race - (bloop) Fix:
checkLiveStatusno longer re-fetches the Jolpica schedule API every 60 s — uses cached data from hourly refresh - (bloop) Fix: sprint qualifying and practice states are now explicitly set to
nullwhen the API endpoint is unavailable - (bloop) Fix: double-Z bug in date parsing (
new Date("...Z"+"Z")→ Invalid Date) that caused round detection to always return null - (bloop) Add:
is_sprint_weekendflag inschedule.calendarJSON entries - (bloop) Remove: unused internal
SIGNALR_BASEconstant
For older changelog entries, see CHANGELOG_OLD.md.
License
MIT License
Copyright (c) 2026 Martin (bloop) [email protected]
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Data Sources & Attribution
This adapter relies on the following data sources:
- Jolpica API — Ergast API mirror, primary source for F1 race calendar, standings, and results
- Ergast API — Historical F1 data, used as fallback when Jolpica is unavailable
- F1 Live Timing — Official real-time session data via SignalR WebSocket
- OpenF1 API — Fallback for live session detection
Disclaimer
This project is not affiliated with, endorsed by, or in any way officially connected with Formula 1, the FIA, or any of their subsidiaries or affiliates.
F1®, FORMULA ONE®, FORMULA 1®, FIA FORMULA ONE WORLD CHAMPIONSHIP®, GRAND PRIX® and related marks are trademarks of Formula One Licensing B.V.
This adapter is intended for personal, non-commercial use only.
