Build your F1 Sensor card

Build a compact weekend overview or a detailed session view with the F1 Sensor card. Choose your content first, then adjust its appearance in the visual editor.

New cards start with the empty Build your own template. The template chooser is open so you can select a preset or add your first module. Existing saved cards keep their modules.

Start with a preset

1. Edit your Home Assistant dashboard and choose Add card.
2. Select F1 Sensor. If you have several F1 Sensor installations, choose which one the card follows.
3. Choose a preset from the table below.
4. Review the preview and save the card.

Preset	Initial content
Race weekend	Overview, weekend schedule and weather.
Weather comparison	Current conditions and race-start forecast.
Follow the session	Session overview, timing and Race Control.
My driver	Session overview, driver timing with recent laps, and Race Control. Choose a driver in the card or editor.
Results and championship	Results, championship standings and points progression.
Build your own	An empty card ready for your first module.

A preset is a starting point. You can change its modules after selecting it. Selecting another preset shows a review before replacing the current content; changing the visual style keeps your content choices.

Preview your card

Home Assistant provides the card's only preview. At the top of it, Preview data starts with Actual data from your installation. Choose Sample data to try practice, qualifying, sprint, race, replay or missing-data scenarios, even when no session is running. Sample data is clearly marked DEMO.

This choice only affects the preview and stays selected while you edit the card. It is never saved in your dashboard configuration. Preview controls cannot change integration settings or start replay playback. On small screens, use Home Assistant's preview toggle to show the same preview.

Reuse your own template

Open Reusable templates in the visual editor, enter a name and export the template JSON. On another dashboard or device, paste the JSON or open the saved JSON file and choose Review template. The editor shows the current and incoming content before anything changes.

If the template refers to an F1 Sensor installation that does not exist in the current Home Assistant system, you must explicitly choose the replacement installation. Applying a template does not save the dashboard automatically and can be undone during the editing session.

You can add this card several times to one dashboard. Home Assistant controls where the cards sit; the F1 Sensor editor controls the content inside each card.

Choose the information you want

Use Add module to add content, then select the module to edit it. Select fields or columns, reorder them with the move buttons, and open Module options for relevant filters and presentation choices. Modules can be moved, duplicated, disabled or removed.

Content	Available modules
Planning	Overview, Schedule and Weather.
Session	Timing, Minisectors, Race Control, Tyres, Pit stops and Incidents.
Results	Results, Championship, Season progression and Historical archive.
Analysis	Lap history chart, Session timeline, Strategy analysis, Battles and position changes, and Track map.
Watching later	Replay and Replay telemetry.
Officials	FIA documents.

Data availability depends on the source and session. Adding a module does not create missing observations, enable integration features or guarantee access to every live stream. See F1TV access and data coverage, historical results and weekend analysis.

Timing can follow a session profile or use your selected columns. Choosing your own timing columns keeps them as a custom selection. A module pinned to a driver keeps that driver when you change the card's general focus.

Show minisectors

Minisectors show the status published for each small segment of S1, S2 and S3. The source does not publish a time for each minisector, so the card does not calculate or estimate one.

Choose the presentation that fits each module:

Presentation	Fields to select
Sector time only	S1, S2 and S3 in Timing.
Sector time with status blocks	S1 with minisectors, S2 with minisectors and S3 with minisectors.
Status blocks only	S1 minisectors, S2 minisectors and S3 minisectors, either in Timing or in a separate Minisectors module.

These are ordinary optional fields. You can reorder them, combine them with other fields and configure each Timing or Minisectors module independently. The separate Minisectors module starts with Driver and the three status strips. No existing Timing profile adds minisectors automatically.

Status strips are available for live and replay practice, qualifying, sprint qualifying, sprint and race sessions when the source has supplied segment data. Different circuits can have different numbers of blocks. Before the first segment frame, or when a selected archive has no segment data, the module follows its When data is unavailable setting. Ordinary sector timing remains available when only minisector data is unavailable.

Set Recent lap columns under the Timing module's Module options to compare the latest 1–30 completed laps directly in the timing table. The default value is 0, which keeps these columns hidden. Each column is labelled with its lap number; a dash means that no usable time is available for that driver and lap.

Compare driver details

Open Driver details in a Timing module to choose information that appears when you select a driver. These choices are independent of Content and columns. The initial detail fields are Best lap, Tyre age and Status. You can choose other Timing fields, including S1, S2 and S3 minisectors, without adding them to the table. Minisector data is requested only while a selected driver needs it.

Select a driver to expand a detail row directly beneath that driver in the Timing table. You can open several drivers at once, and each driver's details stay attached to their row as the order changes. Select a driver again to close that row, or use Close all driver details above the table. Your selection is temporary and belongs to this Timing module. It does not change the card's driver focus. Changing session or replay context clears the selection.

Fields already shown as table columns are omitted from the detail panels. Recent laps in driver details can include older completed laps without repeating the laps already shown as table columns. If the chosen detail fields and laps add nothing to the table, the driver names are not opening controls. Clear Show driver details to disable them explicitly. Missing values remain missing; the card does not estimate minisector times.

Use Show text below times to hide the lap number, qualifying part and other supporting text below timing values. Use Show time status icon to hide the arrow, dot or square in a timing value. These choices apply independently to Last lap, Best lap, sector times, combined sector and minisector fields, qualifying times and lap comparisons in that Timing module.

Weather, Battles, Strategy and Replay telemetry show a collapsible About section by default. To remove it from one module, open that module's Module options and clear Show About section. Warnings, errors and controls remain visible.

Season progression uses each driver's or team's established Formula 1 color when Team accents is enabled. Select a name in the legend or select its line in the chart to hide that series; select the crossed-out legend name to show it again. The data table follows the visible series. This filter is temporary and does not change the saved card configuration; hiding the legend shows every series again.

Drag modules into place

Open Modules → Arrange modules in the card editor. The layout overview shows each module as a named tile. Choose Module layout → Columns and Columns in layout for a layout with two, three or four columns.

• Drag the dotted handle to move a module. A dashed outline shows where it will land, and the other tiles move to show the resulting order.
• In Columns, drag the arrow handle at a tile's lower right edge to change its width. Widths snap to whole columns; following modules wrap to the next row when needed.
• Select a tile and use Width of selected module → Full card width to keep that module across the entire row, even when the column count changes.
• Use Undo to reverse a completed drag. Press Escape to cancel a drag, or release a move outside the overview to leave the order unchanged.

You can also use the existing move buttons and width choices. With a handle focused, arrow keys move or resize the module; Home and End select the first/last position or smallest/largest width. Stacked modules and tabs support reordering, while width handles are available in Columns.

On small screens, scroll the overview sideways to reach all columns. Drag only from a handle; the rest of the overview supports normal touch scrolling. Hidden and conditional modules remain available in the overview, while the finished card respects their visibility rules. Tile heights in the overview are illustrative; module heights on the dashboard follow their content.

The overview changes module order and width within the card. It does not store fixed row positions or intentional empty cells. Save the card in Home Assistant to keep the arrangement on your dashboard.

Arrange modules in columns

Choose Columns under Card settings → Layout and shared focus → Layout to place modules beside each other inside one card. Set Maximum columns to 2, 3 or 4, then select each module and set its Module width to 1–4 columns or Full card width.

For example, use three columns with Timing at 2 columns, Track map at 1 column, and Race Control at Full card width. Timing and Track map share the first row; Race Control fills the row below them.

Modules follow the order in the module list, from left to right and then onto the next row. If a module does not fit in the remaining space, it starts on the next row. Later modules do not move ahead to fill earlier gaps. Hidden modules do not reserve a column.

Give the card enough space

1. In Home Assistant's Sections view settings, allow enough sections across the dashboard.
2. Edit the section containing the card and increase its width to 2, 3 or 4 section columns.
3. In the card's Home Assistant Layout tab, enable Full width card.
4. In the F1 Sensor editor, choose the module column count and widths.

Home Assistant controls the outer card width. Maximum columns only arranges content inside the available space; it does not enlarge the dashboard section. See Home Assistant card sizing.

The card uses fewer columns when space is limited and stacks modules on narrow cards. A module's width is limited to the columns that fit; Full card width always fills a row. Your saved widths return when the card becomes wider. Switching to Stacked modules or Tabs also keeps those width choices.

Use Arrange modules to set the order and widths. Home Assistant limits the width of its built-in preview, so a multi-column card may appear stacked there. Check the final layout on the dashboard at its actual width. A single section remains a narrow card even on a wide desktop screen.

Optional YAML example

type: custom:f1-sensor-card
layout: columns
columns: 3
grid_options:
  columns: full
modules:
  - type: timing
    column_span: 2
  - type: map
    column_span: 1
  - type: race_control
    column_span: full

Place this card in a section wide enough for three columns. The containing section's width is configured separately in Home Assistant.

Choose and lock a session

Open Layout and shared focus to choose whether the card follows the automatic source, the live session or the loaded replay. When the integration exposes a complete stable identity, the editor also offers Pin current live session or Pin loaded replay. An Archive module can pin the event and session selected from its historical catalogue.

A module can inherit the card, follow a source independently or keep its own pinned session. Module selection has priority over a card lock; a locked card has priority over a temporary group selection. If a saved identity is not available, the card keeps it and explains the mismatch. It never silently shows the current session instead. Pinning a replay does not load or start it, and pinning live data does not start another live source.

Under Module options, use Show in session phases to choose Before, Active or interrupted, Finished and Unknown. A module hidden by the current phase remains saved in the editor. Red-flag and other non-final interruptions count as active; only an explicit end state counts as finished.

Show modules conditionally

Open a module's Visibility conditions to show it only when the current Home Assistant state matches your choices. You can add conditions for an entity state, a numeric value, screen size, user, location or time. You can also group conditions with All conditions (AND), Any condition (OR) or Invert conditions (NOT).

Every condition at the top level must match. These conditions are combined with the module's selected session phases. The editor shows Visible now, Hidden now or Always visible, while the saved module remains available for editing. Hidden modules are removed from stacked content, column layouts and the card's tab list.

For example, you can show Timing only when a helper is on and the dashboard is open on a tablet or desktop:

type: custom:f1-sensor-card
version: 3
modules:
  - type: timing
    visibility:
      - condition: state
        entity: input_boolean.show_f1_timing
        state: "on"
      - condition: screen
        media_query: "(min-width: 768px)"

Use Home Assistant's card-level Visibility tab when you want to hide the entire F1 Sensor card. Module visibility controls only the content inside the card. If every module is hidden, a Sections dashboard may still reserve the card's configured grid area.

info

Visibility changes presentation, not permissions. A user who has access to an entity in Home Assistant may still access it even when a module is hidden.

Make the card your own

Open Appearance to choose a style, light/dark behavior and information density. F1, Home Assistant and Minimal use the same content and filters.

For a simple card, choose a preset and adjust only the style and density. The additional groups let you change titles, surfaces, accents, logos, flags, team colors, typography and tyre presentation. A neutral or team accent changes decoration; timing status has its own color settings.

Open Custom CSS (advanced) when the normal appearance controls do not cover your layout. The CSS applies only to that card and has a live preview. Use the documented variables and public parts in custom CSS styling instead of relying on private class names.

Module titles and table headers have separate visibility options under Module appearance. Hidden headings and column labels remain available to assistive technology. Chart data tables retain their labels.

The card-level driver menu uses three-letter driver codes to stay compact. Open Layout and shared focus and clear Show driver focus menu if you do not want the menu on that card. A saved default driver or module-level driver selection continues to apply when the menu is hidden.

:::tip Keep the important fields first Put the driver and the time or status you follow most near the start of a table. A small number of useful columns is easier to read on a phone than a full timing sheet. :::

Read timing colors and symbols

Open Accessibility and timing colors to adjust timing colors and the accompanying signals. Color is only one part of the meaning.

Signal	Meaning
Purple and diamond	Overall fastest.
Green and circle	Personal best.
Yellow and square	A recorded time. Yellow does not mean slower than the previous lap.
Neutral previous-lap value	The value belongs to the labelled earlier lap.
Down triangle with a negative lap delta	A faster lap than the stated reference lap.
Up triangle with a positive lap delta	A slower lap than the stated reference lap.
Position arrow	A position change against its stated comparison, not a change in lap time.

The default sector view keeps values from the same lap together. The Latest sectors, with lap labels option can mix the most recently supplied sectors; the individual lap labels matter in that view. A theoretical lap is the sum of personal-best sectors and may combine different laps.

The same purple diamond, green circle and yellow square are used for minisector status. Yellow means that the provider marked the segment as recorded without a personal or overall best status. It does not prove that the segment was slower than the driver's preceding lap. Reset, special, missing and unrecognized source statuses stay neutral instead of receiving an assumed meaning. Turn on the Minisectors module's status legend when you want the explanation beside the data.

Minisector status is short-lived dashboard data and can update several times per second across all drivers. It is delivered only while a visible modular card needs it and is not exposed as Home Assistant sensor state. This avoids filling Recorder or sending a complete timing grid for every small change. It also means minisector status is intended for the F1 Sensor card rather than entity-based automations.

Custom colors can help you distinguish the timing states. Keep symbols or text available and check both light and dark themes. High contrast, reduced motion and readable text alternatives are part of the card's controls; automated checks alone do not establish compatibility with every screen reader or device.

Track Map moves driver markers smoothly between consecutive live or replay positions. It moves directly to the new position when reduced motion is enabled, the session changes, the position is stale or the new sample is too far from the previous one to be a continuous movement.

See card accessibility for focused keyboard, contrast and motion guidance.

Times and saved data

Clock times follow your Home Assistant profile's Time format: 12-hour, 24-hour, language or system locale. This applies to schedules, Race Control messages, document publication times, map observations, calibration and frozen views. Your profile also controls the time zone, unless you explicitly choose circuit time for a schedule.

Cards keep the focus on the selected Formula 1 content. They do not show automatic update timestamps, elapsed update ages or provider credit lines. Event and session times remain available as content fields.

Under Module options, choose When data is unavailable:

Choice	Behavior
Show explanation	Replace unavailable content with an explanation and keep the saved configuration.
Keep saved data	Keep available saved content with a notice when updates are interrupted.
Hide module	Hide unavailable content until it can be shown again. The module stays in your configuration.

When the browser loses its Home Assistant connection, the card shows a clear disconnected notice. Retained values are saved snapshots. Replay, archive and telemetry controls show their own connection state. Spoiler protection still takes precedence over retained or frozen content.

Entity-backed modules can keep their last captured content when a source becomes unavailable, even if its attributes disappear. Filters continue to apply to that saved content. A different installation, session, replay seek, Live Delay or spoiler state clears these snapshots; they are also released when the card is removed or the page reloads. An available empty result replaces the saved result instead of reviving older rows.

Freeze view captures a reading snapshot in this card. Its values remain at the capture point, identified by the reading-snapshot notice. Resume returns to current data. Freezing does not pause backend replay, change Live Delay or change automations. The button is shown by default; clear Show Freeze view button under Layout and shared focus if you do not want it on a card.

Live Delay, spoilers and replay

Under Layout and shared focus, enable Show Live Delay and global spoiler controls to add the optional Viewing settings panel.

• Manual Live Delay changes require Apply live delay. They affect the selected installation's live delivery and automations.
• Calibrate with TV guides you through choosing a reference, waiting and explicitly matching the moment on TV. Cancel keeps the existing delay. See Live Delay.
• Global spoiler protection affects all F1 Sensor installations. Turning it off includes a review. Local hiding cannot override it.
• Archive selections retrieve history. They do not load or start a replay.
• Replay actions control the selected installation's shared replay. Separate cards are not independent replay players.

Demo previews cannot issue integration actions. A saved card's local driver focus and reading snapshot also leave integration settings unchanged.

Save, reuse and migrate

Save permanent choices in the Home Assistant card editor. Export and import copies the complete card configuration as JSON; importing replaces the editor draft and can be undone before saving.

Converted deprecated configurations retain a recoverable original and show differences for review. Treat conversion as a reviewed starting point and keep a dashboard backup until the new card covers the behavior you use.

Follow the migration guide to convert one card at a time, interpret the review and restore the exact stored deprecated configuration when needed.

Shared driver focus is scoped to the configured group within the same dashboard view and F1 installation. You can also explicitly share temporary session selection; pinned cards keep their own session, and the group cannot operate replay, Live Delay or automations. Temporary group changes are local to that browser connection; they are not synchronized personal preferences across devices.