Advanced Features

This section covers firmware updates, how the data feed and enrichment work, network administration — for users who want to understand what's happening under the hood.

Over-The-Air (OTA) Firmware Updates

FlightRadar checks for firmware updates automatically and installs them securely over HTTPS from the TopBytes update service.

How OTA Works

  • About 30 seconds after WiFi comes up, the device asks the update service whether a newer release is available for this unit (identified by its Device ID / MAC).

  • After the first check, it re-checks every hour for the rest of uptime.

  • Production units automatically install only strictly newer released firmware.

Manual Update Check

You don't have to wait for the hourly cadence. In Settings → SW UPDATE, the row shows the current firmware version; tapping it runs an immediate check. While checking it shows CHECKING...; if you're already current it shows UP TO DATE briefly.

Beta / Pre-Release Builds

If the update service offers a pre-release beta build for your unit, installing it is never automatic. FlightRadar shows a confirmation dialog first:

⚠  Beta version X.Y.Z

This is a pre-release beta build and may be unstable. Install it now?

[ CANCEL ]   [ INSTALL ]

Only if you tap INSTALL does the beta firmware download.

The Update Progress Screen

During an update, a full-screen page takes over the LCD with:

  • A title and a download progress bar (0–100 %) with the percentage

  • The warning: Do not power off. The device restarts when done.

On success the device shows Update complete. Restarting... and reboots into the new firmware. If the download fails it shows Update failed. Resuming., waits a moment, and returns to normal operation — your existing firmware is untouched.

Warning

Do not remove power during an update. Because the previous firmware is only replaced once the new image has fully downloaded and verified, a power loss mid-download simply leaves the existing firmware running — but it's still best to let it finish.

How the Data Feed Works

Aircraft Positions

FlightRadar polls the community adsb.fi open-data network for aircraft within range of your home location:

  • Endpoint: https://opendata.adsb.fi/api/v2/lat/<lat>/lon/<lon>/dist/<radius> (HTTPS), centred on home, with the radius derived from your configured range

  • Poll interval: about 15 seconds in steady state. Until the first successful poll it retries quickly (from 1.2 s), backing off up to 15 s if the service keeps failing

  • Each aircraft record provides the ICAO24 hex, callsign, position, altitude, ground speed, track and vertical rate

Positions are kept in an in-memory table (up to 24 contacts) keyed by ICAO24, so blips update in place across polls rather than flickering. Contacts that stop being reported fade and are removed.

Aircraft & Route Enrichment

When you select an aircraft, FlightRadar looks up extra details from adsbdb.com (a free service — no key required):

  • Aircraft (by ICAO hex): type/model, registration, operator

  • Route (by callsign): IATA flight number, origin and destination, and the destination coordinates used to estimate an ETA

Lookups are cached per aircraft, prioritised for the aircraft you've selected, and throttled in the background so they never block the UI. If a lookup fails or the aircraft isn't in the database, the panel simply shows what it has (unknown aircraft, route unknown) and the scope keeps working.

Note

Both the position feed and enrichment need internet access over HTTPS. If your network blocks outbound HTTPS, the scope and detail panel will have little or no data.

Network Administration

Ports Used

Port

Protocol

Purpose

80

TCP (HTTP)

Web setup page (inbound, AP setup mode only)

53

UDP (DNS)

DNS resolution (outbound; also the captive-portal DNS in AP mode)

123

UDP (NTP)

Time synchronisation (outbound)

443

TCP (HTTPS)

Aircraft feed (adsb.fi), enrichment (adsbdb.com), and firmware updates (u.topbytes.net) — all outbound

Firewall Considerations

For normal operation, allow outbound:

  • HTTPS (443) to opendata.adsb.fi, api.adsbdb.com and u.topbytes.net

  • NTP (123) to pool.ntp.org / time.google.com

  • DNS (53)

The inbound web page on port 80 only runs while the device is in access-point setup mode; it is not exposed on your home network during normal operation.

Warning

The setup web page has no password protection. Only use it on the device's own FlightRadar Setup access point; never expose it to the public internet.

Time Synchronisation

FlightRadar synchronises its clock via NTP shortly after WiFi comes up.

  • NTP servers: pool.ntp.org and time.google.com

  • Timezone: set in Settings → TIMEZONE; daylight-saving is applied automatically

  • Format on screen: HH:MM:SS plus a Mon DD Mon date line

If NTP hasn't completed yet (or the device is offline), the clock will be inaccurate until a sync succeeds.

Power Consumption

  • Typical: ~2–4 W at 5 V (dominated by the LCD backlight)

  • Peak (during an OTA flash): up to ~1 A at 5 V

  • Use a quality 5 V / 1 A or higher USB-C supply

  • USB-C power banks work for portable use; a 10,000 mAh bank runs the device for many hours

  • Use Night Mode to switch the backlight off overnight and reduce power and panel wear

Security Notes

  1. Use a WPA2/WPA3 WiFi network; avoid open networks.

  2. Keep firmware up to date — the OTA check runs hourly.

  3. The setup web page is unauthenticated by design and only runs in AP setup mode; don't route it to the internet.

What's Next?