Integrations

Integrations

All optional, all configured in the web panel (Settings tab) or on the device (gear icon > Integrations tab; the watchlist and flyover alerts sit on the Filters tab). An empty field means the feature is off.

Push notifications to your phone (ntfy.sh)

Free, no account needed.

1. Install the ntfy app (Android or iOS).
2. In the app, subscribe to a topic with a unique name you invent, e.g. jans-esp32flight-8341. Anyone who knows the name can read the topic, so make it non-obvious.
3. Enter the same name in ntfy.sh topic and save.

You get a push for:

• Emergency squawks (7500 hijack, 7600 radio failure, 7700 general emergency) within your radius
• Watchlist aircraft entering your radius
• Flyovers, with Flyover alerts (CPA) enabled: a heads-up a few minutes before an interesting aircraft passes nearly overhead, with distance and direction

Home Assistant / MQTT

Enter your broker URI as MQTT broker, e.g. mqtt://user:password@192.168.1.10:1883. The device announces itself via MQTT discovery, so an "esp32flight" device appears in Home Assistant automatically with sensors: nearest aircraft (callsign, route, distance), aircraft count, and session unique count. No YAML needed.

FlightAware flight numbers and routes

By default flights show radio callsigns (RYR638T). A free FlightAware AeroAPI key adds the commercial flight number (FR4238) next to it and uses the live origin and destination as an extra route source. FlightAware serves actual flight plans, so with a key set the routes become authoritative and stale entries from community databases stop mattering.

Create a Personal key at flightaware.com/aeroapi and paste it into FlightAware API key. Results are cached, so the free monthly credit is more than enough for continuous use.

Watchlist

Comma-separated registration or callsign prefixes in Watchlist, e.g. SP-LR,RCH,A388. Matching aircraft are highlighted in gold in the list and push-notified on entry. Military aircraft and notable heavies (A380, AN-124, C-17 and friends) are always highlighted, no entry needed.

Webhook

On every alert (emergency, watchlist, flyover) the device POSTs

{"source": "esp32flight", "title": "...", "message": "..."}

to the URL in Webhook URL. Point it at Node-RED, n8n, a Discord or Slack bridge, or your own endpoint.

Local ADS-B receiver (dump1090 / readsb)

If you run your own receiver (an RTL-SDR dongle on a Raspberry Pi with dump1090, readsb, or any feeder image), point Local receiver aircraft.json URL at its JSON output, e.g.

http://192.168.1.50:8080/data/aircraft.json

The device then reads aircraft straight from your antenna instead of the internet APIs: faster updates, no rate limits, and it keeps working without internet. When the receiver is unreachable, the device falls back to the internet sources automatically and returns to the receiver when it comes back.