[Feature]: Tweaks after the first race in Melbourne

[BrckedmyRMpro]

Prerequisites

• All information in this issue is written in English. Issues containing non-English content will be closed without response.

Problem to Solve

Some small observations and some feature reqests pictures were included here: https://community.home-assistant.io/t/formula-1-racing-sensor/880842/366?u=angusc

Proposed Solution

@stimo

Great first race!! love the work that you have done to the integration. Coffee has been purchased for your great work.

Just one observation on the Driver and Lap card. It currently only shows the lap sector times but not the gap times from each car in front and the leader. Would it be possible to add this to the card? I checked all the F1 sensors for that attribute but couldn't find it.

Here is the drive card as it appears now:

Here is the example from the f1-dash.com/dashboard:

On the tyre statistics, it looks like all the sensors went off line. or is it my set up? I searched for an updated sensor, but couldn't find any:

I also note that the line height on the Driver & Lap times card is slightly smaller than on the Tyre card, which puts the bottom out of alighment when the two cards are stacked side by side. could you adjust the Driver & Lap times card to be the same line heights so they align?

My last bit of feedback, I see on the TV (F1TV) they showed a remaining battery and over take mode. Would you be able to add that one to your F1 sensors in a nice matching card?

On that note, would you consider using my Race Control message board to make it in to your integration and match the other F1 integration cards?

Alternatives

No response

[Nicxe]

hanks for the detailed feedback and for the coffee — really appreciated! 🙏

Let me go through each point:

• Gap to leader / interval to car ahead
  The data does exist in the F1 live timing feed. It's not currently exposed as sensor attributes, but it's something we want to add. That said, we're not making changes to the sensor data model until version 4.1 — we want to stabilize a few bugs that surfaced during the season opener first.

• Tyre sensors going offline
  This is a known issue we're actively looking into. It's one of the bugs we need to resolve before anything else moves forward. Thanks for confirming you saw it too — that helps.

• Card line height alignment
  This is a dashboard/card layout issue, not a sensor data issue. I'll note it for when we revisit the example cards.

• Remaining battery / overtake mode
  The overtake count data does exist in the feed (OvertakeSeries). The battery/ERS percentage is in a compressed telemetry stream that requires more work to parse reliably. We need to verify what's actually available and stable for 2026 before committing to anything here. This won't happen before 4.1 at the earliest, and only if the data is reliable enough to be useful.

• Race Control message board
  This already exists as a sensor — sensor.f1_race_control. If you're not seeing it, check that it's enabled in your entity list.

To summarize, the immediate focus is bug stability from the Australian GP weekend. New sensor attributes and card features are tracked after 4.1.

[Nicxe]

Thanks again for the detailed feedback here. I went back through this thread with the newer live-feed analysis in hand. Gap-to-ahead and gap-to-leader are still things I think are worth considering. Battery and ERS are a different story, because that live telemetry sits behind F1TV auth, so I do not want to suggest it is something I can make work for normal live use right now. Overtake mode is also something I do not want to promise yet, because I still need better evidence that the live data is stable enough to build on. The tyre problem and the layout issues are better tracked in their own bug threads.