The Flightradar24 integration brings real-time aviation tracking into Home Assistant.

Track flights above your location, monitor airports, follow specific aircraft worldwide, and trigger powerful automations based on live flight events.

✅ No Flightradar24 subscription required

• 🌍 Track flights currently in your area
• ✈️ Follow aircraft anywhere in the world
• 🛬 Monitor airport arrivals and departures
• 🔔 Create flight-based notifications and automations
• 📊 View airport delay and cancellation statistics
• 🗺️ Add live flight maps to Home Assistant dashboards
• 📱 Track flights as Home Assistant device_tracker
• 🔥 Monitor the top 10 most tracked flights on Flightradar24

It allows you:

1. Know how many flights in your area right now, or just have entered or exited it. And get list of flights with full information by every relevant flight for the sensor
2. Track a particular plane or planes no matter where it currently is, even if it is a scheduled flight
3. Monitor daily statistics (like on time/delayed/canceled flights) of the selected airport
4. Get top 10 most tracked flights on FlightRadar24
5. Create notifications (example - Get a notification when a flight enters or exits your area, Get a notification when a tracked scheduled flight takes off)
6. Create automations (example - Automatically track a flight by your needs)
7. Add a live map card with aircraft markers and flight tracks to your Home Assistant dashboard
8. Add flights table for your area to your Home Assistant dashboard by Lovelace Card
9. Add departures/arrivals boards of the selected airport to your Home Assistant dashboard by Lovelace Airport Card
10. Track your flight as Device Tracker
11. Get info for last flights which were in your area or get info about latest exited flight by creating Last Flights History Sensor

1. Install HACS
2. Open HACS
3. Search for Flightradar24
4. Click Download
5. Restart Home Assistant

1. Locate the custom_components directory in your Home Assistant configuration directory. It may need to be created.
2. Copy the custom_components/flightradar24 directory into the custom_components directory.
3. Restart Home Assistant.

Flightradar24 is configured via the GUI. See the HA docs for more details.

The default data is preset already

1. Go to the Settings->Devices & services.
2. Click on + ADD INTEGRATION, search for Flightradar24.
3. You may change the default values for Radius, Latitude and Longitude
4. Click SUBMIT

⚠️ IMPORTANT NOTE ⚠️

1. After integration installation or reload and after every HA restart Current in area sensor may stay at 0 for some minutes or show less than real amount of flights in your area for a while. It is because of downloading information from FR24. Downloading information for a flight takes time. The more flights in your area the more time it takes to load all of them
2. Decreasing scan interval may lead to more errors from FR24
3. Increasing the radius means more flights will be in your area that may get you more errors from FR24
4. If your airport sensors stay Unavailable - check if you track the airport

You may edit configuration data like:

1. Latitude and longitude of your point
2. Radius of your zone
3. Scan interval for updates in seconds
4. The minimum and maximum altitudes in feet between which the aircraft will be tracked
5. Enable/Disable device_tracker for flights
6. Optional: Username and password if you have FlightRadar24 subscription
7. Enable/Disable auto-cleanup of landed tracked flights. That automatically removes flights from the "Additional tracked" list once they arrive at the gate
8. Map Tracker Naming Style.

• Callsign Only (e.g., KLM1412) - Default
• Callsign + Route (e.g., KLM1412 (CDG - AMS))
• Registration + Route (e.g., PH-BXE (CDG - AMS))

To do that:

1. Go to the Settings->Devices & services.
2. Search for Flightradar24, and click on it.
3. Click on CONFIGURE
4. Edit the options you need and click SUBMIT
5. Reload the integration (a full Home Assistant restart is usually not required)

You can configure:

Sensors (Current in area, Entered area, Exited area, Additional tracked) shows how many flights in the given area, additional tracked, just have entered or exited it. All these sensors have attribute flights with list of flight object contained a full information by every relevant flight for the sensor

Sensors Airport arrivals and Airport departures have attribute flights with list of the next 50 airport flights

Switch Most tracked has attribute flights with list of most tracked object

You may be interested to add a live flight as device_tracker with the flight information to a person in HA. To use it - you need to activate this feature in Edit Configuration. When it is enabled - this integration creates device_tracker with static name device_tracker.flightradar24 and this device_tracker updates when there is a live flight in the additional tracked list. It works ONLY with one live flight from the additional tracked list at a time!

⚠️ IMPORTANT NOTE ON ENTITY IDs & TRANSLATIONS ⚠️
Home Assistant automatically generates the underlying entity_id for your sensors based on your system's default language at the time of installation. For example, sensor.flightradar24_current_in_area might automatically become sensor.flightradar24_bereich_betreten on a German system.

Before copying and pasting any YAML or Lovelace code from this README, please verify your exact entity IDs under Settings → Devices & Services → Entities and update the examples to match your localized IDs.

To receive notifications of the entering flights add following lines to your configuration.yaml file:

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 }}"

All available fields in trigger.event.data you can check here

If you have defined more than one device of FlightRadar24 for more places to observe - you may be interested to know what device has fired the event It is stored in

To change name in tracked_by_device

1. Go to the Settings->Devices & services.
2. Search for Flightradar24, and click on it.
3. Click on three-dot near of device you wanted
4. Click on Rename in the opened sub-menu
5. Enter new name and click OK

To receive notification of taking off tracked scheduled flight add following lines to your configuration.yaml file:

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 }}"

To automatically add a flight to additional tracking add following lines to your configuration.yaml file:

Note: If your Home Assistant system is not in English, your sensor names may be translated. Please replace all instances of text.flightradar24_add_to_track below with your exact local entity ID!

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

This is an example to filter flights to track, change the conditions for your needs

You may get info for last flights which were in your area. Or get info about latest exited flight. Here is an example for recording history for the last 5 flights. The sensor has the same structure as sensor.flightradar24_current_in_area and so you can use the same markdown code. Only the sensor state is different - it shows the latest exited flight. You may change it for your needs. Add following lines to your configuration.yaml file:

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

Built-in Lovelace card with an OpenStreetMap of your monitored area, aircraft markers, optional flight tracks, and a list of flights currently in the area.

The card is registered automatically when the integration is loaded — no manual Lovelace resource setup is required.

1. Go to your Home Assistant dashboard
2. In the top right corner, select the three-dot menu, then select Edit dashboard
3. Click + ADD CARD, search for Flightradar24 Card, and select it
4. Choose the sensor entity (usually sensor.flightradar24_current_in_area), set options if needed, and click SAVE

1. Go to your Home Assistant dashboard
2. In the top right corner, select the three-dot menu, then select Edit dashboard
3. Click + ADD CARD, search for Manual, click on Manual
4. Add the following code and click SAVE

Note: If your Home Assistant system is not in English, your sensor names may be translated. Please replace sensor.flightradar24_current_in_area with your exact local entity ID!

type: custom:flightradar24-card
entity: sensor.flightradar24_current_in_area
title: Flights Nearby
show_flights: true
show_tracks: true

You can add flight table to your Home Assistant dashboard

1. Go to your Home Assistant dashboard
2. In the top right corner, select the three-dot menu, then select Edit dashboard
3. Click on + ADD CARD, search for Manual, click on Manual.
4. Add following code to the input window and click SAVE

Note: If your Home Assistant system is not in English, your sensor names may be translated. Please replace all instances of sensor.flightradar24_current_in_area below with your exact local entity ID!

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 %}

This example for sensor.flightradar24_current_in_area which shows flights in your area, to show additional tracked flights replace sensor name to sensor.flightradar24_additional_tracked

All available fields for flight you can check here

To decrease data stored by Recorder in database add following lines to your configuration.yaml file.

⚠️ WARNING
Do not exclude sensor.flightradar24_additional_tracked from Recorder. That sensor restores its tracked flights from the last recorded state after a Home Assistant restart. Excluding it (for example with sensor.flightradar24*) will clear Additional tracked on every reboot.

Heavy flights attributes on other sensors are already excluded from Recorder by the integration itself (_unrecorded_attributes).

Example that keeps Additional tracked restorable:

recorder:
  exclude:
    entities:
      - sensor.flightradar24_current_in_area
      - sensor.flightradar24_entered_area
      - sensor.flightradar24_exited_area

Switch Most tracked when is enabled - shows top 10 most tracked flights on FlightRadar24. It has attribute flights with next flight fields

You can add departures/arrivals boards of the selected airport to your Home Assistant dashboard

To start receiving data for an airport - Pass IATA or ICAO airport code to text.flightradar24_airport_track. To stop receiving airport data just pass an empty string

1. Go to your Home Assistant dashboard
2. In the top right corner, select the three-dot menu, then select Edit dashboard
3. Click on + ADD CARD, search for Manual, click on Manual.
4. Add following code to the input window and click SAVE

Note: If your Home Assistant system is not in English, your sensor names may be translated. Please replace all instances of sensor.flightradar24_airport_ ... below with your exact local entity ID!

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_arrival 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 %}

All available fields for flight you can check here

Sensor sensor.flightradar24_airport_arrivals and sensor.flightradar24_airport_departures shows flights with next flight fields

• FlightRadarAPI by @JeanExtreme002
• The OpenSky integration

This integration should only be used for your own educational purposes. If you are interested in accessing Flightradar24 data commercially, please contact business@fr24.com. See more information at Flightradar24's terms and conditions.