Yup, that’s what I figured. That station is remote (at my wife’s son’s in Los Angeles, whereas I’m in Massachusetts) so it’s just accessible to me by VPN. So I built an image locally by just using bookworm and released packages and sent it to him to burn a new SD card. It’s only used for ADS-B / UAT to feed various services so a Pi 3B+ is enough for that in general. Locally I’m experimenting with the newer OS and packages but have several 4B / 5B devices with 4GB minimum…
Thanks for all you do, I’ve been playing with combine1090 and its ilk here as well…
Yes, there’s a fair overlap in technology between flight tracking technology and amateur radio, I have a few ham friends who also operate feeders. And it keeps me off the street…
I have a question about your suggestion to install piaware:
Since the setup takes quite a long time, as you already mentioned, I wonder what exactly is being installed? Just the piaware client?
If Flightaware eventually manages to get their software to officially support Trixie, will it be necessary or advisable to reinstall the software, or will it be possible to switch from this version to the official one?
How does this work with Flightradar24, Planefinder and RadaBox24?
(1) Tools & dependencies for building piaware package from source code
(2) Run-time dependency packages, which are required to run the piaware
(3) Piaware package.
If pre-built package of piaware from Flightaware (or from my PPA) are installed, then packages under (1) above are NOT installed. However packages under (2) are still installed. As regards piaware package under (3), these are not built on your Pi. The pre-built packages from Flightaware Repository (or from my PPA) are installed by command sudo apt install piaware. Not building package on your Pi saves lot of time which is required if package is compiled from source code.
It should not be necessary to replace the package you built from Flightaware source code, unless Flightaware releases a version with version number higher than 10.2.
Thank you for your information. I used your setup from above, which ran without errors, but M-LAT does not work.
I also installed Piawre Web, but I think I could have saved myself the trouble, as it runs on port 80, which is already occupied by another service. Can the port number be changed? How can I uninstall it if there is no way to change the port, and what about the Piaware setup?
sudo apt purge piaware and sudo apt purge piaware-web?
When setting up Flightradar24, the MLAT client does not start after installation.
Why I think MLAT isn’t working is that the overview page after installation (unfortunately, I didn’t save it) showed MLAT as ‘orange’ while the rest was ‘green’.
Thanks for this great thread – trying to get my feeder back online, started with the official PiAware base OS (then added; ADS-B Exchange, FlightRadar24 and RadarBox), but regretted that after deploying, because I realized it was based on Raspbian 12. Seems I’m going to need to start with a fresh image, as the goal is long-term stability, which I assume means I’ll want Trixie. Glad to see you haven’t missed a beat. Appreciate your well-written and extremely well tested posts and guidance.
Am i safe to assume that using a Trixie base OS will be the correct path forward, starting with a fresh SD Card image, then manually configuring the various feeders? I’m using a RPi4B (4GB) with a basic RTL-SDR usb with basic rabbit ears type antenna. Will revisit the hardware choices once i’ve got the software reconfigured and working.
If by “SD Card image” you mean “Piaware SD Card image” from Flightaware site, then please note that Flightaware has not yet made available Trixie based image, and currently available image is Bookworm based.
What you will need is to write to your microSD Card the “Raspberry Pi OS Trixie” image, using “Pi imager”, and then proceed with package install of dump1090-fa & piaware on it
The piaware and dump1090-fa packages for Trixie can be installed by method given here:
NOTE:
To avoid conflict with Flightaware repository (when they release their packages for Trixie), I strongly ecommend that after installation of packages is comleted and running ok, remove entry of my PPA from your RPi’s apt sources list. This can easily be done by following commands:
This is the easiest way: https://adsb.im/
This isn’t trixie yet either but you get a nice backup / restore option so moving to trixie will be simple.
Not to discourage people from other options of course
Somewhat black box unless you look at the source vs running commands (which are in turn pretty much a black box but hey).
Oh my goodness, thank you – first time seeing ADSB.im site, what a fantastic resource. Seems i have a bunch of reading and research to do now. Absolutely wonderful to see the same familiar faces, appreciate both of you sharing your big brains with a neophyte such as myself, @wiedehopf@abcd567 thank you kindly and happy new year, gents.
during a routine update on my RPI, noticed a message about updated flightware repository, is that something about being installable on Trixie ?
my system still runs previous Debian, thinking of doing new Trixie install ONCE all bits’n’pieces are in place, just curious, TIA
The following packages will be upgraded: dump1090-fa flightaware-apt-repository libnghttp2-14 piaware 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/8,925 kB of archives. After this operation, 3,072 B disk space will be freed. apt-listchanges: Reading changelogs… (Reading database … 204269 files and directories currently installed.) Preparing to unpack …/libnghttp2-14_1.52.0-1+deb12u3_arm64.deb … Unpacking libnghttp2-14:arm64 (1.52.0-1+deb12u3) over (1.52.0-1+deb12u2) … Preparing to unpack …/dump1090-fa_11.0~bpo12+1_arm64.deb … Unpacking dump1090-fa (11.0~bpo12+1) over (10.2) … Preparing to unpack …/flightaware-apt-repository_1.3_all.deb … Unpacking flightaware-apt-repository (1.3) over (1.2) … Preparing to unpack …/piaware_11.0~bpo12+1_arm64.deb … Unpacking piaware (11.0~bpo12+1) over (10.2) … Setting up libnghttp2-14:arm64 (1.52.0-1+deb12u3) … Setting up dump1090-fa (11.0~bpo12+1) … adduser: The user dump1090' is already a member of plugdev’. Restarting lighttpd.. Setting up flightaware-apt-repository (1.3) … Installing new version of config file /etc/default/flightaware-apt-repository … flightaware-apt-repository: regenerated APT configuration /etc/apt/sources.list.d/flightaware.sources flightaware-apt-repository: please run ‘sudo apt update’ to use the new configuration Removing obsolete /etc/apt/sources.list.d/flightaware-apt-repository.list file … Setting up piaware (11.0~bpo12+1) … Processing triggers for rsyslog (8.2302.0-1+deb12u1) … Processing triggers for man-db (2.11.2-2) … Processing triggers for libc-bin (2.36-9+rpt2+deb12u13) …
Ver 11.0 is released for bookworm (debian 12) only, and not yet for trixie.
Checked few minutes ago on trixie.
pi@rpios-trixie:~ $ sudo apt update
... ... ...
... ... ...
Warning: OpenPGP signature verification failed: https://apt.svc.flightaware.com/piaware/release trixie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key 56B6684E138929F4E7CF014BC3B2A470AAD5A173, which is needed to verify signature. Signing key on 4E49CAF6B9F2BF8FC240E4BAB931BB28DE85F0DD is not bound: No binding signature at time 2026-05-14T20:16:43Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Error: The repository 'http://flightaware.com/adsb/piaware/files/packages trixie InRelease' is not signed.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Thank you Oliver. Yes I had installed older version 1.2 about a month ago. After seeing your post, installed version 1.3, and now it shows piaware ver 11.0 is available.
