That’s great news! tar1090 is a nice alternative to the stock SkyAware.
Got this installed on a RasPi3 - seemed to work ok. Used the “Package” install method, over top of an existing 3.8.1 install. One gotcha that I’ve not yet figured out - had to disable the apt-proxy (apt-cache-ng on a different machine on my network) to get the install to run. Won’t say I’m an apt-cache-ng expert. Any one have any suggestions?
What failed when the proxy is in place? The FA repo should just be a fairly standard apt repository (it’s built by reprepro)
I just updated Piaware with no issues. I installed new cable to the antenna outside and coverage is up to 200 Miles so far.
1 Like
Thank you so much, again. 4.0 up and running!!!
I just update my Pi with 4.0. I noticed it was off line and did some checking.
I used WiFi to connect and for some reason after the update, it is no longer connecting to my wifi network. I brought it inside and connect via a LAN cable and it works.
I am guessing my WiFi information got lost.
How do I change the WiFi settings and what file do I edit and how?
THANKS!
@behrcowboy Do the following commands return the correct credentials?
piaware-config -show wireless-ssid
piaware-config -show wireless-password
To set these config settings, enter this and replace the ssid/password with the correct credentials
piaware-config wireless-ssid ssid
piaware-config wireless-password password
sudo piaware-restart-network
Or you can just edit those settings in piaware-config.txt file manually
Well, Ansible tells me: “Failed to update apt cache” but that probably isn’t what you want to know. If I run an “sudo apt-cache update” manually, I get:
"Err:4 http://flightaware.com/adsb/piaware/files/packages buster InRelease
Connection failed [IP: my.Proxy.IP.addr 3142]"
Reading package lists... Done
W: Failed to fetch http://flightaware.com/adsb/piaware/files/packages/dists/buster/InRelease Connection failed [IP: my.Proxy.IP.addr 3142]
W: Some index files failed to download. They have been ignored, or old ones used instead.
Digging around some in logs on the proxy server, I see:
<br>
Checking/Updating flightaware.com/adsb/piaware/files/packages/dists/buster/InRelease...
<span class="ERROR">500 Connection failure: Connection timed out</span>
I can ping Flightaware.com from the proxy.
I can fetch that URL ok (and presumably your piaware can reach it if it goes direct); not sure why only your cache is having problems reaching it.
Thank you.
Both the SSID and the password are correct using those commands.
I tried rebooting the Pi and I get both the eth0 down and wlan0 down on the boot up screen.
Any other suggestions?
Not sure either. Is pretty vanilla apt-cacher-ng install on debian. Manual “wget” seems to work ok on both the client and the cache machine.
Makes sense.
I have a PiAware SD setup at a small airport. The pilots have Stratux/Stratus units in the planes. Since I saw the feature in PiAware, I thought it would be cool to enable it so the pilots could look at the PiAware output on Foreflight at their desk. Just another way to see local airtraffic before heading out to the plane.
I like the new features. Is there a way to retain custom range ring settings?
Right, long thread and I haven’t had a chance to read all the way through.
I updated my main receiver using the option through the stats page and now it shows 4.0
I’ve rebooted the Pi and cleared my cache but SkyAware still shows 3.8.1
I’m not using an FA image, just a plain Buster Lite with everything added on.
Have I missed something?
Are there any .deb packages for AMD64 platforms?
I assume you did not miss a lot between all the success messages.
Same OS here, but no problem SkyAware V4.0 was up and running directly after the upgrade was finished.
Try restarting dump1090-fa, piaware and lighttpd.
Yes, you did not upgrade dump1090-fa which generates the SkyView map.
The dump1090-fa is still version 3.81, hence it is showing 3.8.1 on the map.
Please see this post:
I sent the “Upgrade and restart PiAware” command, but now the device is no longer registering with FlightAware. My device shows as disconnected (red) on the ADS-B page, but when I click the “PiAware SkyAware” link I can still connect to the device and see activity. Has anyone else had this problem?
I tried restarting by unplugging and plugging it back in, but nothing changed (other than the PiAware SkyAware page went down temporarily).
For me it was working by simply run
sudo apt update
sudo apt upgrade
The FA repository updated both Piaware and dump1090-fa in one step.
This was working on both of my devices without any additional interaction
Thanks, I knew it would be something obvious. I had to do a manual apt-get update and upgrade first because it failed first time but it’s all good now.