Just a note of caution for Airspy feeders who run the Debian Package Add-on and who have not upgraded yet - based on my own dumb mistake…
If you do the upgrade via apt upgrade, do not answer Y when asked about Configuration file ‘/etc/default/dump1090-fa’:
Preparing to unpack .../09-dump1090-fa_5.0_armhf.deb ...
Unpacking dump1090-fa (5.0) over (4.0) ...
Preparing to unpack .../10-piaware_5.0_armhf.deb ...
Unpacking piaware (5.0) over (4.0) ...
Preparing to unpack .../11-piaware-repository_5.0_all.deb ...
Unpacking piaware-repository (5.0) over (4.0) ...
Setting up chromium-codecs-ffmpeg-extra (88.0.4324.187-rpt1) ...
Setting up piaware-repository (5.0) ...
Setting up python3-pygments (2.3.1+dfsg-1+deb10u1) ...
Setting up dump1090-fa (5.0) ...
Configuration file '/etc/default/dump1090-fa'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** dump1090-fa (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/default/dump1090-fa ...
Configuration file '/etc/lighttpd/conf-available/89-dump1090-fa.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** 89-dump1090-fa.conf (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/lighttpd/conf-available/89-dump1090-fa.conf ...
The user `dump1090' is already a member of `plugdev'.
Enabling lighttpd skyaware module..
Enabling skyaware: ok
Run "service lighttpd force-reload" to enable changes
Restarting lighttpd..
This overwrites the airspy_adsb specific changes to the dump1090-fa config file and puts your feeder off the air.
It took me a while to work out what I had done. If you end up in this position, you need to edit /etc/default/dump1090-fa to restore the airspy_adsb settings and restart dump1090-fa.
sudo nano /etc/default/dump1090-fa
sudo systemctl restart dump1090-fa
This is what my file looks like post edit:
# dump1090-fa configuration
# This is sourced by /usr/share/dump1090-fa/start-dump1090-fa as a
# shellscript fragment.
# If you are using a PiAware sdcard image, this config file is regenerated
# on boot based on the contents of piaware-config.txt; any changes made to this
# file will be lost.
# dump1090-fa won't automatically start unless ENABLED=yes
ENABLED=yes
RECEIVER_OPTIONS="--net-only"
DECODER_OPTIONS="--max-range 360 --fix"
NET_OPTIONS="--net --net-heartbeat 60 --net-ro-size 1300 --net-ro-interval 0.2 --net-ri-port 0 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005
JSON_OPTIONS="--json-location-accuracy 1"
# Use a machine-specific wisdom file if it exists
if [ -f /etc/dump1090-fa/wisdom.local ]
then
RECEIVER_OPTIONS="${RECEIVER_OPTIONS} --wisdom /etc/dump1090-fa/wisdom.local"
fi
I’m not sure how the Wisdom File section of the config file is necessary for an airspy_adsb setup, but my feeder seems to be working with it in the file.
