Skip to main content

Race Control Notifications

Get instant notifications whenever the race director sends a message — flag changes, safety car deployments, penalties, incident reports, and more.

This blueprint listens to the Race Control sensor and forwards messages to any notification service you choose. All filtering is optional, so you can start simple and refine over time.

Sync with your TV

For notifications to arrive at the right moment, configure the Live Delay to match your broadcast offset.


Import the Blueprint

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

Or go to Settings > Automations & Scenes > Blueprints and import manually using the URL:

https://raw.githubusercontent.com/Nicxe/f1_sensor/main/blueprints/f1_officials_race_control_notifications.yaml

Requirements

  • F1 Sensor integration installed and configured with live data enabled
  • At least one notification service available in Home Assistant (mobile app, persistent notification, TTS, etc.)

Step-by-step Setup

Step 1 — Create an automation from the blueprint

  1. Go to Settings > Automations & Scenes > Blueprints
  2. Find F1 Sensor - Race Control Notifications
  3. Click Create Automation

Step 2 — Configure Source

SettingDescription
Race Control SensorSelect the *_race_control sensor from your F1 Sensor integration
Require Active Session PhaseEnable this to only receive notifications during specific session phases
Session Status SensorRequired if you enable phase filtering — select the *_session_status sensor
Active Session PhasesWhich phases should trigger notifications. Defaults to live and suspended
info

The Session Status Sensor is only needed when Require Active Session Phase is turned on. If you leave it off, notifications arrive for all messages regardless of session state.


Step 3 — Session Scope (Optional)

Limit notifications to specific session types. This is useful if you only want to receive race control messages during the Race and Qualifying sessions, while ignoring Practice sessions.

SettingDescription
Enable Current Session FilterWhen enabled, notifications are only sent during the selected session types. Disabled by default
Current Session SensorSelect the *_current_session sensor. Required when the filter is enabled
Allowed Current SessionsWhich session types should send notifications. Defaults to all sessions
info

When this filter is enabled, the automation checks the Current Session sensor to decide whether to send a notification. If the current session is not in the allowed list, the notification is suppressed regardless of other filter settings.


Step 4 — Configure Filters (Optional)

All filters are optional and collapsed by default. Leave them empty to receive every race control message.

SettingDescription
Allowed FlagsOnly notify for specific flag types. Leave empty to allow all flags
Allowed CategoriesComma or semicolon-separated category names. Leave empty to allow all categories
Include KeywordsOnly notify when the message contains at least one of these words
Exclude KeywordsSkip notifications when the message contains any of these words

Available flag values:

FlagWhen it appears
CLEARTrack is clear, normal racing conditions
GREENSession start or restart
YELLOWYellow flag, caution on track
DOUBLE YELLOWDouble yellow, significant hazard
VSCVirtual Safety Car deployed
SCSafety Car deployed
REDRed flag, session stopped
BLUEBlue flag shown to a driver being lapped
WHITESlow vehicle on track
BLACKDriver disqualified
CHEQUEREDSession finished

Step 5 — Configure Notifications

SettingDescription
Title PrefixText prepended to the notification title. Defaults to F1 Race Control
Include Fields in MessageExtra details added below the main message text
Cooldown (seconds)Pause between notifications to reduce alert spam. Defaults to 0 (no cooldown)
Notification ActionsAdd one or more Home Assistant actions for delivery

Available fields for the message body:

FieldWhat it contains
CategoryThe type of race control event
FlagThe flag associated with the message
ScopeTrack-wide or specific sector/car
SectorWhich sector is affected (if applicable)
Car numberThe car number if the message targets a specific driver
UTCTimestamp of the message
Event IDInternal event identifier
Session phaseCurrent session phase at the time of the message

Step 6 — Add a Notification Action

In the Notification Actions field, add your delivery action. Below are examples for the most common services.

Mobile app notification:

- service: notify.mobile_app_your_phone
data:
title: "{{ notification_title }}"
message: "{{ notification_message }}"

Persistent notification (visible in Home Assistant UI):

- service: persistent_notification.create
data:
title: "{{ notification_title }}"
message: "{{ notification_message }}"

Text-to-speech:

- service: tts.speak
target:
entity_id: tts.home_assistant_cloud
data:
message: "{{ race_control_message }}"
media_player_entity_id: media_player.living_room

Template Variables

The following variables are available inside your notification actions:

VariableDescription
{{ notification_title }}Ready-to-use title combining prefix and flag
{{ notification_message }}Ready-to-use message with selected fields
{{ race_control_message }}The raw race control message text
{{ race_control_category }}Event category
{{ race_control_flag }}Flag type
{{ race_control_scope }}Scope (track, sector, car)
{{ race_control_sector }}Affected sector
{{ race_control_car_number }}Car number if applicable
{{ race_control_utc }}UTC timestamp
{{ race_control_event_id }}Event ID
{{ race_control_session_phase }}Current session phase

Example Configurations

Notify only for safety car and red flag

Set Allowed Flags to SC, VSC, and RED. Leave all other filters empty.


Notify only during the race

Enable Require Active Session Phase and set Active Session Phases to live and suspended only.


Exclude administrative messages

Set Exclude Keywords to clerk, official, document to filter out FIA document references.