ketilmo / balena-ads-b Goto Github PK

It would be nice if a way to push data to VRS (Virtual Radar Server) could be created. This means that the receiver could be installed in a remote location.

Refactor the FlightAware integration to match approach used in the PlanerFinder integration that's part of this repo.

Hey
It be nice if you add https://theairtraffic.com/
To the mix

Refactor the Flightradar24 integration to match approach used in the PlanerFinder integration that's part of this repo.

opensky-network Statistics
opensky-network - started on Mon Dec 25 10:00:33 2023
opensky-network - running since 1d, 00h:27m:48s
opensky-network
opensky-network Receiver
opensky-network - 221289 frames received (2.51 /s, 0.93 /s)
opensky-network - 88127 [ 40%] Mode-A/C (1.00 /s, 0.93 /s)
opensky-network - 43185 [ 20%] Mode-S Short (0.49 /s, 0.00 /s)
opensky-network - 89977 [ 41%] Mode-S Long (1.02 /s, 0.00 /s)
opensky-network - 10539 [ 8%] type 0 (0.12 /s, 0.00 /s)
opensky-network - 3893 [ 3%] type 4 (0.04 /s, 0.00 /s)
opensky-network - 3312 [ 2%] type 5 (0.04 /s, 0.00 /s)
opensky-network - 25441 [ 19%] type 11 (0.29 /s, 0.00 /s)
opensky-network - 279 [ 0%] type 16 (0.00 /s, 0.00 /s)
opensky-network - 72364 [ 54%] type 17 (0.82 /s, 0.00 /s)
opensky-network - 18 [ 0%] type 18 (0.00 /s, 0.00 /s)
opensky-network - 12275 [ 9%] type 20 (0.14 /s, 0.00 /s)
opensky-network - 5041 [ 4%] type 21 (0.06 /s, 0.00 /s)
opensky-network - 0 [ 0%] status (0.00 /s, 0.00 /s)
opensky-network - 0 [ 0%] unknown (0.00 /s, 0.00 /s)
opensky-network - 88127 [ 40%] filtered (1.00 /s, 0.93 /s)
opensky-network - 0 [ 0%] Mode-S filtered (0.00 /s, 0.00 /s)
opensky-network - 221289 unsynchronized frames
opensky-network
opensky-network Buffer
opensky-network - 0 queued messages (current)
opensky-network - 21 queued messages (max)
opensky-network - 0 discarded messages (current)
opensky-network - 0 discarded messages (overall)
opensky-network - 0 discarded messages (in worst overflow situation)
opensky-network - 199 messages in pool (Usage 0.00%)
opensky-network - 0 dynamic pools (current)
opensky-network - 0 dynamic pools (overall)
opensky-network - 0 dynamic pools (max)
opensky-network - 0 uncollected dynamic pools
opensky-network - 6 flushes
opensky-network - 0 Garbage Collector runs
opensky-network
opensky-network Network
opensky-network - currently online
opensky-network - 88067 [100%] seconds online (overall)
opensky-network - 5 disconnections
opensky-network - 6 connection attempts
opensky-network - 2858500 bytes sent (32.46/s)
opensky-network - 36 bytes received (0.00/s)

Seems like i am getting alot of disconnections any other people having the same issue

Thanks for your work!

It would be very interesting and also helpful if you could integrate the graphs1090 service from wiedehopf

See here: https://github.com/wiedehopf/graphs1090

This gives us various graphs for information about the proper work of dump1090

Thanks

Daniel

Since a few weeks I am not able to update my balena ADS-B device anymore.
It is a raspberry pi 3 and is running Supervisor Version15.0.0 and Host Os Version 4.0.16.
I want to update the system to SV 15.0.2 and Host OS Version 4.1.1. I select i the dashboard summarythe SV and select 15.0.2. It start to apply the update but it always fails.

After that I tried to create a new release which instaled correctly but did not update to newer versions of the SV nor the Host OS.

What can I do to get the latest update installed and working?

Hi Ketil,

Based on my experience with Stratux receiver, I thought it might be useful to add GPS module support to your project.
For example VK172 USB or similar module for GPS/GLONASS. It cost ±5$ and gives mobile users, who use run receiver from a car or vessel, flexibility with GEO Variables. No need to set LAT and LON if GPS module detected on the device.

B.R.
Michael

When I click on "Web interface: View live data" link on my https://flightaware.com/adsb/stats/user/medicusnocte#stats-131113 Flightaware status page, it takes me to wrong link: http://172.17.0.5:8080/

The device is actually on http://10.0.1.187:8080/ and when I go there, the live data comes up correctly.

How do I get my instance of balena-ads-b to tell Flightaware what the correct local link is?

As mentioned in #52 – add instructions to the Readme about how to upgrade to the latest version.

It would be great if you could support CZADSB service, and share flying data with them.

I tried to update to the latest version of the supervisor version and also the host os version.
The host OS version updated without any problem. After that the system became stuck in online (VPN only) mode.
I could not find what to do to get the system running in normal state again.

As I have setup all the radars I do not want to start from scratch.

See #45 for details.

ads-b-raspberrypi_release-log_radarbox-437000f.txt

I created a new application using the 'Deploy with Belena' link but during build it fails to build the radarbox service.
The device chosen was Raspberry Pi 3. I tried deleting the application and re-creating again but it failed building again at the same spot.

Attached are the build logs for radarbox and a screenshot of the error.

dump1090-fa Receiver longitude is set: 3.7641157410193986
dump1090-fa
dump1090-fa Settings verified, proceeding with startup.
dump1090-fa
dump1090-fa Fri Jul 30 18:58:26 2021 UTC dump1090-fa 5.0 starting up.
dump1090-fa rtlsdr: no supported devices found.
dump1090-fa Verifying settings...
dump1090-fa
dump1090-fa Receiver latitude is set: 51.04xxxxxxxxxxxxxxxx
dump1090-fa Receiver longitude is set: 3.76xxxxx
dump1090-fa
dump1090-fa Settings verified, proceeding with startup.
dump1090-fa
dump1090-fa Fri Jul 30 18:59:31 2021 UTC dump1090-fa 5.0 starting up.
dump1090-fa rtlsdr: no supported devices found.

I'm using the flightaware pro stick plus (since april 2021) on a Raspberry Pi4 4GB
Update: I've tried swapping the stick from USB ports - no results
Also tried another RTLSDR stick (the one I used before), still same error.

Any change we could see ADS-B exchange being added to the sending containers? It supports dump1090.

Instructions: https://www.adsbexchange.com/how-to-feed/

The system is running and all are sending data. Only for the Flightaware (Piaware) it does not sent MLAT data. For the other services this is running normally. I have restarted the Flightaware service and than it switches on but shortly after is is red again.
Please have a look what is going on and how to resolve the issue.

Dear,

I believe that a lot of people are using your fantastic solution on airports, like as I 🙂

Have you thought about adding a new feature, namely intercepting communications at the airport's frequency?

Something like in the picture:

Thank you

There are instructions for compatibility here: https://www.balena.io/blog/introducing-balenahub-an-easier-way-to-find-and-publish-apps-and-projects-for-edge-devices/, let me know if i can help at all!

Hello there,

I am trying to configure a new flight feeder from scratch, and I have an issue with the FlightRadar24 config part.
I am currently at 4.B.14: When asked for your receiver's IP address/hostname, enter dump1090-fa.

When I try to do that, I get an error saying the value is incorrect, see image below.

Does anyone know what I'm doing wrong and how to fix it? 😁

Balena's variables are V(x) now. Should update this reference.

Implement ADS-B Exchange Support, along the same lines used in the PlanerFinder integration that's part of this repo.

range decreased 176 to 26nm with update

Just received an email from Flightradar24. They are asking for all receivers (that aren't directly from them) to disable MLAT if said receivers are sharing to multiple networks.

https://forum.flightradar24.com/forum/radar-forums/flightradar24-feeding-data-to-flightradar24/213550-disable-mlat-if-sharing-with-other-networks

Is there a balena variable we can set for this?

So i have set up the abs flight tracker on balena cloud everything is setup up but when i try to access the web page it says Bad Gateway thats all

Thanks

Hi,

Thank you for your great work. I wanted to set up a new Pi4 as an ADS-B receiver. So far, it has always been very laborious and time-consuming. With your Balena package, this is almost child's play. TOP!

I normally pull the data for my VRS (Virtual Radar Server) from my dump1090 receivers via ports 30005 and 30106, but with my actually Balena installation I don't seem to have any access?
Are the ports not accessible from the outside? Is there any other way to push to a VRS?

Thanks

Daniel

Implement OpenSky Network Support, along the same lines used in the PlanerFinder integration that's part of this repo. (The FlightAware and FlightRadar24 integrations are slated for refactoring.)

I have accidentaly ended the previous issue regarding balena not creating a release

It would be great if you could integrate ADSB Exchange's Graphana and display the unfiltered local feed.

Add wiedehop's tar1090 web interface to the setup. From #40:

Only thing i can think of is that your image is missing a nice interface ;P
It should be straight forward to add tar1090 using /run/adsbexchange as a data source if you're interested.
https://github.com/wiedehopf/tar1090#tar1090
The components you need are the html directory, http configuration pointing at /tar1090/data at /run/adsbexchange and (optional but highly recommended) the bash script that makes history files from a configurable path (/run/adsbexchange) and puts them in /run/tar1090 ... then you also need http config pointing /tar1090/chunks at /run/tar1090.
The github repo has http configuration templates for nginx and lighttpd.
nginx is highly recommended, once you use it you won't want to go back!

Anyhow i wouldn't want to make a PR for this stuff as you know better how you want it integrated.
There is also a tar1090 docker container by mikenye but it runs its own readsb .. you wouldn't need to do that but you certainly could easy enough if you want it independent of the adsbexchange feed part.
https://github.com/mikenye/docker-tar1090/

Writing this as more of a reminder to myself (or others) to merge the upstream code from the latest Balena Dash release (https://github.com/balena-labs-projects/balena-dash/releases/tag/v2.0.7)

So ... this mlat-client will clash with the normal mlat-client package as the package isn't really named different.
Python is a mess anyhow that's why the adsbexchange feed client uses a venv and just installs like that.
See this script here: https://github.com/adsbxchange/adsb-exchange/blob/master/update.sh#L180

Anyhow the normal mlat-client will work but our fork is strongly preferred.
(and our fork probably also works for other aggregators but that is in no way guaranteed)

I can look into making it adsbexchange-mlat-client i suppose including package name and everything ...

Are you opposed to just using the master branch?
The version used here is very very very old (it's from before the fork).
Actually this made me realize i should just remake that repository and fork from my repository ... it doesn't have all the database baggage making it huge.
But that would also mean your build will stop working.

If you want to not use a branch but rather a version ... the current commit is as good as any: 8468e346408b3c79ce16cf33e86640d03727fc4f

I'd make a PR but the changes depend on how you want to handle the above :)

hello, I have been using this for a while and for some odd reason I not been able to get MLAT status even thou everything is setup correctly. I am using the balenaCloud setup I followed the directions to the letter and I see the green MLAT status for a few minutes and then it's gone. Any ideas?

Thanks

Hi together,
sorry I am very new to this space and I dont know excatly how it works here. I tried to set up the balena ads b project but unfortunately I can't get any further at point 14. Maybe you can help me? My powershell gives me an error message that the term "git" is not recognized as a name of a cmdlet, function, script file, or executable program. See Screenshot. I already installed a newer version of powershell (7.2.1) and i tried also install poshGit module. What I am doing worng?
Thanks in advance for your help!

Hi,

I am running this system for over a year and would like to update to the latest version so that adsbexchange will be included. This because I use adsbexchange a lot for tracking flight around my home. I cannot find the correct way to do an update. Of course I do not want to lose all my settings. I cannot find the blue button and balena push is not working as it is not complete.
Is there an easy way of updating available. I am running on a Raspberry Pi 3. The current release I am running is : cd2c1cd.
I did update the BalenaOS and the supervisor. BalenaOS is now 2.98.12. Supervisor is 13.1.6.
Thanks for the help, much appreciated.

piaware keeps reporting this:
no ADS-B data program seen listening on port 30978

it never reports up any UAT traffic.

Running pi3b with 2 SDRs configured.

It looks like the ADSB Exchange breakup has splintered in a few places, and adsb.fi is one of them. Could this be added as well as a target? Thanks!

Im unable to create a banela release the reason it fails is

I have tried to create a release 4 plus times and same error occurs

Hi @ketilmo,

can you also put the port 30106 in the ports list, please? 30106 is normally the FA MLAT results port. With VRS you get from there the MLAT-data in Basestation-format.

See here: https://discussions.flightaware.com/t/vrs-show-both-dump1090-adsb-and-fa-mlat-positions/17399

From my other receivers I pull 30005 an 30106 to VRS.

Greetings from Berlin

Daniel

Hello,
At the stage of push to the device (git push balena master) there is an error with client.planefinder.net address:

[planefinder] Processing triggers for libc-bin (2.28-10) ...
[planefinder] --2021-02-27 08:52:54-- http://client.planefinder.net/pfclient_4.2.70_armhf.deb
[planefinder] Resolving client.planefinder.net (client.planefinder.net)...
[planefinder] 23.63.240.192, 23.63.240.186, 2600:141b:7000::173f:f0ba, ...
[planefinder] Connecting to client.planefinder.net (client.planefinder.net)|23.63.240.192|:80...
[planefinder] connected.
[planefinder]
[planefinder] HTTP request sent, awaiting response...
[planefinder] 404 Not Found
[planefinder]
[planefinder] 2021-02-27 08:52:54 ERROR 404: Not Found.
[planefinder]
[planefinder] Removing intermediate container d3d3b3cb1600
[planefinder] The command '/bin/sh -c chmod +x /tmp/planefinder_installer.sh && ./planefinder_installer.sh && chmod +x /start.sh && rm -rf /tmp/' returned a non-zero code: 8
[Info] Uploading images
[Success] Successfully uploaded images
[Error] Some services failed to build:
[Error] Service: planefinder
[Error] Error: The command '/bin/sh -c chmod +x /tmp/planefinder_installer.sh && ./planefinder_installer.sh && chmod +x /start.sh && rm -rf /tmp/' returned a non-zero code: 8
[Info] Built on arm05
[Error] Not deploying release.

remote: error: hook declined to update refs/heads/master
To git.balena-cloud.com:g_michael_b2/airradar.git
! [remote rejected] master -> master (hook declined)
error: failed to push some refs to '[email protected]:g_michael_b2/airradar.git'
root@orangepione:~/balena-ads-b#

Can you kindly check how to fix this?
Thank you!

Hi Ketil,

Is it possible to integrate the function / option to change the external backport for the MLAT results?
Background: I have two receivers at one address. Only one receiver can get the data via port 30104.
Flightaware offers this function regularly. See here (mlat-results-format): https://de.flightaware.com/adsb/piaware/advanced_configuration
With the other services, I don't know right now.

Thanks,
Daniel

On my second feeder, I get this error in a restart loop:

12.07.22 16:21:39 (+0200) dump1090-fa Verifying settings...
12.07.22 16:21:39 (+0200) dump1090-fa
12.07.22 16:21:41 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:21:41 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:21:41 (+0200) dump1090-fa
12.07.22 16:21:41 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:21:41 (+0200) dump1090-fa
12.07.22 16:21:41 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:21:41 (+0200) dump1090-fa Tue Jul 12 14:21:41 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:21:41 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:21:41 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:21:41 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:21:42 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:21:42 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:21:42 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:21:42 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:21:42 (+0200) dump1090-fa /start.sh: line 54: 13 Killed /usr/bin/dump1090-fa $dump1090configuration
12.07.22 16:22:38 (+0200) dump1090-fa Verifying settings...
12.07.22 16:22:38 (+0200) dump1090-fa
12.07.22 16:22:40 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:22:40 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:22:40 (+0200) dump1090-fa
12.07.22 16:22:40 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:22:40 (+0200) dump1090-fa
12.07.22 16:22:40 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:22:40 (+0200) dump1090-fa Tue Jul 12 14:22:40 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:22:40 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:22:41 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:22:41 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:22:41 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:22:41 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:22:41 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:22:41 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:22:41 (+0200) dump1090-fa /start.sh: line 54: 13 Killed /usr/bin/dump1090-fa $dump1090configuration
12.07.22 16:23:46 (+0200) dump1090-fa Verifying settings...
12.07.22 16:23:46 (+0200) dump1090-fa
12.07.22 16:23:48 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:23:48 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:23:48 (+0200) dump1090-fa
12.07.22 16:23:48 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:23:48 (+0200) dump1090-fa
12.07.22 16:23:48 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:23:49 (+0200) dump1090-fa Tue Jul 12 14:23:49 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:23:49 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:23:49 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:23:49 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:23:49 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:23:49 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:23:49 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:23:49 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:23:49 (+0200) dump1090-fa /start.sh: line 54: 13 Killed /usr/bin/dump1090-fa $dump1090configuration
12.07.22 16:24:55 (+0200) dump1090-fa Verifying settings...
12.07.22 16:24:55 (+0200) dump1090-fa
12.07.22 16:24:57 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:24:57 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:24:57 (+0200) dump1090-fa
12.07.22 16:24:57 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:24:57 (+0200) dump1090-fa
12.07.22 16:24:57 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:24:57 (+0200) dump1090-fa Tue Jul 12 14:24:57 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:24:57 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:24:57 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:24:57 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:24:58 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:24:58 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:24:58 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:24:58 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:24:58 (+0200) dump1090-fa /start.sh: line 54: 13 Killed /usr/bin/dump1090-fa $dump1090configuration
12.07.22 16:26:04 (+0200) dump1090-fa Verifying settings...
12.07.22 16:26:04 (+0200) dump1090-fa
12.07.22 16:26:06 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:26:06 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:26:06 (+0200) dump1090-fa
12.07.22 16:26:06 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:26:06 (+0200) dump1090-fa
12.07.22 16:26:06 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:26:06 (+0200) dump1090-fa Tue Jul 12 14:26:06 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:26:06 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:26:06 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:26:06 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:26:07 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:26:07 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:26:07 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:26:07 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:26:07 (+0200) dump1090-fa /start.sh: line 54: 13 Killed /usr/bin/dump1090-fa $dump1090configuration
12.07.22 16:27:12 (+0200) dump1090-fa Verifying settings...
12.07.22 16:27:12 (+0200) dump1090-fa
12.07.22 16:27:14 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:27:14 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:27:14 (+0200) dump1090-fa
12.07.22 16:27:14 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:27:14 (+0200) dump1090-fa
12.07.22 16:27:14 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:27:14 (+0200) dump1090-fa Tue Jul 12 14:27:14 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:27:14 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:27:14 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:27:15 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:27:15 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:27:15 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:27:15 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:27:15 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:27:15 (+0200) dump1090-fa /start.sh: line 54: 14 Killed /usr/bin/dump1090-fa $dump1090configuration
12.07.22 16:28:20 (+0200) dump1090-fa Verifying settings...
12.07.22 16:28:20 (+0200) dump1090-fa
12.07.22 16:28:22 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:28:22 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:28:22 (+0200) dump1090-fa
12.07.22 16:28:22 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:28:22 (+0200) dump1090-fa
12.07.22 16:28:22 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:28:22 (+0200) dump1090-fa Tue Jul 12 14:28:22 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:28:22 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:28:23 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:28:23 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:28:23 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:28:23 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:28:23 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:28:23 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:28:23 (+0200) dump1090-fa /start.sh: line 54: 14 Killed /usr/bin/dump1090-fa $dump1090configuration
12.07.22 16:29:29 (+0200) dump1090-fa Verifying settings...
12.07.22 16:29:29 (+0200) dump1090-fa
12.07.22 16:29:31 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:29:31 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:29:31 (+0200) dump1090-fa
12.07.22 16:29:31 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:29:31 (+0200) dump1090-fa
12.07.22 16:29:31 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:29:31 (+0200) dump1090-fa Tue Jul 12 14:29:31 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:29:31 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:29:31 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:29:31 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:29:32 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:29:32 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:29:32 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:29:32 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:29:32 (+0200) dump1090-fa /start.sh: line 54: 12 Killed /usr/bin/dump1090-fa $dump1090configuration
12.07.22 16:30:38 (+0200) dump1090-fa Verifying settings...
12.07.22 16:30:38 (+0200) dump1090-fa
12.07.22 16:30:40 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:30:40 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:30:40 (+0200) dump1090-fa
12.07.22 16:30:40 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:30:40 (+0200) dump1090-fa
12.07.22 16:30:40 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:30:40 (+0200) dump1090-fa Tue Jul 12 14:30:40 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:30:40 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:30:40 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:30:40 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:30:41 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:30:41 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:30:41 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:30:41 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:30:41 (+0200) dump1090-fa /start.sh: line 54: 12 Killed /usr/bin/dump1090-fa $dump1090configuration
12.07.22 16:31:46 (+0200) dump1090-fa Verifying settings...
12.07.22 16:31:46 (+0200) dump1090-fa
12.07.22 16:31:48 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:31:48 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:31:48 (+0200) dump1090-fa
12.07.22 16:31:48 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:31:48 (+0200) dump1090-fa
12.07.22 16:31:48 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:31:48 (+0200) dump1090-fa Tue Jul 12 14:31:48 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:31:48 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:31:49 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:31:49 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:31:49 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:31:49 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:31:49 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:31:49 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:31:49 (+0200) dump1090-fa /start.sh: line 54: 13 Killed /usr/bin/dump1090-fa $dump1090configuration
12.07.22 16:32:55 (+0200) dump1090-fa Verifying settings...
12.07.22 16:32:55 (+0200) dump1090-fa
12.07.22 16:32:57 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:32:57 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:32:57 (+0200) dump1090-fa
12.07.22 16:32:57 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:32:57 (+0200) dump1090-fa
12.07.22 16:32:57 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:32:57 (+0200) dump1090-fa Tue Jul 12 14:32:57 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:32:57 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:32:57 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:32:57 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:32:58 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:32:58 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:32:58 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:32:58 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:32:58 (+0200) dump1090-fa /start.sh: line 54: 13 Killed /usr/bin/dump1090-fa $dump1090configuration
12.07.22 16:34:03 (+0200) dump1090-fa Verifying settings...
12.07.22 16:34:03 (+0200) dump1090-fa
12.07.22 16:34:05 (+0200) dump1090-fa Receiver latitude is set: XX.XXX
12.07.22 16:34:05 (+0200) dump1090-fa Receiver longitude is set: XX.XXX
12.07.22 16:34:05 (+0200) dump1090-fa
12.07.22 16:34:05 (+0200) dump1090-fa Settings verified, proceeding with startup.
12.07.22 16:34:05 (+0200) dump1090-fa
12.07.22 16:34:05 (+0200) dump1090-fa Enabling adaptive gain in dynamic range mode.
12.07.22 16:34:05 (+0200) dump1090-fa Tue Jul 12 14:34:05 2022 UTC dump1090-fa 7.2 starting up.
12.07.22 16:34:06 (+0200) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
12.07.22 16:34:06 (+0200) dump1090-fa Found Rafael Micro R820T tuner
12.07.22 16:34:06 (+0200) dump1090-fa rtlsdr: tuner gain set to 49.6 dB (gain step 28)
12.07.22 16:34:06 (+0200) dump1090-fa adaptive: using 50% duty cycle
12.07.22 16:34:06 (+0200) dump1090-fa adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
12.07.22 16:34:06 (+0200) dump1090-fa adaptive: enabled dynamic range control, target dynamic range 30.0dB
12.07.22 16:34:06 (+0200) dump1090-fa Allocating 4 zero-copy buffers
12.07.22 16:34:06 (+0200) dump1090-fa /start.sh: line 54: 13 Killed /usr/bin/dump1090-fa $dump1090configuration

Hi, Ketil,
I hope you are doing well!

I continue to set up the my receiver and had started from FlightRadar24 (where I have the account already).
I've set FR24_KEY and checked logs to find how it is going. Unfortunately it looks like fr24feed can't connect dump1090:

03.03.21 19:13:12 (+0300) fr24feed 2021-03-03 16:13:12 | [feed][n]ping 25
03.03.21 19:13:13 (+0300) fr24feed 2021-03-03 16:13:13 | [feed][n]syncing stream result: 1
03.03.21 19:13:14 (+0300) fr24feed 2021-03-03 16:13:14 | [reader][i]Connecting to unknown receiver via (tcp://dump1090-fa:30005)
03.03.21 19:13:14 (+0300) fr24feed 2021-03-03 16:13:14 | [reader][e]Could not connect to tcp://dump1090-fa:30005
03.03.21 19:13:19 (+0300) fr24feed 2021-03-03 16:13:19 | [reader][i]Connecting to unknown receiver via (tcp://dump1090-fa:30005)
03.03.21 19:13:19 (+0300) fr24feed 2021-03-03 16:13:19 | [reader][e]Could not connect to tcp://dump1090-fa:30005

I also found that local web-page of the device returns "Bad Gateway".
And I also see strange "process killing" activity in the dump1090 log:

03.03.21 19:07:00 (+0300) dump1090-fa Verifying settings...
03.03.21 19:07:00 (+0300) dump1090-fa
03.03.21 19:07:02 (+0300) dump1090-fa Receiver latitude is set: 43.5209
03.03.21 19:07:02 (+0300) dump1090-fa Receiver longitude is set: 39.8595
03.03.21 19:07:02 (+0300) dump1090-fa
03.03.21 19:07:02 (+0300) dump1090-fa Settings verified, proceeding with startup.
03.03.21 19:07:02 (+0300) dump1090-fa
03.03.21 19:07:02 (+0300) dump1090-fa Wed Mar 3 16:07:02 2021 UTC dump1090-fa 4.0 starting up.
03.03.21 19:07:03 (+0300) dump1090-fa rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000001)
03.03.21 19:07:03 (+0300) dump1090-fa Found Rafael Micro R820T tuner
03.03.21 19:07:03 (+0300) dump1090-fa rtlsdr: enabling tuner AGC
03.03.21 19:07:03 (+0300) dump1090-fa Allocating 4 zero-copy buffers
03.03.21 19:07:03 (+0300) dump1090-fa /start.sh: line 46: 13 Killed /usr/bin/dump1090-fa --device-type rtlsdr --device "$DUMP1090_DEVICE" --lat "$LAT" --lon "$LON" --fix --gain "$DUMP1090_GAIN" --ppm "$DUMP1090_PPM" --max-range "$DUMP1090_MAX_RANGE" --net --net-heartbeat 60 --net-ro-size 1000 --net-ro-interval 1 --net-http-port 0 --net-ri-port 0 --net-ro-port 30002,30102 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 30005,30105 --raw --json-location-accuracy 2 --write-json /run/dump1090-fa --quiet

Looking forward for your advise how can I fix this.

B.R.
Michael

Implement Radarbox support, along the same lines used in the PlanerFinder integration that's part of this repo. (The FlightAware and FlightRadar24 integrations are slated for refactoring.)

Hardware in Use:

• Raspberry Pi 3 Model B+
• FlightAware Pro Stick Plus USB Dongle

Steps To Reproduce:

• Device has Balena configuration for my Wifi as part of the device setup.
• Observe it registering correctly with all the ADS-B services.
• Leave it a day or 2

Expected Behaviour:

• Device continues to operate as expected and connected to the WiFi and the services.

Actual Behaviour:

• The device at some point disconnects from the WiFi and starts broadcasting the "balenaWiFi" network.
• The device stays in this state until power cycled, or the "wifi-connect" interfaces is used to reconnect manually.

Comments:

This is highly frustrating and I'd like to be able to resolve this as soon as possible!

curl https://api.github.com/repos/balena-io/wifi-connect/releases/latest -s
{
"message": "Moved Permanently",
"url": "https://api.github.com/repositories/37727198/releases/latest",
"documentation_url": "https://docs.github.com/v3/#http-redirects"
}