maybe better to post in the thread for the card itself…
probably the same or similar subset of people in that thread but maybe the dev will see it…
FWIW I don’t see that error…have you tried the usual things around clear cache, different browser, etc
Yes, i tried EDGE and it seems the errors are gone. So, what is the cause? Chrome? The card itself?
@rbita @bmccluskey Thank your for globe.adsb.fi example - I have added the README
You may have noticed that Flightradar24 has disabled using their map into iframe. So the map alternative is using https://globe.adsb.fi/
Please check the documentation to replace map URL here GitHub - AlexandrErohin/home-assistant-flightradar24: Flightradar24 integration for Home Assistant · GitHub
Fix for closest_distance Fix for closest_distance (#161) by tyz · Pull Request #165 · AlexandrErohin/home-assistant-flightradar24 · GitHub
It is better to use parameters lat and lon instead of SiteLat and SiteLon
URL example:
https://globe.adsb.fi/?enableLabels&trackLabels&zoom=12&hideSideBar&lat=50.984944839678334&lon=11.311357147743463
Hi, did you ever find a fix to this issue? I copy-pasted the code from the official documentation (and changed the coordinates) and I still have the same issue as you did.
To fix this use the original code…
Altering as i did . . Was the prob…
Worked on this today, and I’m loving it 
Source for the airline logos here.
Here’s the relevant code section:
- 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 %}
<pre> {%if flight.airline_iata %}<img src="https://images.daisycon.io/airline/?width=140&height=27&iata={{ flight.airline_iata }}" /> {% endif %} {%if flight.airport_origin_city %}<img src="https://flagsapi.com/{{ flight.airport_origin_country_code }}/flat/64.png" height="30"/>{% endif %} {%if flight.airport_destination_country_code %}<img src="https://flagsapi.com/{{ flight.airport_destination_country_code }}/flat/64.png" height="30" />{% endif %}
{{ flight.flight_number }} {{ flight.airport_origin_code_iata }}-{{ flight.airport_destination_code_iata }} / {{ flight.aircraft_model }}
Altitude {{(flight.altitude * 0.3048)| round(0)}}m / Speed {{(flight.ground_speed * 1.852)| round(0)}}km/h / {{ flight.aircraft_registration }} </pre>
{% endfor %}
Looks to me it is dead for a few days now…
The new stuff is there…but unavailable…
And the ohters are dead too…status: unlnown…
Is the api that falls or flightradar itself?
Did try reload… refresh…new install
Nothing works…any ideas??
Thnx!
Yes I have the same issue, I opened a issue on the Git-Hub, and no documentation on what to put for the airport? ICAO?, IATA or airport name?
Tried therm all and status: unlnown
I had to turn ON most tracked flights and turn OFF the device tracker feature (appears an init bug)
…Then enter the airport code as ICAO
…Then they popped in.
Notes.
The airport field clears on reload? I mean i can create an automation hut should I have to?
There appears to be an init bug on the device tracker feature.
From the documentation
Airport track - Pass IATA or ICAO airport code to start receiving data in Airport sensors. To stop receiving airport data just pass an empty string
What do Home Assistant Logs say?
Ok!..sofar the fic from Nathan worked!
However this means i can’t use the device tracker now…
And that’s just the one i use the most
HA LOG was full of errors due this thing…
Doh@ Ya just beat me intoo it
Thank You for the fix!
