### Configure Scheduled Flight Takeoff Notification Automation

Source: https://github.com/alexandrerohin/home-assistant-flightradar24/blob/main/README.md

Use this automation in your configuration.yaml to get notified when a tracked scheduled flight takes off. Remember to substitute `<device_name>` with your device's name.

```yaml
automation:
  - alias: "Scheduled flight takes off"
    trigger:
      platform: event
      event_type: flightradar24_tracked_took_off
    action:
      service: notify.mobile_app_<device_name>
      data:
        message: >-
          Flight takes off {{ trigger.event.data.callsign }} to {{ trigger.event.data.airport_destination_city }}
          [Open FlightRadar](https://www.flightradar24.com/{{ trigger.event.data.callsign }})
        data:
          url: >-
            https://fr24.com/{{ trigger.event.data.callsign }}/{{
            trigger.event.data.id }}
          clickAction: >-
            https://fr24.com/{{ trigger.event.data.callsign }}/{{
            trigger.event.data.id }}
          image: "{{ trigger.event.data.aircraft_photo_medium }}"
```

--------------------------------

### Initial Configuration Flow Data

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Represents the data collected during the initial setup of the Flightradar24 integration, including geographic center, radius, and polling interval. Optional username and password can be provided for subscription-only data.

```python
# Equivalent programmatic representation of config_flow.async_step_user data
config_entry_data = {
    "latitude": 48.8566,       # Center latitude (defaults to HA home location)
    "longitude": 2.3522,       # Center longitude
    "radius": 1000,            # Bounding radius in meters (default 1000)
    "scan_interval": 10,       # Poll frequency in seconds (default 10)
    # Optional – subscription only:
    "username": "user@example.com",
    "password": "s3cr3t",
}

# In async_setup_entry, HA builds the bounding box and creates the coordinator:
# bounds = client.get_bounds_by_point(latitude, longitude, radius)
# coordinator = FlightRadar24Coordinator(hass, bounds, client, scan_interval, ...)
```

--------------------------------

### Configuration Options Schema

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Defines the full schema for configuring existing Flightradar24 integration entries, including advanced options like altitude limits and enabling the device tracker. These options can be modified after initial setup.

```python
# Full options schema (FlightRadarOptionsFlow.async_step_init)
options = {
    "latitude": 48.8566,
    "longitude": 2.3522,
    "radius": 1500,
    "scan_interval": 15,
    "min_altitude": 0,          # Minimum altitude to track, in feet (default -1 = all)
    "max_altitude": 40000,      # Maximum altitude to track, in feet (default 100000)
    "most_tracked": True,       # Enable "Most Tracked" sensor (top-10 on FR24, default True)
    "enable_tracker": False,    # Enable device_tracker entity for live tracked flight (default False)
    "username": "",
    "password": "",
}
```

--------------------------------

### Set Monitored Airport

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Starts or stops receiving airport schedule and statistics data for a specific airport. Use the IATA or ICAO code to track an airport, or an empty string to stop.

```yaml
# Start tracking Paris CDG
service: text.set_value
target:
  entity_id: text.flightradar24_airport_track
data:
  value: "CDG"
```

```yaml
# Stop tracking
service: text.set_value
target:
  entity_id: text.flightradar24_airport_track
data:
  value: ""
```

--------------------------------

### Display Current Flights in Area (Lovelace)

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Example Lovelace markdown card to display a list of flights currently within the monitored area. It iterates through the 'flights' attribute of the 'sensor.flightradar24_current_in_area' sensor.

```yaml
# Example Lovelace markdown card showing current in-area flights
type: markdown
content: >-
  {% set flights = state_attr('sensor.flightradar24_current_in_area', 'flights') | default([], true) %}
  {% for f in flights %}
    ✈ {{ f.flight_number }} ({{ f.aircraft_registration }}) — {{ f.airline_short }}
    {{ f.airport_origin_city }} → {{ f.airport_destination_city }}
    Alt: {{ f.altitude }} ft  |  Speed: {{ f.ground_speed }} kts  |  Dist: {{ f.distance | round(1) }} km
  {% endfor %}
```

--------------------------------

### Notify on Flight Entry Automation

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

An example Home Assistant automation that triggers a notification when a new flight enters the monitored area. It uses the 'flightradar24_entry' event and extracts flight details from the event data.

```yaml
# Automation: notify when any flight enters the area
automation:
  alias: "Notify on flight entry"
  trigger:
    platform: event
    event_type: flightradar24_entry
  action:
    service: notify.mobile_app_my_phone
    data:
      title: "Flight entered area"
      message: >-
        {{ trigger.event.data.flight_number }} ({{ trigger.event.data.airline_short }})
        {{ trigger.event.data.airport_origin_city }} → {{ trigger.event.data.airport_destination_city }}
        Alt {{ trigger.event.data.altitude }} ft
      data:
        image: "{{ trigger.event.data.aircraft_photo_medium }}"
        url: "https://fr24.com/{{ trigger.event.data.callsign }}/{{ trigger.event.data.id }}"
```

--------------------------------

### Configure Flight Entry Notification Automation

Source: https://github.com/alexandrerohin/home-assistant-flightradar24/blob/main/README.md

Add this automation to your configuration.yaml to receive notifications when a flight enters your defined area. Ensure you replace `<device_name>` with your actual device name.

```yaml
automation:
  - alias: "Flight entry notification"
    trigger:
      platform: event
      event_type: flightradar24_entry
    action:
      service: notify.mobile_app_<device_name>
      data:
        message: >-
          Flight entry of {{ trigger.event.data.callsign }} to {{ trigger.event.data.airport_destination_city }}
          [Open FlightRadar](https://www.flightradar24.com/{{ trigger.event.data.callsign }})
        data:
          url: >-
            https://fr24.com/{{ trigger.event.data.callsign }}/{{
            trigger.event.data.id }}
          clickAction: >-
            https://fr24.com/{{ trigger.event.data.callsign }}/{{
            trigger.event.data.id }}
          image: "{{ trigger.event.data.aircraft_photo_medium }}"
```

--------------------------------

### Configure Automatic Flight Tracking Automation

Source: https://github.com/alexandrerohin/home-assistant-flightradar24/blob/main/README.md

Add this automation to your configuration.yaml to automatically add flights to additional tracking based on specific conditions. Modify the conditions to suit your tracking needs.

```yaml
automation:
  - alias: "Track flights"
    trigger:
      platform: event
      event_type: flightradar24_exit
    condition:
      - condition: template
        value_template: "{{ 'Frankfurt' == trigger.event.data.airport_origin_city }}"
    action:
      - service: text.set_value
        data:
          value: "{{ trigger.event.data.aircraft_registration }}"
        target:
          entity_id: text.flightradar24_add_to_track
```

--------------------------------

### Configure Last Flights History Sensor

Source: https://github.com/alexandrerohin/home-assistant-flightradar24/blob/main/README.md

Add this configuration to your `configuration.yaml` to create a sensor that tracks the last 5 flights exiting your area. It triggers on the `flightradar24_exit` event.

```yaml
template:
  - trigger:
      - platform: event
        event_type: flightradar24_exit

    sensor:
      - unique_id: flightradar24_last_5_flights
        name: "FlightRadar24 Last 5 Flights"
        state: >-
          {% set flight = trigger.event.data %}
          {{ flight.flight_number }} - {{ flight.airline_short }} - {{ flight.aircraft_model }} ({{ flight.aircraft_registration }})
          {{ flight.airport_origin_city }} > {{ flight.airport_destination_city }}
        attributes:
          flights: >-
            {% set n = 5 %}
            {% set m = this.attributes.flights | count | default(0) %}
            {{ [ trigger.event.data ] + 
               ( [] if m == 0 else 
                 this.attributes.flights[0:n-1] )
            }}
          icon: mdi:airplane
```

--------------------------------

### device_tracker.flightradar24

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Creates a GPS-based device tracker that follows the first live flight in the 'Additional Tracked' list when enabled. It updates in real-time with the aircraft's location and exposes flight attributes as state attributes.

```APIDOC
## device_tracker.flightradar24

### Description
Provides a GPS-based device tracker for the first live flight in the 'Additional Tracked' list. Location and flight attributes are updated in real-time.

### Configuration
Requires `enable_tracker: true` in the integration options.

### Usage
Can be used in `person` entities or templates to access flight data.

### Example Attributes
- `flight_number` (string)
- `altitude` (string)
- `ground_speed` (string)
```

--------------------------------

### Lovelace Map Card with Live Flight Overlay

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

This Lovelace configuration displays live flight data on a map. It includes an entities card to show the number of flights overhead and a conditional markdown card to list details of live flights. An iframe card embeds an external ADS-B map for visual tracking. Ensure you replace the placeholder LAT/LON with your specific coordinates.

```yaml
type: vertical-stack
title: Live Air Traffic
cards:
  - type: entities
    entities:
      - entity: sensor.flightradar24_current_in_area
        name: Flights overhead
  - type: conditional
    conditions:
      - condition: numeric_state
        entity: sensor.flightradar24_current_in_area
        above: 0
    card:
      type: markdown
      content: >-
        {% set flights = state_attr('sensor.flightradar24_current_in_area', 'flights') | default([], true) %}
        {% for f in flights %}{% if (f.tracked_type | default('live')) == 'live' %}
        **{{ f.flight_number }}** — {{ f.airline_short }} — {{ f.aircraft_model }}
        {{ f.airport_origin_city }}{% if f.airport_origin_country_code %} 🏳 {{ f.airport_origin_country_code }}{% endif %} → {{ f.airport_destination_city }}{% if f.airport_destination_country_code %} 🏳 {{ f.airport_destination_country_code }}{% endif %}
        Alt: {{ f.altitude }} ft ({{ (f.altitude * 0.3048) | round(0) }} m) · Speed: {{ f.ground_speed }} kts
        {% endif %}{% endfor %}
  - type: iframe
    # Replace LAT/LON with your coordinates
    url: "https://globe.adsb.fi/?enableLabels&trackLabels&zoom=11&hideSideBar&lat=48.8566&lon=2.3522"
    aspect_ratio: 75%
```

--------------------------------

### Device Tracker Usage

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Enables a GPS-based device tracker that follows the first live flight in the 'Additional Tracked' list. Location updates in real-time, and flight attributes are exposed as state attributes.

```yaml
# Enable the device tracker in options first, then use it in a person entity
person:
  - name: "My Flight"
    id: my_flight
    device_trackers:
      - device_tracker.flightradar24

# Read tracker attributes in a template
{{ state_attr('device_tracker.flightradar24', 'flight_number') }}
{{ state_attr('device_tracker.flightradar24', 'altitude') }} ft
{{ state_attr('device_tracker.flightradar24', 'ground_speed') }} kts
```

--------------------------------

### Lovelace Airport Card Configuration

Source: https://github.com/alexandrerohin/home-assistant-flightradar24/blob/main/README.md

Use this configuration to add a card to your Home Assistant dashboard that displays airport arrivals and departures. It requires the `sensor.flightradar24_airport_arrivals` and `sensor.flightradar24_airport_departures` entities.

```yaml
type: vertical-stack
title: Flightradar24
cards:
  - type: entities
    entities:
      - entity: sensor.flightradar24_airport_arrivals_canceled
        name: Arrivals canceled
      - entity: sensor.flightradar24_airport_arrivals_delayed
        name: Arrivals delayed
      - entity: sensor.flightradar24_airport_arrivals_on_time
        name: Arrivals on time
  - type: markdown
    title: Arrivals
    content: >
      {% set flights = 
      state_attr('sensor.flightradar24_airport_arrivals','flights') | 
      default([], true) %}
        | TIME | FROM | FLIGHT | REMARK |
        | ---- | ---- | ------ | ------ | {% for f in flights %} 
        | {{ f.time_scheduled_arrival | timestamp_custom('%H:%M') if f.time_scheduled_departure else '--:--' }} | {{ f.airport_city |  default('---', true) }} | {{ f.flight_number |  default('---', true) }} | {{ f.status_text |  default('---', true) }} | {% endfor %}
  - type: entities
    entities:
      - entity: sensor.flightradar24_airport_departures_canceled
        name: Departures canceled
      - entity: sensor.flightradar24_airport_departures_delayed
        name: Departures delayed
      - entity: sensor.flightradar24_airport_departures_on_time
        name: Departures on time
  - type: markdown
    title: Departures
    content: >
      {% set flights = state_attr('sensor.flightradar24_airport_departures',
      'flights') |  default([], true) %}
        | TIME | TO | FLIGHT | REMARK |
        | ---- | ---- | ------ | ------ | {% for f in flights %} 
        | {{ f.time_scheduled_departure | timestamp_custom('%H:%M') if f.time_scheduled_departure else '--:--' }} | {{ f.airport_city |  default('---', true) }} | {{ f.flight_number |  default('---', true) }} | {{ f.status_text |  default('---', true) }} |{% endfor %}
```

--------------------------------

### Lovelace Card for Airport Arrivals Board

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Displays a detailed arrivals board for a specific airport (e.g., CDG), showing on-time, delayed, and canceled flights. It lists the scheduled arrival time, origin, flight number, and status for up to 50 flights.

```yaml
# Arrivals/departures board Lovelace card
type: vertical-stack
title: CDG Airport
cards:
  - type: entities
    entities:
      - entity: sensor.flightradar24_airport_arrivals_on_time
        name: On time
      - entity: sensor.flightradar24_airport_arrivals_delayed
        name: Delayed
      - entity: sensor.flightradar24_airport_arrivals_canceled
        name: Canceled
  - type: markdown
    title: Arrivals (next 50)
    content: >-
      {% set flights = state_attr('sensor.flightradar24_airport_arrivals', 'flights') | default([], true) %}
      | Time | From | Flight | Status |
      |------|------|--------|--------|
      {% for f in flights %}
      | {{ f.time_scheduled_arrival | timestamp_custom('%H:%M') if f.time_scheduled_arrival else '--:--' }} | {{ f.airport_city | default('---') }} | {{ f.flight_number | default('---') }} | {{ f.status_text | default('---') }} |
      {% endfor %}
```

--------------------------------

### Exclude Flightradar24 Sensors from Recorder

Source: https://github.com/alexandrerohin/home-assistant-flightradar24/blob/main/README.md

Add this configuration to your `configuration.yaml` file to prevent Flightradar24 sensor data from being stored in the Home Assistant Recorder database, which helps reduce database size.

```yaml
recorder:
  exclude:
    entity_globs:
      - sensor.flightradar24*
```

--------------------------------

### switch.flightradar24_api_data_fetching

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Enables or disables all FlightRadar24 API calls. This is useful for conserving bandwidth when flight tracking is not actively needed.

```APIDOC
## switch.flightradar24_api_data_fetching

### Description
Enables or disables all FlightRadar24 API calls to save bandwidth.

### Method
`switch.turn_on` or `switch.turn_off`

### Endpoint
`switch.flightradar24_api_data_fetching`
```

--------------------------------

### Exclude FlightRadar24 Entities from Recorder

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Configure Home Assistant's Recorder to exclude high-frequency FlightRadar24 entities to reduce database size. Add this configuration to your configuration.yaml file.

```yaml
# configuration.yaml
recorder:
  exclude:
    entity_globs:
      - sensor.flightradar24*

```

--------------------------------

### Flight Data Schema

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

This dictionary represents the structure of flight data, including identification, position, aircraft, airline, airport, and time information. It is exposed by the 'flights' sensor attribute and 'trigger.event.data'.

```python
flight = {
    # Identification
    "id": "2babe3b0",
    "flight_number": "LH400",
    "callsign": "DLH400",
    "aircraft_registration": "D-AIHA",
    "tracked_type": "live",          # "live" | "schedule" | "not_found" (tracked flights only)
    "tracked_by_device": "FlightRadar24",  # device name (events only)

    # Position & dynamics (updated every poll)
    "latitude": 48.9012,
    "longitude": 2.4521,
    "altitude": 3500,                # feet
    "heading": 275,                  # degrees
    "ground_speed": 210,             # knots
    "vertical_speed": -800,
    "on_ground": 0,                  # 0 = airborne, 1 = on ground
    "squawk": "1000",                # subscription only
    "distance": 12.4,               # km from your configured point
    "closest_distance": 8.1,        # closest distance reached while tracking (km)

    # Aircraft
    "aircraft_model": "Airbus A350-900",
    "aircraft_code": "A359",
    "aircraft_photo_small": "https://cdn.flightradar24.com/..._t.jpg",
    "aircraft_photo_medium": "https://cdn.flightradar24.com/..._m.jpg",
    "aircraft_photo_large": "https://cdn.flightradar24.com/..._l.jpg",

    # Airline
    "airline": "Lufthansa",
    "airline_short": "Lufthansa",
    "airline_iata": "LH",
    "airline_icao": "DLH",

    # Origin airport
    "airport_origin_name": "Frankfurt Airport",
    "airport_origin_code_iata": "FRA",
    "airport_origin_code_icao": "EDDF",
    "airport_origin_country_name": "Germany",
    "airport_origin_country_code": "DE",
    "airport_origin_city": "Frankfurt",
    "airport_origin_timezone_offset": 3600,
    "airport_origin_timezone_abbr": "CET",
    "airport_origin_terminal": "1",
    "airport_origin_latitude": 50.0264,
    "airport_origin_longitude": 8.5431,

    # Destination airport
    "airport_destination_name": "John F. Kennedy International Airport",
    "airport_destination_code_iata": "JFK",
    "airport_destination_code_icao": "KJFK",
    "airport_destination_country_name": "United States",
    "airport_destination_country_code": "US",
    "airport_destination_city": "New York",
    "airport_destination_timezone_offset": -18000,
    "airport_destination_timezone_abbr": "EST",
    "airport_destination_terminal": "1",
    "airport_destination_latitude": 40.6413,
    "airport_destination_longitude": -73.7781,

    # Times (Unix timestamps)
    "time_scheduled_departure": 1700000000,
    "time_scheduled_arrival":   1700030000,
    "time_real_departure":      1700000300,
    "time_real_arrival":        None,
    "time_estimated_departure": None,
    "time_estimated_arrival":   1700028000,
}

```

--------------------------------

### Template Sensor for Last 5 Exited Flights

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

This template sensor captures the last 5 flights that triggered the flightradar24_exit event. It stores the flight number and aircraft model in the state and a list of flight data in the attributes.

```yaml
template:
  - trigger:
      - platform: event
        event_type: flightradar24_exit
    sensor:
      - unique_id: flightradar24_last_5_exits
        name: "FR24 Last 5 Exits"
        state: >-
          {{ trigger.event.data.flight_number }} — {{ trigger.event.data.aircraft_model }}
        attributes:
          flights: >-
            {% set n = 5 %}
            {% set prev = this.attributes.flights | default([], true) %}
            {{ [trigger.event.data] + prev[0:n-1] }}
          icon: mdi:airplane-remove
```

--------------------------------

### Lovelace Card for Flightradar24 Map

Source: https://github.com/alexandrerohin/home-assistant-flightradar24/blob/main/README.md

Add this markdown to a Manual Lovelace card to display live flight data on a map. Replace LATITUDE and LONGITUDE with your desired coordinates. The card shows current flights in the area and provides a link to a detailed map.

```yaml
type: vertical-stack
title: Flightradar24
cards:
  - type: entities
    entities:
      - entity: sensor.flightradar24_current_in_area
        name: In area
  - type: conditional
    conditions:
      - condition: numeric_state
        entity: sensor.flightradar24_current_in_area
        above: 0
    card:
      type: markdown
      content: >-
        {% set data = state_attr('sensor.flightradar24_current_in_area',
        'flights') | default([], true) %} {% for flight in data %} 
          <ha-icon icon="mdi:airplane"></ha-icon>{{ flight.flight_number }}({{ flight.aircraft_registration }}) - {{ flight.airline_short }} - {{ flight.aircraft_model }}
          {{ flight.airport_origin_city }}{%if flight.airport_origin_city %}<img src="https://flagsapi.com/{{ flight.airport_origin_country_code }}/shiny/16.png" title='{{ flight.airport_origin_country_name }}'/>{% endif %} -> {{ flight.airport_destination_city }}{% 
          if flight.airport_destination_country_code %}<img src="https://flagsapi.com/{{ flight.airport_destination_country_code }}/shiny/16.png" title='{{ flight.airport_destination_country_name }}'/>{% endif %}
          {%if flight.time_scheduled_departure %}Departure - {{ flight.time_scheduled_departure | timestamp_custom('%H:%M') }}; {% endif %}{%if flight.time_scheduled_arrival%}Arrival - {{ flight.time_scheduled_arrival | timestamp_custom('%H:%M') }}{% endif %}
          Altitude - {{ flight.altitude }} ft{%if flight.altitude > 0 %} ({{(flight.altitude * 0.3048)| round(0)}} m){% endif%}; Gr. speed - {{ flight.ground_speed }} kts{%if flight.ground_speed > 0 %} ({{(flight.ground_speed * 1.852)| round(0)}} km/h){% endif%}
          {% endfor %}
  - type: iframe
    url: >-
      https://globe.adsb.fi/?enableLabels&trackLabels&zoom=12&hideSideBar&lat=LATITUDE&lon=LONGITUDE
    aspect_ratio: 100%
```

--------------------------------

### Lovelace Card for Top-10 Most Tracked Flights

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Presents a markdown table of the top 10 most tracked flights globally from Flightradar24, including their route and current watcher count. This requires enabling the `most_tracked` option.

```yaml
# Template to list top-10 most tracked with click counts
type: markdown
content: >-
  {% set flights = state_attr('sensor.flightradar24_most_tracked', 'flights') | default([], true) %}
  | # | Flight | Route | Watchers |
  |---|--------|-------|---------|
  {% for f in flights %}
  | {{ loop.index }} | {{ f.flight_number }} | {{ f.airport_origin_city }} → {{ f.airport_destination_city }} | {{ f.clicks }} |
  {% endfor %}
```

--------------------------------

### button.flightradar24_clear_additional_tracked

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Clears all flights currently being tracked in the 'Additional tracked' sensor with a single press.

```APIDOC
## button.flightradar24_clear_additional_tracked

### Description
Clears all flights from the `Additional tracked` sensor.

### Method
`button.press`

### Endpoint
`button.flightradar24_clear_additional_tracked`
```

--------------------------------

### Add FlightRadar24 Card to Lovelace Dashboard

Source: https://github.com/alexandrerohin/home-assistant-flightradar24/blob/main/README.md

Use this markdown code to add a flight table to your Home Assistant dashboard. It displays flights in the area and can be customized.

```yaml
type: vertical-stack
title: Flightradar24
cards:
  - type: entities
    entities:
      - entity: sensor.flightradar24_current_in_area
        name: In area
  - type: conditional
    conditions:
      - condition: numeric_state
        entity: sensor.flightradar24_current_in_area
        above: 0
    card:
      type: markdown
      content: >-
        {% set data = state_attr('sensor.flightradar24_current_in_area',
        'flights') | default([], true) %} {% for flight in data %}{% if (flight.tracked_type | default('live')) == 'live' %}
          <ha-icon icon="mdi:airplane"></ha-icon>{{ flight.flight_number }} - {{ flight.airline_short }} - {{ flight.aircraft_model }}
          {{ flight.airport_origin_city }}{%if flight.airport_origin_city %}<img src="https://flagsapi.com/{{ flight.airport_origin_country_code }}/shiny/16.png" title='{{ flight.airport_origin_country_name }}'/>{% endif %} -> {{ flight.airport_destination_city }}{% 
          if flight.airport_destination_country_code %}<img src="https://flagsapi.com/{{ flight.airport_destination_country_code }}/shiny/16.png" title='{{ flight.airport_destination_country_name }}'/>{% endif %}
          {%if flight.time_scheduled_departure %}Departure - {{ flight.time_scheduled_departure | timestamp_custom('%H:%M') }}; {% endif %}{%if flight.time_scheduled_arrival%}Arrival - {{ flight.time_scheduled_arrival | timestamp_custom('%H:%M') }}{% endif %}
          Altitude - {{ flight.altitude }} ft{%if flight.altitude > 0 %} ({{(flight.altitude * 0.3048)| round(0)}} m){% endif%}; Gr. speed - {{ flight.ground_speed }} kts{%if flight.ground_speed > 0 %} ({{(flight.ground_speed * 1.852)| round(0)}} km/h){% endif%}
          {% else%}
          <ha-icon icon="mdi:airplane"></ha-icon>{{ flight.flight_number }} - {{ flight.callsign }} - {{ flight.tracked_type }}
          {% endif%}{% endfor %}
```

--------------------------------

### Auto-track FRA departures

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Triggers an automation when a flight exits the monitored area, specifically if it originated from Frankfurt. It then adds the aircraft's registration to be tracked.

```yaml
automation:
  alias: "Auto-track FRA departures"
  trigger:
    platform: event
    event_type: flightradar24_exit
  condition:
    - condition: template
      value_template: "{{ trigger.event.data.airport_origin_city == 'Frankfurt' }}"
  action:
    - service: text.set_value
      target:
        entity_id: text.flightradar24_add_to_track
      data:
        value: "{{ trigger.event.data.aircraft_registration }}"
```

--------------------------------

### Tracked flight took off notification

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Sends a notification when a flight in the 'Additional Tracked' list takes off. The notification includes flight details and a link to FlightRadar24.

```yaml
# Notification: alert when a tracked scheduled flight takes off
automation:
  alias: "Tracked flight took off"
  trigger:
    platform: event
    event_type: flightradar24_tracked_took_off
  action:
    service: notify.mobile_app_my_phone
    data:
      title: "Flight departed!"
      message: >-
        {{ trigger.event.data.flight_number }} took off from {{ trigger.event.data.airport_origin_city }}
        heading to {{ trigger.event.data.airport_destination_city }}.
        ETA: {{ trigger.event.data.time_estimated_arrival | timestamp_custom('%H:%M') }}
      data:
        image: "{{ trigger.event.data.aircraft_photo_medium }}"
        url: "https://fr24.com/{{ trigger.event.data.callsign }}/{{ trigger.event.data.id }}"
```

--------------------------------

### Lovelace Card for Additional Tracked Flights

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Displays a list of flights that have been explicitly added for tracking using the `sensor.flightradar24_additional_tracked` entity. It shows flight number, type, route, and scheduled arrival time.

```yaml
# Lovelace card for additional tracked flights
type: markdown
content: >-
  {% set flights = state_attr('sensor.flightradar24_additional_tracked', 'flights') | default([], true) %}
  {% for f in flights %}
    ✈ {{ f.flight_number }} [{{ f.tracked_type }}]
    {{ f.airport_origin_city | default('?') }} → {{ f.airport_destination_city | default('?') }}
    {% if f.time_scheduled_arrival %}
      ETA: {{ f.time_scheduled_arrival | timestamp_custom('%H:%M') }}
    {% endif %}
  {% endfor %}
```

--------------------------------

### text.flightradar24_add_to_track

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Adds a flight to be tracked by its aircraft registration. This is often used within automations to dynamically track flights based on certain conditions.

```APIDOC
## text.flightradar24_add_to_track

### Description
Adds a flight to be tracked by its aircraft registration.

### Method
`text.set_value`

### Endpoint
`text.flightradar24_add_to_track`

### Parameters
#### Request Body
- **value** (string) - Required - The aircraft registration of the flight to track.
```

--------------------------------

### Clear all tracked flights

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Clears all flights currently in the 'Additional tracked' sensor by pressing the associated button. This is useful for resetting the tracking list.

```yaml
# Script: clear all tracked flights
script:
  clear_fr24_tracked:
    alias: "Clear FR24 tracked flights"
    sequence:
      - service: button.press
        target:
          entity_id: button.flightradar24_clear_additional_tracked
```

--------------------------------

### Add Flight to Additional Tracked via Service Call

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

This service call adds a specific flight to be tracked by the `sensor.flightradar24_additional_tracked` entity. It accepts a flight number, callsign, or aircraft registration as input.

```yaml
# Service call from automation or script
service: text.set_value
target:
  entity_id: text.flightradar24_add_to_track
data:
  value: "LH400"   # flight number, callsign, or registration (e.g. D-AIHA)
```

--------------------------------

### text.flightradar24_airport_track

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Sets or stops monitoring an airport by its IATA or ICAO code. When set, it provides airport schedule and statistics data. An empty string stops monitoring.

```APIDOC
## text.flightradar24_airport_track

### Description
Sets or stops monitoring an airport by its IATA or ICAO code. Provides airport schedule and statistics data. Pass an empty string to stop.

### Method
`text.set_value`

### Endpoint
`text.flightradar24_airport_track`

### Parameters
#### Request Body
- **value** (string) - Required - The IATA or ICAO code of the airport to monitor, or an empty string to stop monitoring.
```

--------------------------------

### Pause FR24 at night

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Disables all FlightRadar24 API calls during specific hours to save bandwidth. The automation turns off the data fetching switch at night and re-enables it in the morning.

```yaml
# Turn off during night hours via automation
automation:
  alias: "Pause FR24 at night"
  trigger:
    - platform: time
      at: "23:00:00"
  action:
    - service: switch.turn_off
      target:
        entity_id: switch.flightradar24_api_data_fetching

  # Re-enable in the morning
  - alias: "Resume FR24 in morning"
    trigger:
      - platform: time
        at: "06:00:00"
    action:
      - service: switch.turn_on
        target:
          entity_id: switch.flightradar24_api_data_fetching
```

--------------------------------

### text.flightradar24_remove_from_track

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Removes a flight from additional tracking using its flight number, callsign, or registration.

```APIDOC
## text.flightradar24_remove_from_track

### Description
Removes a flight from additional tracking by flight number, callsign, or registration.

### Method
`text.set_value`

### Endpoint
`text.flightradar24_remove_from_track`

### Parameters
#### Request Body
- **value** (string) - Required - The flight identifier (flight number, callsign, or registration) to remove from tracking.
```

--------------------------------

### Remove a Tracked Flight

Source: https://context7.com/alexandrerohin/home-assistant-flightradar24/llms.txt

Removes a specific flight from additional tracking using its flight number, callsign, or registration. This service call is used to manage the list of flights being actively monitored.

```yaml
service: text.set_value
target:
  entity_id: text.flightradar24_remove_from_track
data:
  value: "LH400"
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.