Skip to content

[Bug]: driver_positions grid_position is the qualifying order, not the starting grid after penalties #830

Closed

Description

@Tagliax

Prerequisites

  • I am running the latest version of F1 Sensor
  • I have searched existing issues
  • I have restarted Home Assistant
  • All information in this issue, including logs and screenshots, is written in English. Issues containing non-English content will be closed without response.

F1 Sensor Version

5.7.2 (the same code is still in the v5.8.0 tag)

Component

Integration

Device

Raspberry Pi 5

Home Assistant Installation Type

Home Assistant Container

System Architecture

aarch64

Current Behavior

2026 Singapore GP: Russell qualified P6 and got a 20-place grid drop (FIA Doc 79), so he started P19.

During the whole race sensor.f1_live_drivers_driver_positions reported grid_position: "6" for RUS, and every car that qualified behind him was shifted by one (PIA 7 instead of 6, LAW 9 instead of 8, HUL 11 instead of 10, ...). In total 16 of 22 drivers had a wrong grid_position.

At the same time sensor.f1_live_session_f1_starting_grid had the correct grid: status confirmed, source live_timing_gridpos, RUS grid_position: 19, qualifying_position: 6.

So positions gained/lost from the grid computed from driver_positions are wrong for most of the field (RUS shown as losing 11 places instead of gaining 10).

Expected Behavior

grid_position in driver_positions should match the confirmed starting grid (after penalties) when it is available.

Logs

No error is logged.

Activity

  1. LePousson commented on Oct 11, 2026

    @LePousson

    I think that, according to FIA Documents, that the final starting grid was published just some minutes before the race ...

  2. Tagliax commented on Oct 11, 2026

    @Tagliax
    Author

    @LePousson Thanks — the official FIA grid may well be published late, but in this case the data was already in the live feed: sensor.f1_live_session_f1_starting_grid switched to confirmed (source live_timing_gridpos) at 11:07:41Z, ~50 min before the start, with RUS 19. driver_positions kept grid_position: "6" for RUS until the end of the race, so it isn't a timing issue: it never picks up the post-penalty grid, even though the integration already has it.

  3. LePousson commented on Oct 11, 2026

    @LePousson

    oh ok, i misunderstood what you meant exactly ... I also noticed that difference but when the FIA is using systems that crashed when raining or when someone forgot to push a button (loooool), not surprising that some feeds are outsynced ...

  4. added a commit that references this issue on Oct 12, 2026
    568cc69
  5. github-actions commented on Oct 12, 2026

    @github-actions
    Contributor

    A fix for this issue is now available in v5.8.0-beta.3, a BETA pre-release of F1 Sensor.

    To test the beta version, open HACS in Home Assistant, go to Integrations, and find F1 Sensor. Click the three-dot menu and select Redownload. Make sure Show beta versions is enabled in the HACS settings for this integration. Alternatively, you can download the release manually from the Releases page.

    Your feedback on the beta is very welcome — please report any issues you run into so they can be addressed before the stable release.

  6. github-actions commented on Oct 16, 2026

    @github-actions
    Contributor

    A fix for this issue is now available in v6.0.0, the latest stable release of F1 Sensor.

    To update via HACS, open Home Assistant, go to HACS → Integrations, find F1 Sensor, and click Update. If you installed it manually, download the latest release from the Releases page and replace the existing files.

    After updating, restart Home Assistant to apply the changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions