Legacy Update

Original Flight Tracker boxes.

A short note on why some first-generation FlightTrackerLED boxes stopped updating, what changed, and the two ways I can help.

What happened

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

The first Flight Tracker boxes were Raspberry Pi based and used an earlier API path. Over time, the amount of API traffic those boxes generated became too expensive for me to keep paying for in the background.

The original data setup worked for a long time, but the cost and request volume kept growing. I had to move the platform to something more sustainable so I could keep supporting the boxes without the API bill getting out of hand.

Mach 2 receives cloud aircraft positions and routes from the managed FlightTrackerLED service. It also supports an optional ADS-B receiver on your home network. Changes to upstream providers are handled in the service and through firmware updates.

I also have guides for open aviation APIs and alternate data sources, so owners are not locked into one backend forever. If a provider stops making sense, a new one can be switched on from settings without replacing the box.

Manual patch

I can patch the box manually if you are comfortable following the remote.it process. That means granting temporary access through the remote.it app, then letting me SSH in and update what needs to be updated.

This is the lowest-cost path, but it takes a little back and forth. I will add the exact steps here once the process is fully written out.

Mach 2 Drop In

This is the clean replacement path for original boxes. It swaps the Raspberry Pi setup for the new Mach 2 controller, with current firmware, OTA updates, Airplanes.live overhead data, and the newer scenes and settings work.

The newer hardware supports USB setup, an online owner portal, optional Local ADS-B, and OTA updates so fixes can ship without taking the box apart.

Redundancy

The focus now is simple: no single data provider should be the whole product. If one API becomes too expensive or stops working, the box has another documented path, and OTA updates give me another way to keep it supported.