Setting up from scratch with Trixie?

Hi there,

Well the time has come…I have 8 Pi’s with my ‘main’ box running my VR stuff which looks like it has a corrupt SD Card and will not boot. My carefully curated backup system failed a while ago where most of my Pi’s lost the ability to clone the system card to a spare as I had been doing for years.

I rebooted my main PoE switch and 7 Pi’s came back up but of course the one that failed was my VR box…typical…the very one that I would have no idea of how to start from scratch on.

So…as I am still running Bullseye on all 8 of the Pi 4 4GB I figured I’d better get up to date and so downloaded Pi Imager and wrote Trixie to a 128GB microSD Card, inserted it into my ‘dead’ Pi and plugged it into the PoE cable and Yay…up it came.

So now I need to start from scratch installing the four packages I feed;

FlightAware

FlightRadar 24

RadarBox 24

ADS-B Exchange

But how best to go about this?

Which package to install first and how to configure from scratch using the AirSpy 2 I have sat in its box since Feb 2022 instead of the old RadarBox Green dongle I have been using since 2020-ish?

Is there a resource anywhere that might help me or is there a patient, kind-hearted soul that can walk this ‘forgotten more than I ever knew in the first place’ sap through the entire process please which might also serve to help others in the future?

I don’t have direct access to any of my Pi’s through keyboard/mouse/monitor but access through RDP, SSH and various Apps which may very well be a problem now I am using Trixie as ISTR things like XRDP would not even work properly when using 64-bit Bullseye let alone a 3-generation newer Raspberry Pi OS.

So how best to proceed with a virgin Pi/Trixie to add my four Flight Feeders, AirSpy 2 etc.

Thanks & kind regards,

-=Glyn=-

Well, there is this thread about trixie and piaware.

abcd567 also wrote somewhere how to add different feeders to one install, not sure if is in this one, as well.

Maybe it is also worth to take a look at ADSB.im, it is a convenient way to feed different aggregators and a lot of other stuff, maybe you could consolidate the amount of Pis you are using.

1 Like

By far the easiest way: Use a premade image:

https://adsb.im

Oh someone already pointed it out.
There is also new sites using the tar1090 interface you would have seen on adsbexchange that are easy to add with the image:
https://adsb.lol / https://globe.airplanes.live / https://globe.adsb.fi and a couple others.

Airspy R2 will work out of the box.
If you have a filtered LNA that’s recommended for ADS-B with the airspy but it will work fine without it.

1 Like

Hi @GlynH
Glad to see you after a long gap. How are you doing?
Here is the how-to you require.

(1) Installing dump1090-fa & piaware on Raspberry Pi OS Trixie

Flightaware has not (yet) released their packages for Trixie. However you can still Install pre-built packages from my PPA (Personal Package Archieves) on Github. I have built these packages using Flightaware source code, and have tested these and running on two of my RPis for more than 2 months without any issue.

(1.1) Issue following 3 commands to add list of packages at my PPA, to your RPi’s apt sources list
NOTE: First two commands are very long, and their right-most part may not be visible. Please scroll right to see and copy these in full

sudo wget -O /etc/apt/sources.list.d/abcd567a.list https://abcd567a.github.io/debian13/abcd567a.list 
sudo wget -O /etc/apt/keyrings/abcd567a-key.gpg https://abcd567a.github.io/debian13/KEY2.gpg 
sudo apt update  

 

(1.2) Issue following commands to install dump1090-fa, piaware & piaware -web:

sudo apt update  

sudo apt install dump1090-fa   

sudo reboot  

sudo apt install piaware  

sudo apt install piaware-web  


(1.3) Configure piaware:

sudo piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  
sudo piaware-config allow-manual-updates yes  
sudo piaware-config allow-auto-updates yes  
sudo systemctl restart piaware  

 

(1.4) IMPORTANT: As you will install pre-built packages by this method from my PPA, in order to avoid any conflict with Flightaware Repository in future (when they release their package for Trixie), I strongly recommend that after installation of packages is comleted and running ok, remove entry of my PPA from your RPi’s apt sources list. This can be done by following commands:

sudo rm /etc/apt/sources.list.d/abcd567a.list

sudo rm /etc/apt/keyrings/abcd567a-key.gpg

sudo apt update

(2) Install Graphs by @wiedehopf

sudo bash -c "$(curl -L -o - https://github.com/wiedehopf/graphs1090/raw/master/install.sh)"

(3) Install Additional Feeders

(3.1) Flightradar24 Feeder

wget -qO- https://fr24.com/install.sh | sudo bash -s

After completing email. feeder-key, replied YES, to following question:
Would you like to use autoconfig (*yes*/no)$: yes

Next issued following commands:

sudo systemctl enable fr24feed

sudo systemctl restart fr24feed

(3.2) Planefinder Feeder

wget http://client.planefinder.net/pfclient_5.3.29_arm64.deb
sudo dpkg -i pfclient_5.3.29_arm64.deb

After installation completed, in browser opened following address, and completed configuration:

IP-of-DebianPC:30053

(3.3) AIS-catcher

sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/install-aiscatcher/master/install-aiscatcher.sh)"

(3.4) Planeplrotter uploadedr - ppup1090

sudo bash -c "$(wget -O - https://github.com/abcd567a/ppup1090/raw/master/install-ppup.sh)"

(3.5) RadaBox24

The Radarbox24 feeder is NOT available for Trixie
It is available for for Bookworm, but their repository & installation script are designed for Bookworm & Bullseye, and fail on Trixie.

Following is the workaround for installing rbfeeder on RPi (arm64) running OS Trixie:

(3.5.1) Install tools
sudo apt install dirmngr gnupg

(3.5.2) Set apt
Note: Following three (3) commands are very long. Scroll right to see and copy these in full

gpg --keyserver keyserver.ubuntu.com --recv-keys F2A8428D3C354953  

gpg --export --armor F2A8428D3C354953 | sudo gpg --dearmor -o /etc/apt/keyrings/rb24.gpg  

echo "deb [signed-by=/etc/apt/keyrings/rb24.gpg] https://apt.rb24.com/ bookworm main" | sudo tee /etc/apt/sources.list.d/rb24.list 

(3.5.3) Update apt and install rbfeeder:

sudo apt update
sudo apt install rbfeeder

(3.5.4) After installation is completed, signup as follows:

sudo systemctl restart rbfeeder

After a few seconds, RBFeeder will connect to the AirNav servers and you can view your sharing-key with this command:

sudo rbfeeder --showkey

If you already have a sharing-key from a previous installation, you can set the same key using this command:

sudo rbfeeder --setkey ‹your sharing key›

(3.5.5) Install mlat-client
The installation of mlat-client from RB24 repository by command sudo apt install mlat-client fails with following error message:
mlat-client:arm64 Depends python3 (< 3.12) but this is not installable (Trixie apt provides python 3.13)

Solution: Build & install mlat-client using source code

sudo apt install git build-essential debhelper dh-python python3-dev python3-setuptools python3-pyasyncore

git clone https://github.com/mutability/mlat-client  

cd mlat-client 

sudo dpkg-buildpackage -b --no-sign 

cd ../  

sudo dpkg -i mlat-client_0.2.13_*.deb  

sudo systemctl restart rbfeeder  

And that is all. The rbfeeder installation is completed.

Check status by following command

sudo systemctl status rbfeeder

 

Please see this post:

 

1 Like

@abcd567 I came across this today while exploring tcltls-rebuild on GitHub.

https://core.tcl-lang.org/tcltls/tktview?name=6dd5588df6

It seems the problem was finally fixed in October. Does this mean that the apt-mark hold tcl-tls associated with your version of PiAware for Trixie is no longer required?

I just now removed hold from tcl-tls and isuied sudo apt update and sudo apt upgrade, and the package i built (tcltls-rebiilt) was immediately replaced by tcl-tls from Debian repository.

apt-cache policy tcl-tls
tcl-tls:
  Installed: 1.8.0-2
  Candidate: 1.8.0-2
  Version table:
 *** 1.8.0-2 500
        500 http://deb.debian.org/debian trixie/main arm64 Packages
        100 /var/lib/dpkg/status

I then rebooted Pi and after reboot, checked pisware. It reported failure due to TLS. Please see screenshot attached below.

Now there’s 4 packages that can’t be upgraded in Trixie:

pi@trixie:~ $ sudo apt update
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://deb.debian.org/debian-security trixie-security InRelease
Hit:4 http://archive.raspberrypi.com/debian trixie InRelease
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
pi@trixie:~ $ apt list --upgradable
libcamera-ipa/stable 0.6.0+rpt20251202-1 arm64 [upgradable from: 0.5.2+rpt20250903-1+b1]
librpicam-app1/stable 1.10.1-1 arm64 [upgradable from: 1.10.0-1]
rpicam-apps-core/stable 1.10.1-1 arm64 [upgradable from: 1.10.0-1]
tcl-tls/stable 1.8.0-2 arm64 [upgradable from: 1.7.22-2+fa1]
pi@trixie:~ $ sudo apt upgrade
Not upgrading:
  libcamera-ipa  librpicam-app1  rpicam-apps-core  tcl-tls

Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 4

I guess it doesn’t matter though --those 3 other packages seem to be related to camera software, which I’m not using.

Thanks - I will leave the hold in place.

If you get sick of the Not upgrading: message

sudo apt remove libcamera-ipa librpicam-app1 rpicam-apps-core

Ok. Also this could be a phased upgrade. Maybe wait a few days to get the upgrade. I think I have seen this before.

1 Like