Legacy Update

Original Flight Tracker boxes.

Why some first-generation boxes stopped updating, and the two ways I can help.

What happened

The original setup became too expensive to keep running the same way.

The first boxes were Raspberry Pi based and used an earlier API path. Over time their API traffic became too expensive to keep paying for in the background.

I moved the platform to something sustainable so I could keep supporting the boxes.

Mach 2 gets aircraft positions and routes from the managed FlightTrackerLED service, with optional support for your own ADS-B receiver. Provider changes are handled in the service and in firmware updates.

Guides for open aviation APIs and other data sources mean no owner is locked into one backend; a new provider can be switched on from settings.

Manual patch

If you are comfortable with remote.it, grant me temporary access in the app and I will SSH in and update the box.

The lowest-cost path, with a little back and forth. Exact steps coming here.

Mach 2 Drop In

The clean replacement: the Raspberry Pi comes out and the Mach 2 controller goes in, with current firmware, scenes and OTA updates.

Phone or USB setup, the online owner portal and optional Local ADS-B.

Redundancy

No single data provider should be the whole product. If one API gets too expensive or stops working, there is another documented path, and OTA updates keep the box supported.