This is a really nice integration and out of the box I’ve got a nice map showing the overhead flights, we’re under a flight path so it saves me opening the app! Next step is to refine the notification radius and then get them announced!
Having gone through this thread and the github pages a few times, I do have a F24 subscription but I can’t find where to enter this, if I need to because I’m making too many API calls being under a flight path? I am also not clear how I can use the flight_number to follow the family flights, either on a map or a sensor.
Guidance to the right documentation would be appreciated.
I’m guessing this is more of a FR24 issue, but… I have a relative returning to UK on flight QR11 from Doha, when I add to track QR11 I get flight QR1109.
If I search in FR24 for QR11, in the search results QR1109 is the first result in LIVE FLIGHTS. The flight QR11 is further down listed under RECENT OR SCHEDULED FLIGHTS.
Hi, I’ve created a custom card to go along with this integration.
It is designed to show flights relative to a tracker, and in addition to the data received from the integration it calculates if flights are approaching you, how close they will pass and when.
It allows for filtering with complex conditions and features a small zoomable “radar” screen with the tracked flights. Flight positions can be continuously projected between updates from flightradar24 based on current position, speed and direction. Local features as runways and locations can be added to the radar.
Wonderful addition. Thank you for your hard work and generosity. A couple suggestions:
When a photo of the plane is not available, just display nothing, instead of a “broken” image icon.
Allow a fixed location (ideally the home location) instead of the device tracker.
(I live near a military base, so there are no photos available for many of the flights. I travel frequently, but only care about flights near my home, not relative to where any of the tracked devices/people may be.)
As an opposite question of what FortranFour asked, it would it nice to configure the Flightradar24 integration to optionally use a tracker for the location instead of a fixed lat/lon pair?
Thanks for this…very nice card.
When adding the new location config to my install the card complained when only location: (with lat/lon) was specified that location_tracker: was missing from the config…adding this back in (with a zone rather than device_tracker so it doesn’t report a location) made the card work fine again (and using the lat/lon as I can see flights at home while currently away)
I just read through your documentation about templating. Would be nice if you can give one sample config of this card including template configuration.