Give command sudo piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
where xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx is the Unique Identifier you have copied from your Flightaware stats page.
If the command is executed successfully, it will rerturn following
Set feeder-id to xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx in /etc/piaware.conf:9
.
Restart piaware for implementing feeder id sudo systemctl restart piaware
.
Wait 10 minutes, then give following command to check status sudo systemctl status piaware -l
If it is feeding Flightaware, last few lines will be like following:
9 msgs recv'd from dump1090-fa; 9 msgs sent to FlightAware
63 msgs recv'd from dump1090-fa (54 in last 5m); 63 msgs sent to FlightAware
69 msgs recv'd from dump1090-fa (6 in last 5m); 69 msgs sent to FlightAware
Hi abcd567! Thanks for remembering! Life been a little hectic lately - and have had no real issues up until now but have been lurking occasionally on all thee forums.
I had a good look through the forums before I posted so had already tried that command.
Results
pi@piaware:~$ sudo piaware-config feeder-id 3d7f7167-346d-43ec-a805-33dcfdbfca43
piaware-config options:
-user value specify the user name of a valid FlightAware account <>
-password interactively specify the password of the FlightAware account
-autoUpdate value 1 = allow FlightAware to automatically update software on my Pi, 0 = no <>
-manualUpdate value 1 = allow me to trigger manual updates through FlightAware, 0 = no <>
-mlat value 1 = allow multilateration data to be provided, 0 = no <>
-mlatResults value 1 = send multilateration results to localhost:30004, 0 = no <>
-mlatResultsFormat value format(s) to generate mlat results in, ‘default’ to reset to the default format <>
-start attempt to start the ADS-B client
-stop attempt to stop the ADS-B client
-restart attempt to restart the ADS-B client
-status get the status of the ADS-B client
-show show config file
– Forcibly stop option processing
-help Print this message
-? Print this message
I think the problem is the install is a very old version and logs into Flightaware using the MAC address for id. What intrigues me is I have tried 2 different restores from 2 separate dates with the same result.
Might have to reinstall…
BTW hope you and your family have a great Festive season!
Both the OS and piaware are too old.
The clean solution is a fresh install (i.e. format the USB memory stick, and install latest Raspbian and all other software).
You can install dump1090-mutability (or dump1090-fa) + piaware + planefinder data feeder + flightradar24 data feeder + performance graphs using Automated method given here:
If it is of any help, long ago I decided to separate the RasPi apps onto their own boxes. So, I have one that runs the ADSB stuff like FlightAware, FR24, adsbexchange etc. Then another Pi for some temperature monitoring, and another for webserving, another for Kodi, and two more for DNS (PiHole) …don’t tell my wife I bought so many! But really, they are so inexpensive it was just easier from a software upgrading standpoint to separate them.
.
During this trial upgrade, I noted following two things:
For creating folder autostart the command given in the raspberrypi forum is: mkdir /home/pi/.config/autostart
This command fails as (1) sudo is missing, and (2) folder .config in path to folder autostart does not exist.
Use following command, in which argument -p creates any folders in path if it does not exist. A better alternative to -p is -pv which announces all the directory created, so that you can see what directories are created.
sudo mkdir -p /home/pi/.config/autostart
OR better
sudo mkdir -pv /home/pi/.config/autostart
Newly created folder .config is not listed when ls or dir command are issued. However command cd /home/pi/.cofig moves prompt to folder .config
(B) Upgrading Piaware from 2.1 to 3.5.3 (After successful upgrade from Wheezy to Jessie)
First purge the existing old version 2.1-5 of Piaware
This will download and install PiAware and required dependencies on your Raspberry Pi.
sudo apt-get update
sudo apt-get install piaware
This will enable automatic and manual (web-based, via your request) PiAware software updates. These updates are disabled by default. To leave updates disabled, skip this step.
Good luck!
When yesterday I upgraded from Wheezy to Jessie, it took more than an hour to complete.
At one point it hanged for very very long time, and I had to reboot Pi and once again issue command sudo apt-get dist-upgrade. I then got responce " the dpkg process was interrupted, please try command sudo dpkg-reconfigure -a. I issued this command and after its completion, again issued command sudo apt-get dist-upgrade.
.
Actually I do not have any Pi with wheezy. All are either Jessie or Stretch.
The upgrade I did was not meant to fix my problem, but was meant to test the upgrade method, before I recommend it to you and others in this forum.
Only yesterday I downloaded and burned wheezy on a spare blank microSD card, and then upgraded it to Jessie to test the method.
After test, I have formatted the test microSD card, and am keeping it as reserve blank microSD card.
.
I dont know why mine took so long. My microSD card is class 10 with 25 Mb/sec write and 50 Mb/s read speed. Maybe your USB is 3.0 and high speed (50 Mb/sec write and 100 Mb/sec read speed), making upgrade faster.
.
.
Glad to know that you could fix it and your system is up and running again.
PiAware version 2 systems will not be able to connect to FlightAware soon. I think the count was something around 100 sites still connected to FlightAware with the older software.
If you have any trouble upgrading or flashing a new SD image you can use the discussion boards or email flightaware at adsbsupport@flightaware.com
@david.baker:
You are right David. Re-flashing with latest image is the cleanest, trouble free, and long-lasting solution.
The OP (original poster) had two-fold problem:
Piaware version 2.1-5
Raspbian 7 Wheezy
As you have suggested, I also initially suggested OP to flash latest Raspbian image and install latest Piaware 3.5.3 (package install). The OP did not like this as he had many other software running on Pi and did not want to re-install everything.
In view of reluctance of OP to flash new image, I posted a method which comprised of following 3 steps:
Upgrade existing OS from Wheezy to Jessie WITHOUT re-imaging.
Thanks for the advice David. And thank you abcd567.
The upgrade has gone well. I understand the purist stance however the real world dictates that hacks are sometimes necessary - and this one suited my purposes.