restartign the container appears to have cleared any issues and I’m showing green online again
Does this persistently update the docker container for Wingbits? If it’s a docker image won’t it just revert to older pulled image on restart?
Is there a supported way of updating the Wingbits docker image version in this distribution?
Just to add, running the update commands in my wingbits container terminal completely borked it and it will no longer start. Not sure how to fix it without completely reinstalling the packages from scratch.
Edit: Found my answer in the Git discussions.
Just for anyone else looking, the answer to this is here:
Additionally, there is a few ways of how to automatically update the system each time an update is pushed to the balena-ads-b repo using GitHub actions etc. It is relatively simple to do if you know your way around balena and GitHub but for those that don’t I’ll try and find time to put together a quick guide for it.
Thanks for reaching out, @mah!
I have now created a feature request for this on balena-ads-b’s GitHub page. You can track it here: [FEATURE REQUEST] Relay station support · Issue #109 · ketilmo/balena-ads-b · GitHub
Hi Ketil,
I completely understand your request as I faced a similar issue myself. I was able to address it by implementing custom filters in the balena ADS-B project. Specifically, I added a filter to track flights based on altitude and range from my location. I found that integrating these filters required modifying some of the project’s configuration files and scripts to accommodate the new parameters.
If you’re interested, I’d be happy to share more details about the modifications I made or guide you through the process.
Sounds like a cool feature!
Hi all,
first of all thanks the project.
I don’t know if this is the right place to post this.
I’ve a problem, with my rasp 4 and 1090 receiver.
I started using it with adsbexchange feed client and it works super, now i’d like to move to balena adsb, I load everything all the services seems to work properly, but plane are not received. If i change the the SD card and reboot it with adsbexchange client it work perfectly. Any help?
Thanks
Simone
Hi Simone,
Thanks for using balena-ads-b. Have you migrated all the settings from your install, and added the necessary variables? Do you see anything in the logs?
I’ve followed the guide step by step I think the problem is in some setting of the SDR
From the Log I see for example: piaware 0 msgs recv’d from the ADS-B data program at dump1090-fa/30005 (0 in last 5m); 0 msgs sent to FlightAware
I am getting this logs continous, what really mean this…
tar1090 /run/s6/basedir/scripts/rc.init: fatal: stopping the container.
tar1090 s6-rc: info: service libseccomp2: stopping
tar1090 s6-rc: info: service legacy-cont-init: stopping
tar1090 s6-rc: info: service 09-rtlsdr-biastee: stopping
tar1090 s6-rc: info: service libseccomp2 successfully stopped
tar1090 [2025-01-30 16:14:42.284][09-rtlsdr-biastee-down] Device type is not rtlsdr, skipping…
tar1090 s6-rc: info: service 09-rtlsdr-biastee successfully stopped
tar1090 s6-rc: info: service legacy-cont-init successfully stopped
tar1090 s6-rc: info: service fix-attrs: stopping
tar1090 s6-rc: info: service fix-attrs successfully stopped
tar1090 s6-rc: info: service s6rc-oneshot-runner: stopping
tar1090 s6-rc: info: service s6rc-oneshot-runner successfully stopped
My Wingbits container is running an old version so the ‘wingbits’ commands don’t work and the Geosigner isn’t ‘seen’. I’ve created a new device with latest as the deploy button no longer works. Anything else I can try?
Ok, installed CLI and performed push. wingbits status command shows everything is failed, however stations page on web shows online and geosigner green ticked with serial number, so guess this is ok for now?
@sadeedp these errors are not a problem. See GitHub issue here s6 service errors in tar1090 container · Issue #250 · ketilmo/balena-ads-b · GitHub
@rtype23 wingbits status
won’t work on balena as it doesn’t use systemctl
You can use wingbits geosigner info
instead
I’ve just started using balena, as central way to manage several on site/at home Raspberry Pis. One’s a 3B and one’s a 4. Installing was flawless, was upgrading. My main purpose was to us the OS/system to stablize my two ADS-B trackers, which use primarily piaware and f24feeder. I have long standing accounts and feeder keys/ids from both services.
After installing the ADS-B Flight Tracker, balena-ads-b, and following instructions to set the appropriate variables, there’s no signal being sent up stream. The log file seems to indicate some errors with daemons along the lines: no latitude, no longitude.
Killing service ‘piaware sha256:8828aa921719e4ce115f1de568dd292d3924add2641057df0a74a0286b5cc22f’
Service exited ‘piaware sha256:8828aa921719e4ce115f1de568dd292d3924add2641057df0a74a0286b5cc22f’
Killed service ‘piaware sha256:8828aa921719e4ce115f1de568dd292d3924add2641057df0a74a0286b5cc22f’
Installing service ‘piaware sha256:8828aa921719e4ce115f1de568dd292d3924add2641057df0a74a0286b5cc22f’
Taking update locks
Installed service ‘piaware sha256:8828aa921719e4ce115f1de568dd292d3924add2641057df0a74a0286b5cc22f’
Starting service ‘piaware sha256:8828aa921719e4ce115f1de568dd292d3924add2641057df0a74a0286b5cc22f’
Started service ‘piaware sha256:8828aa921719e4ce115f1de568dd292d3924add2641057df0a74a0286b5cc22f’
Releasing update locks
piaware Verifying settings…
piaware
piaware FlightAware feeder ID is set: 3f867654-006b-44a4-a544-0c6cf4243b59
piaware Receiver latitude is missing, will abort startup.
piaware Receiver longitude is missing, will abort startup.
piaware Receiver altitude is missing, will abort startup.
piaware Receiver host is set: dump1090-fa
piaware Receiver port is set: 30005
piaware Receiver MLAT port is set: 30104
piaware
piaware Settings missing, aborting…
piaware
piaware Idling…
Addendum… I have solved this problem by setting the LAT / LON / ALT variables. My bad.
However MLAT data does not seem to be registering on my FlightAware account.
@quist did you set the station location in flightaware side?
You need to do this, and then activate MLAT there to get it to work.
From the website you need to login and then under the menu My ADSB you click stats and then the little settings cog
Hello.
I get a release creation error when deploying using the deploy button from balena hub. The problem seems to be opensky-network.
[Info] Starting build for balena-ads-b, user g_kamil_w
[Info] Dashboard link: balena dashboard
[Info] Building on 8fdf4d7
[Info] No suitable previous release for caching, skipping cache pull
[Info] Starting to build kiosk
[Info] Starting to build wifi-connect
[Info] Starting to build autohupr
[Info] Starting to build planefinder
[Info] Starting to build dump1090-fa
[Info] Starting to build radarbox
[Info] Starting to build opensky-network
[Info] Starting to build adsb-exchange
[Info] Starting to build tar1090
[Info] Starting to build planewatch
[Info] Starting to build piaware
[Info] Starting to build fr24feed
[Info] Starting to build dump978-fa
[Info] Starting to build wingbits
[Info] Starting to build frontend-proxy
[Success] Successfully built service wifi-connect
[Success] Successfully built service autohupr
[Success] Successfully built service planefinder
[Success] Successfully built service radarbox
[Success] Successfully built service tar1090
[Success] Successfully built service wingbits
[Success] Successfully built service frontend-proxy
[Success] Successfully built service fr24feed
[Success] Successfully built service adsb-exchange
[Success] Successfully built service kiosk
[Success] Successfully built service piaware
[Success] Successfully built service planewatch
[Success] Successfully built service dump1090-fa
[Success] Successfully built service dump978-fa
[Info] Uploading images
[Success] Successfully uploaded images
[Error] Some services failed to build:
[Error] Service: opensky-network
[Error] Error: The command ‘/bin/sh -c chmod +x /tmp/opensky_installer.sh && ./opensky_installer.sh’ returned a non-zero code: 8
[Info] Built on 8fdf4d7
[Error] Not deploying release.
Thanks for getting in touch, @jediksd. I’m sorry you’re having issues with the build. Can you please create an issue in our GitHub repo, including what hardware you are deploying to? It makes it easier for us to coordinate the debugging.
Repo link here: https://tgithub.com/ketilmo/balena-ads-b
@Ketil Opensky-Network problem Orange Pi Zero deploy by BalenaHUB · Issue #289 · ketilmo/balena-ads-b · GitHub
Thanks @jediksd, we’ll look into it.