Skip to main content

Pit Stops

Review each driver’s stops, fitted tyres and available pit timing. Compare stop duration and pit-lane time while keeping the latest tyre information beside the stop history.

Pit Stops card showing its dashboard layout
Example Pit Stops layout. Appearance depends on your session, version and display options.Select the image to open it full size.

Availability

F1TV live / Replay. Enable Pit Stops, Current Tyres, Driver Positions and Driver List. Live pit-stop timing uses optional F1TV Auth enhanced data. Replay Mode can show pit details when they are present in the archive; it does not guarantee every timing field.

Add the card

  1. Open your dashboard, select Edit dashboard, then Add card.
  2. Search for F1 and select the Pit Stops card.
  3. Select Pit Stops under Data Sources and confirm the driver and tyre sources. Keep stop count and tyre information visible. Enable tyre laps if you want stint age alongside each stop.
  4. Select Save.

If the card is missing from the picker, follow Card installation. With more than one F1 Sensor entry, use the sources from the same entry; see Entity selection.

Minimal YAML

Use this in a manual dashboard card. Replace any entity ID with the one in your installation if it differs.

type: custom:f1-pitstop-overview-card
pitstops_entity: sensor.f1_pitstops
theme_mode: auto

Use the card

Pit-stop duration and total pit-lane time measure different parts of a stop. Missing values are left unavailable rather than estimated. Delta compares available stop times with the fastest stop.

Configuration

Data sources

The defaults below are the card’s fallback values. Automatic discovery connects standard sources to the selected integration entry, including renamed entity IDs. See Entity selection.

OptionDefaultDescription
drivers_entitysensor.f1_driver_listDriver List for names, teams and driver detail. Select the entity from your F1 Sensor entry.
tyres_entitysensor.f1_current_tyresCurrent Tyres for compound and stint detail. Select the entity from your F1 Sensor entry.
pitstops_entitysensor.f1_pitstopsPit Stops for stop counts and available timings. Select the entity from your F1 Sensor entry.
positions_entitysensor.f1_driver_positionsDriver Positions for timing and running order. Select the entity from your F1 Sensor entry.
auth_status_entitysensor.f1_f1tv_token_statusF1TV token status entity used for enhanced-data notices.
no_spoiler_entityswitch.f1_no_spoiler_modeEntity whose on state enables spoiler protection. See No Spoiler Mode.

Display and behavior

OptionDefaultDescription
theme_modedarkdark, light or auto; auto follows Home Assistant. See Appearance.
titlePit Stops & TyresCard title
show_headertrueShow the card header
show_table_headertrueShow column labels
show_tlatrueShow driver TLA
show_full_namefalseShow full driver names
show_team_logofalseShow team logo
team_logo_stylecolorcolor or white for team logos.
show_statustrueShow pit stop status
show_tyretrueShow tyre compound
show_tyre_lapsfalseShow laps completed on the current tyre
show_pit_counttrueShow number of stops
show_pit_timetrueShow pit stop duration
show_pit_lane_timetrueShow total pit lane time
show_pit_deltatrueShow delta to fastest stop
show_availability_noticetrueShow informational enhanced-data notices. Expired, invalid or rejected authentication warnings stay visible.
font_stylewidewide, balanced or system. See Typography.

All bundled cards also support f1_entry_id and card actions. Home Assistant layout settings remain available in the dashboard editor.

When data is missing

Before the first stop, an empty history is expected. Missing pit timing during a live session can indicate that enhanced data is unavailable. Check the notice and F1TV status; a replay may simply lack that field. Hiding availability notices does not hide authentication errors.

For an Entity not found message, check the selection in Data Sources and confirm that the entity is enabled in F1 Sensor. For a missing card type or an old interface after an update, use the card loading checks.