Giter Club home page Giter Club logo

home-assistant-flightradar24's Introduction

Flightradar24 integration for Home Assistant

Flightradar24 integration allows one to track overhead flights in a given region or particular planes. It will also fire Home Assistant events when flights enter/exit/landed/took off.

IMPORTANT: No need FlightRadar24 subscription!

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
  3. Get top 10 most tracked flights on FlightRadar24
  4. Create notifications (example - Get a notification when a flight enters or exits your area)
  5. Create automations (example - Automatically track a flight by your needs)
  6. Add flights table to your Home Assistant dashboard by Lovelace Card)

Components

Events

  • flightradar24_entry: Fired when a flight enters the region.
  • flightradar24_exit: Fired when a flight exits the region.
  • flightradar24_most_tracked_new: Fired when a new flight appears in top 10 most tracked flights on FlightRadar24
  • flightradar24_area_landed: Fired when a flight lands in your area.
  • flightradar24_area_took_off: Fired when a flight takes off in your area.
  • flightradar24_tracked_landed: Fired when a tracked flight lands.
  • flightradar24_tracked_took_off: Fired when a tracked flight takes off.

Sensors

  • Current in area
  • Entered area
  • Exited area
  • Additional tracked
  • Most tracked flights (You may disable it via configuration)

Configuration

  • Add to track
  • Remove from track

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

Configuration inputs fields allows to add or remove a flight to/from sensor - Additional tracked. Adding/Removing supports flight number, call sign, aircraft registration number

Installation

HACS (recommended)

Have HACS installed, this will allow you to update easily.

Install quickly via a HACS link

  1. Go to the Hacs->Integrations.
  2. Add this repository (https://github.com/AlexandrErohin/home-assistant-flightradar24) as a custom repository
  3. Click on + Explore & Download Repositories, search for Flightradar24.
  4. Search for Flightradar24.
  5. Navigate to Flightradar24 integration
  6. Press DOWNLOAD and in the next window also press DOWNLOAD.
  7. After download, restart Home Assistant.

Manual

  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.

Configuration

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

Edit Configuration

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 foots between which the aircraft will be tracked
  5. Enable/Disable top 10 most tracked flights on FlightRadar24
  6. Username and password if you have FlightRadar24 subscription

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

Uses

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:
        content: >-
          Flight entry of {{ trigger.event.data.callsign }} to {{ trigger.event.data.airport_destination_city }}
          [Open FlightRadar](https://www.flightradar24.com/{{ trigger.event.data.callsign }})

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 automatically add a flight to additional tracking add following lines to your configuration.yaml file:

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 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
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') %} {% for flight in data %}
          <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%}
          {% 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_tracked

All available fields for flight you can check here

Lovelace Card with Map

  1. Open in a browser https://www.flightradar24.com
  2. Move the map so that your area is in the middle of the screen. And scroll to select comfortable map zoom
  3. Now you have URL of the map like https://www.flightradar24.com/50.03,8.49/12 Remember this URL
  4. Go to your Home Assistant dashboard
  5. In the top right corner, select the three-dot menu, then select Edit dashboard
  6. Click on + ADD CARD, search for Manual, click on Manual.
  7. Add following code to the input window. Replace LATITUDE, LONGITUDE and ZOOM from URL from step 3. (Example - https://www.flightradar24.com/50.03,8.49/12 - LATITUDE is 50.03, LONGITUDE is 8.49, ZOOM is 12)
  8. Click SAVE
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') %} {% 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://www.flightradar24.com/simple?lat=LATITUDE&lon=LONGITUDE&z=ZOOM&label1=reg&size=small
    aspect_ratio: 100%

Database decrease

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

recorder:
  exclude:
    entity_globs:
      - sensor.flightradar24*
Field Description
tracked_by_device 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. To rename the device check this
flight_number Flight Number
latitude Current latitude of the aircraft
longitude Current longitude of the aircraft
altitude Altitude (measurement: foot)
distance Distance between the aircraft and your point (measurement: kilometers)
ground_speed Ground speed (measurement: knots)
squawk Squawk code are what air traffic control (ATC) use to identify aircraft when they are flying (for subscription only)
vertical_speed Vertical speed
heading The compass direction in which the craft's bow or nose is pointed (measurement: degrees)
callsign Callsign of the flight
aircraft_registration Aircraft registration number
aircraft_photo_small Aircraft small size photo url
aircraft_photo_medium Aircraft medium size photo url
aircraft_photo_large Aircraft large size photo url
aircraft_model Aircraft model
aircraft_code Aircraft code
airline Airline full name
airline_short Airline short name
airline_iata Airline IATA code
airline_icao Airline ICAO code
airport_origin_name Origin airport name
airport_origin_code_iata Origin airport IATA code
airport_origin_code_icao Origin airport ICAO code
airport_origin_country_name Origin airport country name
airport_origin_country_code Origin airport country code
airport_origin_city Origin airport city name
airport_destination_name Destination airport name
airport_destination_code_iata Destination airport IATA code
airport_destination_code_icao Destination airport ICAO code
airport_destination_country_name Destination airport country name
airport_destination_country_code Destination airport country code
airport_destination_city Destination airport city name
time_scheduled_departure Scheduled departure time
time_scheduled_arrival Scheduled arrival time
time_real_departure Real departure time
time_real_arrival Real arrival time
time_estimated_departure Estimated departure time
time_estimated_arrival Estimated arrival time

Sensor Most tracked shows top 10 most tracked flights on FlightRadar24 with next flight fields

Field Description
flight_number Flight Number
callsign Callsign of the flight
squawk Squawk code are what air traffic control (ATC) use to identify aircraft when they are flying
aircraft_model Aircraft model
aircraft_code Aircraft code
clicks How many people track this flight
airport_origin_code_iata Origin airport IATA code
airport_origin_city Origin airport city name
airport_destination_code_iata Destination airport IATA code
airport_destination_city Destination airport city name

Thanks To

home-assistant-flightradar24's People

Contributors

alexandrerohin avatar alray31 avatar cvc90 avatar djaeger avatar igorsantos07 avatar michalbundyra avatar miggi92 avatar ottovdv avatar peyn avatar xbmcnut avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

home-assistant-flightradar24's Issues

Flight tracking - timeout "issue"?

Hi

When tracking specific planes, it seems they only get tracked foor x amount of time, cant find any doc on this.
is this the case or?

As of now i have to use a script to update the add to track to have them be tracked the whole flight.

any workaraound or just a feature ?

Add a link and a question about callsign / flightnr

Hi!

  1. Because there are a lot of attributes (flight fields) it could be nice to add a link to it where you can click for more information about the flight or aircraft.

Is that possible to add into your integration?
For instance this url, I think if you search for the spotted flightnumber on this website, it gives you more information.

The main website: https://www.flightaware.com/
and an example of a flight: https://www.flightaware.com/live/flight/BEL8YE

Then you can setup an alerting like this:

service: notify.family
data:
  title: Flightradar
  message: Flightnumber {{ trigger.event.data.callsign }}
  data:
    actions:
      - action: URI
        title: More Info
        uri: >-
          https://www.flightaware.com/live/flight/{{
          trigger.event.data.??? }}
  1. what is the purpose of the sensors? because they stay at "0" all the time?
    image

only when I click on the exited sensor I see a count, but not at the entered sensor. thats strange right?
a flight should be enter AND exit in a certain zone.
image
image

The attritribute flights should be filled with additional information about the flights right? but stays empty here.
What I would like to see is a list of past flights in the area in a lovelace card.

  1. Oh and what is the difference between callsign and flight number? it looks the same

Thanks

Wrong flight number

Adding TK2 (Turkish New York JFK -> Istanbul IST) to track instead adds TK20 (Turkish Istanbul IST -> Seoul ICN)

HA 2026.1 & FR 1.14.1 | [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'flightradar24' at custom_components/flightradar24/coordinator.py, line 240

I just updated from HA 2024.5.5 to 2024.6.1 and am now getting the following error.
I have v1.14.1 of the FlightRadar24 integration.
Just for reference, a number of other integrations I use are encountering the same issue, e.g. Tuya-Local (make-all/tuya-local#1981) and TheWatchman (dummylabs/thewatchman#135) with HA 2024.6

2024-06-08 13:35:17.793 WARNING (MainThread) [homeassistant.util.loop] Detected blocking call to open inside the event loop by custom integration 'flightradar24' at custom_components/flightradar24/coordinator.py, line 240: country = pycountry.countries.get(alpha_3=code) (offender: /usr/local/lib/python3.12/site-packages/pycountry/db.py, line 103: with open(self.filename, encoding="utf-8") as f:), please create a bug report at https://github.com/AlexandrErohin/home-assistant-flightradar24/issues
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 223, in <module>
    sys.exit(main())
  File "/usr/src/homeassistant/homeassistant/__main__.py", line 209, in main
    exit_code = runner.run(runtime_conf)
  File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
    return loop.run_until_complete(setup_and_run_hass(runtime_config))
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete
    self.run_forever()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever
    self._run_once()
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once
    handle._run()
  File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 255, in _handle_refresh_interval
    await self._async_refresh(log_failures=True, scheduled=True)
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 312, in _async_refresh
    self.data = await self._async_update_data()
  File "/config/custom_components/flightradar24/coordinator.py", line 109, in _async_update_data
    await self._update_flights_in_area()
  File "/config/custom_components/flightradar24/coordinator.py", line 125, in _update_flights_in_area
    await self._update_flights_data(obj, current, self.in_area, SensorType.IN_AREA)
  File "/config/custom_components/flightradar24/coordinator.py", line 187, in _update_flights_data
    flight = self._get_flight_data(data)
  File "/config/custom_components/flightradar24/coordinator.py", line 267, in _get_flight_data
    'airport_origin_country_code': _get_country_code(
  File "/config/custom_components/flightradar24/coordinator.py", line 240, in _get_country_code
    country = pycountry.countries.get(alpha_3=code)

Feature Request: estimated times

Alexander,

Would you consider exposing the estimated departure and arrival times of a flight as well? That information is made available by Flightradar24 as well. It would allow me to track a plane's arrival and inform me when it is time for me to leave to pick someone up at the airport.

Thanks,

Christophe

Confused on Adding Track

I just added the integration as we are near an airport and I wanted to figure out what are the various helicopters circling at times, without having to jump into the FlightRadar app. I have the helicopter callsigns saved that I wanted to track and then alert on when they are in the area. I assumed it was as simple as adding a track and then that would show me when any of the added tracks added are in the area, but that doesn't seem to be the case.

I'm trying to wrap my head around how I would then filter the list of in the area to only list or count this set of callsigns.

Adding tails to the lovelace cards

This is more of a documentation suggestion.

The lovelace cards can be configured to include a logo or tail logo of the airline using images from airhex. They have watermarks, but they work well in small configurations. Here is the airhex documentation: https://airhex.com/api/logos/

For larger cards like this:

image

The following img src code can be used:

<img src="https://content.airhex.com/content/logos/airlines_{{flight.airline_icao}}_90_90_f.png?proportions=keep">

This generates a 90x90 image with strict proportions kept. The letter after the dimensions can be used to pick different logo shapes:

'r' for rectangular logos with 3.5:1 sides ratio;
's' for square logos (1:1 sides);
't' for tail logos (1:1 sides);
'f' for flipped tail logos (1:1 sides)

I'm using the flipped tail logo in my case.

Full card code to show inbound flights to my home airport (SAN). I filter by altitude over 1000 and under 7000 so that I can filter out aircraft flying over or taking off, I change the filters for the Outbound card and the flying over card:

{% set data = state_attr('sensor.flightradar24_current_in_area',
  'flights') %} {% for flight in data | sort (attribute='altitude')%} {% if
  flight.airport_destination_code_iata == 'SAN' and flight.altitude > 1000
  and flight.altitude < 7000 and flight.airline_short %} <table>
 <tr>
  <td><img src="https://content.airhex.com/content/logos/airlines_{{flight.airline_icao}}_90_90_f.png?proportions=keep"></td>
  <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<td>
  <td>
  {{ flight.flight_number }} {{ flight.aircraft_code }}<br>
  {{ flight.airline_short }}<br>
  {{ flight.airport_origin_code_iata }} <ha-icon icon="mdi:arrow-right"></ha-icon> {{ flight.airport_destination_code_iata }}<br>
  Altitude - {{ flight.altitude }} ft{%if flight.altitude > 0 %} ({{(flight.altitude * 0.3048)| round(0)}} m){% endif%}<br> 
  </td>
 </tr>
 {% endif %}
 </table>
 {% endfor %}

I find that using tables helps keep the card cleaner.

To add small tail logos to the suggested lovelace code provided by the integration, you can replace

<ha-icon icon="mdi:airplane"></ha-icon>

with

<img src="https://content.airhex.com/content/logos/airlines_{{flight.airline_icao}}_20_20_f.png?proportions=keep">

20x20 looks ok to me. If you want to use a square logo instead, use s instead of f like in the guidelines above.

With flipped tails, my card looks like this:

image

edit: Updated the code to use airline_icao instead of airline_iata because there's a small airline that uses the same JL code as Japan Airlines. Airhex supports ICAO codes so this is more accurate.

Maybe also include squawk?

Very nice work on this integration! I previously made a pyscript app to pull from opensky, but was looking into doing the same for flightradar24 when I came across this! Very nicely done! One thing I'm missing is squawk, usually I don't care about it that much, but I do like to look out for squawk 7700/7600 and 7500 (we had one a while ago at EHAM, that turned out to be pilot error).

Vertical Speed

Love this integration. I have a few automations for airplanes and airliners flying overhead and announcing them on my Alexa.

I was wondering if VSI rate could become an available 'field'. I would use this info to assist in determining whether an aircraft/airliner was inbound, outbound or cruising overhead or into/out of my nearby airport.

Thanks so much for this fun integration!

Country code bug

It was reported that there is a mix of Alpha-2 and Alpha-3 country codes.

Minor setup wording corrections

Hi
Thanks for your work on this integration, I've just installed it, so far impressed.
When installing I noticed some wording which looks incorrect (possibly just a language translation error) so constructively sharing fyi:
I'll send a picture as much easier to see & consider.
Cheers
image

Possible simplification by using get_bounds_by_point

Not completely sure, but it looks like the integration also does a calculation to find the bounding box, based on coordinates and radius, but the pyton FlightRadarAPI also has a call for that? get_bounds_by_point.

Maybe that was not used for a reason, or maybe it was overlooked?

Feature request: Two Devices

Is it possible to create a second device with a different radial? I am lloking to have 500m radial and a 30Km radial. I have tried and created the second device but it does not initialize.

Many Thanks for the hardwork.

Feature Request: Configurable single aircraft sensor

I can do a lot of powerful filtering and display in Home Assistant to get exactly the type of aircraft I care about. For example I have a small area that only looks for Helicopters, and another that only displays commercial aircraft.

This is done by adding entries to the if statement in the for loop used for the lovelace card.

I want to use the data that the integration provides to generate an image on my Tidbyt. The Tidbyt doesn't have official Home Assistant integration, but I've been able to make a lot of things work by running their pixlet binary (to generate the screens) locally and query Home Assistant for data from Media Players for example.

I have an app that tracks flights, but it uses a RapidAPI API that is paid and I can't do a lot of filtering on it (or I can, but I am a lot more comfortable with Home Assistant templates than the Tidbyt Skylark code).

It would be nice if the integration could create a sensor based on user specified parameters. This could be a new sensor, or have an option to make sensor.flightradar24_current_in_area use the filters.

Filters would be maybe common things like:

  • Altitude is higher/lower than
  • Contains Airline Short (private aircraft don't have one)
  • Ground speed is higher/lower than
  • Origin/Destination airport is X or is not X
  • Excluded/included aircraft codes
  • Max number of results to show

Again, this can all be done with if statements, but I think it would be pretty user friendly to have the above settings in the Integration configuration. This is by no means urgent, but just wanted to put it out there.

Thank you for all your work. I love this integration.

Not getting any data within Home Assistant

I am trying you install, it deploys, starts, and is configured as expected

image

However I am never getting any aircraft tracking within Home Assistant

I am however sending data to fr24

image

Logs in debug mode as follows

2024-02-27 11:32:21.976 ERROR (MainThread) [custom_components.flightradar24.config_flow] FlightRadar24 Integration Exception - Your email or password is incorrect
2024-02-27 11:36:17.112 DEBUG (MainThread) [custom_components.flightradar24] Finished fetching flightradar24 data in 0.255 seconds (success: True)
2024-02-27 11:36:27.531 DEBUG (MainThread) [custom_components.flightradar24] Finished fetching flightradar24 data in 0.291 seconds (success: True)
2024-02-27 11:36:27.531 INFO (MainThread) [homeassistant.components.sensor] Setting up flightradar24.sensor
2024-02-27 11:36:47.195 DEBUG (MainThread) [custom_components.flightradar24] Finished fetching flightradar24 data in 0.332 seconds (success: True)
2024-02-27 11:37:08.793 DEBUG (MainThread) [custom_components.flightradar24] Finished fetching flightradar24 data in 0.186 seconds (success: True)
2024-02-27 11:37:29.157 DEBUG (MainThread) [custom_components.flightradar24] Finished fetching flightradar24 data in 0.295 seconds (success: True)
2024-02-27 11:37:49.182 DEBUG (MainThread) [custom_components.flightradar24] Finished fetching flightradar24 data in 0.320 seconds (success: True)
2024-02-27 11:38:09.059 DEBUG (MainThread) [custom_components.flightradar24] Finished fetching flightradar24 data in 0.197 seconds (success: True)
2024-02-27 11:38:29.145 DEBUG (MainThread) [custom_components.flightradar24] Finished fetching flightradar24 data in 0.265 seconds (success: True)
2024-02-27 11:38:49.050 DEBUG (MainThread) [custom_components.flightradar24] Finished fetching flightradar24 data in 0.188 seconds (success: True)
2024-02-27 11:39:09.059 DEBUG (MainThread) [custom_components.flightradar24] Finished fetching flightradar24 data in 0.196 seconds (success: True)
2024-02-27 11:39:29.372 DEBUG (MainThread) [custom_components.flightradar24] Finished fetching flightradar24 data in 0.348 seconds (success: True)

however current in area is empty, and given that I in Atlanta and KATL , its pretty safe to assume that there is many aircraft over me right now... Infact ADSBExchange shows several dozen right now...

Thanks, and appreciate any help you can offer :)

Event for plane landing

Can there be an automation that calls the notification service when a tracked flight lands?

No data after update beyond 1.7 and min/max wording confusing

Thank you for this awesome add-on! I'm not seeing any flights with the parameters shown below. It was working just fine under 1.6. Running 1.8 now and downgraded to 1.7, made no difference.

Also, I think the wording could be improved for the minimum and maximum heights?

  • "The maximum attitude in foots above which the aircraft Will be tracked" should maybe say "Aircraft above this altitude will be ignored. (or have I got that backwards?)
  • "The minimum altitude in foots under which the aircraft will be tracked" should maybe say "Aircraft below this altitude will be ignored"

Of course, upper level altitude setting should also be on top of the lower limit but that might be my OCD? 😁Using minimum and under together along with maximum and over at least for me is very confusing.

image

image
Above was with 2 aircraft in range.

Unable to track specific flight by number

Screenshot_20240312_073520_Home Assistant

Hi, i was trying to track a flight and there are no way it can be added. FYI: no credentials for flightradar account are set.

UPD: I've even tried to use in different name variants, such as su1395, SU1395, SU 1395 and SU-1395.

Feature Request: altitude limit

Many thanks for the great integration! As I live near an airport, it would be great to be able to specify an altitude limit, as I'm usually only interested in the planes arriving and departing. The overflights at higher altitudes are less interesting.

Thanks again!

Translations

Доброго времени суток! Спасибо за полезный компонент!
Два вопроса:

  1. Сегодня заметил что в последнем обновлении добавилась поддержка польского языка. Так где, собственно говоря, появляется локалзация разных языков, в каком месте интерфейса или в карте на dashboard? В названии сенсоров, я так понимаю?
  2. Написал скрипт который выводит оповещение для произнесения Алисой со следующим содержимым:
    "На данный момент над нами пролетает самолет Airbus A321-271NX авиакомпании Lufthansa, рейс номер LH1281 из Athens в Frankfurt"
    Но никак не приложу ума как сделать так, чтобы названия городов и авиакомпаний тоже переводились Алисой, не смог найти подходящий сервис. Возможно ли вообще такое?

Addon breaching FR24's Terms of Service?

I had been running this addon for a few weeks when randomly it stopped being able to update flight information, and I also found that all of my iOS devices on the network were semi-banned from the iOS app, only displaying limited information, and overall a pretty broken app.

I reached out to Flightradar24 help and after a few back-and-forth emails they told me that this integration violates their terms of service and that the ban had been administered correctly:
"Please note the information you describe is against Flightradar24's terms of service https://www.flightradar24.com/terms-and-conditions. So the block was correctly administered. "

The support rep also stated that there is a new API service being released in the coming months:
"If you require more data then you may be interested in our API service that we will be releasing shortly. Please keep an eye out for this in the coming months."

Posting this here to see if anyone else has had the same problem, and if the developers of this addon can resolve the issue with Flightradar24. I'm still working on getting them to remove my ban but as of when I post this that is still in place.

Change System options

It would be nice if in the future we could change the system options like:

  • refresh rate
  • radius

Example:
Screenshot_20231124-100704.png

Instructions can't be followed

Hi, thanks for this app! The instructions talk about a password and IP... I did not get prompted for either, albeit the installation seems to work. Not urgent

Improve startup performance

I checked integration startup times in 2024.4 and from all my integrations, Flightradar24 is the slowest one with 15.48 seconds. I don't think I have a very complicated config.
Anything that can be done to improve this?

PS: Great integration so happy to accept the startup time, but maybe there are quick wins.

Feature request: Planes on the ground

Great integration! 👍🏻
I'd just want the option to show what's on the ground in a specific area. I live right by an airport and as soon as the planes land they "disappear" from HA.
/ David

Is it possible to identify which device triggered the event?

This was mentioned in #11, but since it's just tangentially related, I'm posting a separate issue: the problem is exactly what was mentioned there, there's no way to identify which place triggered the event. It would be helpful to create more meaningful notifications, for instance.

In the meantime, I'll try checking about moving the automation out of events and maybe post here an example.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.