How It Connects / Local and online paths

Most of Local Flight stays on your network.

Your screens talk to the computer running Local Flight over your home or local network (LAN). The internet is used only for the flight data you choose, phone-only Standalone mode, optional encrypted access away from home, or a report you submit.

PATHDESTINATIONSTATE
AT HOMEYour computer and screensLOCAL
FLIGHT DATAYour chosen sourceCHOICE
AWAYEncrypted paired messagesOPTIONAL
REPORTSOnly when sent or enabledCONSENT

Illustrative connection table · no live network inspection

01 / CONNECTIONS

Follow only the paths your setup uses.

Each path below says what connects and what leaves your device. Local screens stay local; optional online services enter only for the feature you select.

Use Local Flight around the house
Computer running Local FlightWindows · macOS · Linux · Raspberry Pi
Your local screensDesktop app · browser · LED matrix · Companion. Nothing leaves your network for this connection.
Get real-world flight data
Your own aviation-data API keysThe keys remain saved on the computer running Local Flight.
Your selected providerOnly the provider receives its key and the airport or aircraft request needed for the feature.
Use the Beacon Tools shared service
Your Local Flight setupSends a random service ID and the airport request needed for the shared board.
Community RelayReuses recent shared airport data and applies update and fair-use limits.
Reach your setup while away
Remote CompanionThe encryption key stays on your paired phone and Local Flight computer.
Community RelayPasses along encrypted messages and routing details. Beacon Tools cannot read the message.
Use only a phone
StandaloneYour airport choice and recent movement history remain on the phone.
Community RelayReceives a random service ID and the requests needed for board, radar, weather, and map data.
02 / UPDATE TIMING

Why Local Flight may keep showing an older board.

Aviation-data services have update limits and can be temporarily unavailable. Local Flight keeps a known board visible when it is safer and more useful than an empty screen, and shows when the data was last updated.

30 min

Community Relay board

A Community Relay setup requests a new schedule board no more often than every 30 minutes.

3 h

Standalone board

Phone-only Standalone checks for a new schedule board no more often than every three hours.

5 min

Standalone radar

Phone-only Standalone asks for new radar data no more often than every five minutes while the radar is open.

If a provider has a temporary problem, Local Flight may keep the last known board visible. Check the freshness time shown in the app.

03 / TROUBLESHOOTING

Start with the mode shown in the app.

The mode name tells you whether to check your home network, the computer running Local Flight, or the phone’s internet connection.

  1. 01 / HOMECompanion on Wi-Fi

    Keep the phone and Local Flight computer on the same trusted network, confirm Local Flight is running, and scan the pairing code in Settings or enter the local address with port :8000.

  2. 02 / AWAYRemote Companion

    Leave the Local Flight computer online and connected to Community Relay. If access was revoked, return to the same home or local network and pair again.

  3. 03 / DIRECTStandalone

    Check the phone’s internet connection and wait a few minutes. A recent board may remain visible while a provider is unavailable.

  4. 04 / SUPPORTNeed another pair of eyes?

    Use Support and include the mode, airport, approximate time, and whether the phone and Local Flight computer were online. Include diagnostics only if you choose.