Docs · 1 min read

Troubleshooting

Common installer, ADS-B and weather-station issues, and how to recover from each of them.

The installer keeps offering a full Allsky reinstall

An earlier release incorrectly looked for Allsky's retired config/config.sh marker. If your installer repeatedly offers a full Allsky reinstall, do not accept it. Update PiSky and rerun the wrapper instead:

cd ~/pisky
git fetch origin
git pull
./install-pisky.sh

The corrected detector recognises config/settings.json, config/options.json, the Allsky service, and completed/reboot-pending status states. It then installs the missing PiSky control helper, WeeWX and ADS-B components without touching Allsky again.

No aircraft showing up

Confirm the decoder is actually producing aircraft.json before assuming PiSky is at fault — open /admin/?page=flights to check receiver status, range, targets and message counts. For Mode-S Beast receivers, check ls -l /dev/beast; if nothing appears, the udev rule hasn't matched your receiver and you should set the serial device to the real port instead (usually /dev/ttyUSB0).

Weather station not updating

Reopen the guided preset in PiSky Setup and use Check for live weather data — it will tell you whether PiSky has received a recent observation. Double check the station's custom server settings point at the Pi's current IP or hostname and the configured listener port.