Hi everyone,
on my stats page i am getting an “anomaly detected” information saying that i am running V9 and should upgrade to V10.
Any way to disable that?
Jetvision devices cannot be upgraded directly, the package is maintained by Jetvision and they are testing it currently.
Not a big deal, more a “cosmetic” problem, but it still irritates me whenever i am accessing my profile 
I don’t think that you can remove that notification.
I’m on 10.0.1 and it also notifies me that 10.1 is available but when running the update commands it does not update to 10.1.
So I think the new version isn’t yet available for download or it hasn’t been propagated to the download server yet.
Oh well next try tomorrow 
Doesn’t the X in the top right of the update banner function? It appears to be selectable.
The update functions but the 10.1 version isn’t found when you run the update.
In the changelog description iti is there but not in the actual piaware files itself.
Interesting. Mine has a completely different banner format.
My understanding is that unless the current installation is on the current OS, no automatic update is possible, a re-image of the SD card is required.
I’m running bookworm and I can’t update from 10.0.1 to 10.1 ( Package installation).
If the package is availble it would be picked up with the following command once logged into the Pi
sudo apt update
sudo apt upgrade -y
The system tells me all packages are up todate so 10.1 isn’t available yet.
pi@raspberrypi28tom:~ $ sudo apt update
Hit:1 http://deb.debian.org/debian bookworm InRelease
Get:2 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB ]
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:5 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:6 https://repo-feed.flightradar24.com flightradar24 InRelease
Hit:4 https://www.flightaware.com/adsb/piaware/files/packages bookworm InRelease
Fetched 48.0 kB in 5s (10.6 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
On github it shows V10.1 released last week:
Maybe the package hasn’t been built so far.
In that folder the config.tcl of the sources is the only file beeing updated in a single line: where they deleted the line with 10.1-dev and replaced it with 10.1
set serverRetryIntervalSeconds 60
set piawareVersion 10.1
set piawareVersionFull 10.1~dev
set piawareVersionFull 10.1
# how many seconds with no messages received from the ADS-B receiver before
# we will attempt to restart dump1090
Maybe @eric1tran can say something about it as the maintainer of the package/the file
Could be that this is valid for the Piaware image only
There is something odd going on.
The anomaly warning is still there stating that they need to be upgraded to 10.1.
That doesn’t answer my initial question. I cannot upgrade as the package need to be maintained by the vendor of my device (Jetvision). So the upgrade notification is simply not applicable to me and i don’t need it.
If you cannot stop the upgrading notification, then simply ignoring the notification will give you peace of mind.
That has been clarified already in the first replies of this thread
Hi foxhunter,
Those Jetvision Radarcape and Air!Squitter (with commercial license) devices are excellent. I knew they fully supported FA with their internal software, but did not realize until looking at your station today that they clearly identified as below.
Feeder Type: PiAware (Air!Squitter) 9.0.1
OT: We had a similar thing years ago with another network and Jetvision internal software. The Jetvision receivers had internal software that would upload to the PlanePlotter network, but would not support mode-A/C and mode-S mlat on the PP network. Most of the Radarcape users supported mlat through other software. A year or so the Pi software ppup1090 was updated to handle the Radarcape default GPS timestamps. That allowed people to pull data from a Radarcape and support mlat from a separate Pi. At the time, they also released a Buster 32-bit version of ppup1090 that could be run directly on the Radarcape. That connects to beast binary port=10003 and fully supports mode-a/c and mode-s mlat.
None of that matters to you! However, if you REALLY wanted to, you could always disable the Radarcape internal FA support, and simply install the normal FA packages directly on the Radarcape itself. I’m not suggesting you do this, but it’s just something interesting to think about. You probably already know this, and might have already tested this.
Regards,
-Dan
I think at the end FA doesn’t care which device is in use. And that’s understandable.
As said, it’s not really an issue, more a “cosmetic” problem.
I can simply stop looking at my stats, then i won’t see it any more 
I’ve pinged Günter from Jetvision about their upgrade plans.
The notification seems to be gone again from the anomalies section ;-), I don’t have it anymore at the moment.
That notification was only showing when it was a major version out of date or something like that, not for minor versions?
So they probably fixed it to only show when it’s significantly out of date.
Agreed for the Pi with 10.0.1 on it.
