This release ends support for Jessie OS . If you are still on Jessie, we highly encourage you to re-image your SD card with PiAware 7 or upgrade your OS to continue receiving updates.
If you are re-imaging an existing setup, be sure to back up your SD card and reclaim your unique feeder-id after re-imaging. Re-imaging and reclaiming instructions can be found at PiAware - Upgrade PiAware to the latest version - FlightAware. Note that if you are testing the new Wi-Fi setup via web or mobile device without reclaiming your feeder-id, it will automatically claim a new feeder-id on your FlightAware account. You should set your existing feeder-id via piaware-config.txt if you want to resume your statistics.
The official release will be available for update in a few weeks.
If you have some spare hardware laying around or have some time over the holidays, try it out and and let us know if you see any issues. Please provide which Raspberry Pi model you are testing on. We’re looking for users with Raspberry Pi Zero, Pi Zero 2 W, Pi 3B+, and Pi 4s.
Hmmm … first pass has been a failure.
Site 81771
Not sure it the Pi is a 3b or 3b+.
Burnt a clean image and only added UUID and SSH. The Pi appears not to be booting.
Wrote Piaware SD Card image ver 7.0 to 8 Gb microSD card
Added file ssh in /boot partition
Added WiFi credentials in /boot/piaware-config.txt
Slipped microSD card into RPi Model 4, 1 Gb,
Could SSH, but now MAC address for WiFi is that which was previously (ver 6.1) for Wired Connection.
Tried to claim from Android Phone’s browser, using Bluetooth, but failed.
Finally edited file /boot/piaware-config.txt and at bottom added following line (existing feeder-id) and rebooted feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
I flashed 2 Mode-S nodes (Raspberry Pi 2 Model B Rev 1.1) and 1 UAT node (Raspberry Pi 3 Model B Rev 1.2). All 3 are connected via wired Ethernet. This is the only unexpected thing I’ve encountered.
pi@piaware:~ $ sudo apt update
Get:1 http://flightaware.com/mirror/raspbian/raspbian bullseye InRelease [15.0 kB]
Ign:2 http://flightaware.com/adsb/piaware/files/packages bullseye InRelease
Get:3 http://flightaware.com/mirror/raspberrypi/debian bullseye InRelease [23.5 kB]
Err:4 http://flightaware.com/adsb/piaware/files/packages bullseye Release
404 Not Found [IP: 206.253.81.28 80]
Get:5 http://flightaware.com/mirror/raspbian/raspbian bullseye/main armhf Packages [13.2 MB]
Get:6 http://flightaware.com/mirror/raspberrypi/debian bullseye/main armhf Packages [242 kB]
Reading package lists... Done
E: The repository 'http://flightaware.com/adsb/piaware/files/packages bullseye Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Thanks @obj and @eric1tran
Just to get familiar with this new and very useful Bluetooth feature, tonight I will try both the options suggested by @eric1tran and post the results.
Using ssh twice I changed the password, both occasions it said successful but both occasions I had to login with the default password as it kept indicating wrong password.