PIXEL desktop on PiAware

FlightAware ADS-B Flight Tracking
11

@abcd567 I installed 32-bit Raspbian (not 64) as I wasn’t sure if all the FA/FR24 stuff was compatible with a 64bit OS.
I recreated my install “one step at a time” and checked as it went.

  1. I loaded the OS (32-bit Bullseye) and confirmed that VNC is working,

  2. I loaded PiAware, confirmed that it’s working (sending data to FA) and that VNC is working.

  3. My next step was to activate FR24 per (Re-imaging Made Easy) Section 3.2
    I created the fr24feed.ini file and populated it with the previous data, and then executed:

sudo bash -c "$(wget -O - https://repo-feed.flightradar24.com/install_fr24_rpi.sh)"

and what I get back finishes like…

Hit:1 http://flightaware.com/adsb/piaware/files/packages bullseye InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
dirmngr is already the newest version (2.2.27-2+deb11u2).
The following package was automatically installed and is no longer required:
  libfuse2
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.WqM7tDuxwc/gpg.1.sh --recv-key --keyserver keyserver.ubuntu.com C969F07840C430F5
gpg: keyserver receive failed: Server indicated a failure
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.XADxvxJvr5/gpg.1.sh --recv-key --keyserver pool.sks-keyservers.net C969F07840C430F5
gpg: keyserver receive failed: Server indicated a failure
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
Executing: /tmp/apt-key-gpghome.17F6gLHavv/gpg.1.sh --recv-key --keyserver pgp.mit.edu C969F07840C430F5
gpg: keyserver receive failed: Server indicated a failure
pi@PiPlane:~ $

multiple “failures” and then it stops.

The steps on the above-linked webpage, state that the command should keep running and start the configuration process. Then I should end that process via (Ctrl+C), and start up the fr24feed via:

sudo systemctl restart fr24feed

However, I never get a chance to Ctrl+C, it just dies. If I try to start the process, I get back:

pi@PiPlane:~ $ sudo systemctl restart fr24feed
Failed to restart fr24feed.service: Unit fr24feed.service not found.

At this point VNC is still working.

Then I did “option 2” from the Fr24 manual:

wget https://repo-feed.flightradar24.com/rpi_binaries/fr24feed_1.0.23-8_armhf.deb
sudo dpkg -i fr24feed_1.0.23-8_armhf.deb
sudo systemctl restart fr24feed

and it seemed to work - including asking if I wanted to keep the existing config file.

I rebooted, and now it seems to be working - both FA, FR24, and VNC (?)

So - VNC is working now - when (I think) it wasn’t working on the identical effort yesterday. :man_shrugging:
I am not going to try a third time, though, I’m taking “success” and running with it.

But as to getting FR24 functional, I again confirmed that the “Option 1” approach doesn’t work for me. I’m not sure if that’s due to the 32/64 bit question, maybe a Buster/Bullseye issue, or something else. The fact others haven’t complained makes me wonder what’s wrong with my setup, but I’ve made copious notes to myself so that if/when I have to do this again, I’ll have a recipe for getting to the end.

Again, I greatly appreciate all the time and attention you’ve provided here (and in other threads in the various forums FA and FR24 that I’ve been reading).

Regards,
–Mark