[Bug]: Pit counter not increasing (Race Lap card)

[simonedimarzio]

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

4.1.0

Device

Raspberry Pi 4

Home Assistant Installation Type

Home Assistant OS

System Architecture

No response

Current Behavior

Just to notify that pit counter stays zero, instead tyre age is updated correctly.
Noticed inside the Race Lap card.

Thank you for your work!
KR
Simone

Expected Behavior

Pit counter updates correctly

Logs

[Nicxe]

I traced this to the integration rather than the Race Lap card, and it appears to be separate from #427.

During the China race stream, PitStopSeries was not reliable enough on its own, but the live feed still exposed pit stop totals through the driver timing data. The integration only built sensor.f1_pitstops from detailed pit stop events, so if those events were delayed or missing, the sensor stayed at 0 even though tyre age and the rest of the live data continued to update correctly.

I have implemented a fix that also uses the live driver timing pit stop counts as a fallback. That means the pit stop sensor and the Race Lap card can still show the correct totals even when the detailed pit stop event stream is incomplete. I also added regression tests to cover both the direct pit stop event path and the fallback path.

[simonedimarzio]

Thank you.
During the race, I noticed that sensor.f1_pitstops got stuck at zero for the entire session.

[Nicxe]

Thanks for the report. The pit stop counter staying at zero is caused by a change in F1's live timing API. The PitStopSeries stream, which provides detailed pit stop data (counts, durations, timestamps), now requires F1TV authentication to be delivered during live sessions. Without a valid token the stream is simply empty, so the counter never increments. The tyre age you see updating correctly comes from a different stream (TimingAppData) that remains openly available, which is why that part still works fine.

This is a data source restriction rather than an integration bug. I don't currently support F1TV authentication and I'm not sure if I will — I don't have an F1TV Pro subscription to develop against.

The pit stop data is still present in the archived session files after the session completes, so it works correctly in replay mode. In the next version I'm making the pit stops sensor replay-only, meaning it won't show up during live sessions at all. This avoids the misleading "0 stops" state during a live race. The config UI will clearly label it as replay-only as well.

[Nicxe]

I want to correct my earlier explanation here after reviewing newer capture data. I cannot confidently reduce this to one simple cause yet. What I can say is that the detailed live pit stop feed is not something I currently trust enough to present as normal live data, so I still need to treat this carefully. From a user point of view, I do not want to overstate this as solved or simple yet. Thanks for reporting it, because this is exactly the kind of case where the live feed behaves in a more awkward way than it first appears.

[github-actions]

Included in beta release v4.2.0-beta.2.

[github-actions]

Included in release v4.2.0.