Thanks for your kind feedback. It’s both inspirational and motivating.
I have no experience with CoT applications, but after a quick look at https://github.com/ampledata/adsbcot, it seems that you can configure it to pull dump1090’s JSON output file using this command -D DUMP1090_URL. Am I understanding you correctly that you already have adsbcot up and running on a separate device?
HI @Ketil, thank you for taking the time to reply.
Yes you are correct, however instead of taking the feed from the JSON, it can be done through beast on port 3005.
I have a standalone instance of FlightAware with adsbcot running perfectly, but would like to integrate it into Balena for multiple deployments. Perhaps this separate post may assist in understanding where I am stuck.
You might get balena-ads-b to run on a Pi Zero 2, but you might have to remove some of the standard services first. The project has grown a bit over the years, and now requires more horsepower than it did initially.
Fr24 are asking for the following edits to be made as a quality issue. I’d like ot change the fr24 feed only, not as a global variable. If I term into the Fr24 container I can cat the file, but cannot edit it.
I just wanted to let you know that a shiny new version of balena-ads-b has just been released! It includes, among other things, UAT tracking support – which is currently only available in the US.
Check out our GitHub repo for all the details, or upgrade to the latest version using our favorite big blue button:
Enjoy! And don’t hesitate to reach out if you have questions.
Hi - with the recent news of ADSBx and the commercial deal fracturing the community I’d like to support the other ADSBx clones too that have popped up over the past few weeks. I’ve very little git experience however. I assume I need to copy the ADSBx section and populate to feed the new sites, and mirror or reuse the variables, and something to start each service? I’m using a Pi 4 4GB so have plenty of resources to use.
Any pointers you could advise?
Once again many thanks for the excellent project!
Rich
Thanks for reaching out. It’s great that you want to contribute to the project. What ADSBX clones are you looking into? They may be relatively straightforward to implement if they are similar to other alternatives. (I have also replied here: ASDB Exchange forks / clones · ketilmo/balena-ads-b · Discussion #76 · GitHub)
I have just recieved another RTLSDR reciever and an antenna I would like to add to my existing setup.
There is already a dongle connected and working and I was wondering if and how one can add another dongle to the same Raspberry Pi.
Dear @Ketil
I have just got into your nice ads-b work through balena.I have put it on a Raspberry 3b+ and tested with a rtl-sdr dongle that worked very nice ; the problem is just the signal inside my building is not so good.
I have one receiver on rooftop that is working for years and feeding both raw and decrypted outputs to my local virtual radar through lan.
Now I want to know if there is any way to make the balena ADS-B station behave somehow like a relay station to get the raw feed from my first unit and share it to other flight trackers ?(which guess it could be done) and if yes,how could it be done( may be inserting variables and values to the console?)
Thanks a lot
Mhayar
<wingbits> 2024-05-28T07:03:22.055651Z INFO vector::config::watcher: Creating configuration file watcher.
<wingbits> 2024-05-28T07:03:22.056417Z ERROR vector::config::watcher: Failed to create file watcher. error=No such file or directory (os error 2) about ["/etc/vector/vector.yaml"]
<wingbits> 2024-05-28T07:03:52.059287Z INFO vector::config::watcher: Creating configuration file watcher.
<wingbits> 2024-05-28T07:03:52.060123Z INFO vector::config::watcher: Speculating that configuration files have changed.
<wingbits> 2024-05-28T07:03:52.060339Z INFO vector::signal: Signal received. signal="SIGHUP"
<wingbits> 2024-05-28T07:03:52.078868Z WARN vector::config::loading: Unknown env var in config. name = "DEVICE_ID"
<wingbits> 2024-05-28T07:03:52.078991Z WARN vector::config::loading: Unknown env var in config. name = "DEVICE_ID"
<wingbits> 2024-05-28T07:03:52.079518Z WARN vector::config::loading: Unknown env var in config. name = "DEVICE_ID"
<wingbits> 2024-05-28T07:03:52.079827Z WARN vector::config::loading: Unknown env var in config. name = "DEVICE_ID"
<wingbits> 2024-05-28T07:03:52.080182Z INFO vector::topology::running: Reloading running topology with new configuration.
<wingbits> [readsb-wingbits] Position json output: Remote server disconnected: localhost port 30006 (fd 8, SendQ 0, RecvQ 0)
<wingbits> [readsb-wingbits] Position json output: Attempting connection to localhost port 30006 ...
<wingbits> [readsb-wingbits] Position json output: Connection to localhost (::1) port 30006 failed: Transport endpoint is not connected
<wingbits> 2024-05-28T07:03:52.095490Z INFO vector::topology::running: Running healthchecks.
<wingbits> 2024-05-28T07:03:52.096194Z INFO vector::topology::running: New configuration loaded successfully.
<wingbits> 2024-05-28T07:03:52.096299Z INFO vector: Vector has reloaded. path=[File("/etc/vector/vector.yaml", Some(Yaml))]
<wingbits> 2024-05-28T07:03:52.096364Z INFO source{component_kind="source" component_id=readsb component_type=socket}: vector::sources::util::net::tcp: Listening. addr=0.0.0.0:30006
<wingbits> [readsb-wingbits] Position json output: Attempting connection to localhost port 30006 ...
<wingbits> [readsb-wingbits] Position json output: Connection established: localhost (127.0.0.1) port 30006
Rebooting to terminal
root@b05d7a03e98b:/tmp# root@b05d7a03e98b:/tmp# Error response from daemon: Container b05d7a03e98b5b3b03a1740aa67f6252f4a69bda39ff832b36147feabecf97ba is not running
Error response from daemon: Container b05d7a03e98b5b3b03a1740aa67f6252f4a69bda39ff832b36147feabecf97ba is not running
SSH session disconnected
SSH reconnecting...
Spawning shell...
root@1911dca90a60:/tmp#