Hey I’ve had an adsb tracker that pushed to flightaware in the past, took it down and am looking to get back into it now that i’ve redone my home (lab) network. This time I want to do a little bit of a more “custom” install (relatively speaking of course) but have some questions about some things im not sure of.
I am planning on using the readsb-protobuf software to decode the data on a raspberry pi zero stationed outside and up high (for best reception).
From there i want to “push” the data to
a web server running tar1090 on a different machine on the network
flightaware
Now my question is , does flight aware and/or tar2090 support protocol buffers/push servers?
Admittedly I havent spent hours combing through documentation and code to try and figure this out but from what I do know/understand (at least from when I last did this) is that:
dump1090(-fa) / readsb will decode the adsb data then makes the data available either through
a- some type of socket on port 3004/3005
b- local json files
2a) the json files are then used by tar1090 for displaying your local readings
2b) piaware will listen to port 3005 convert the (beast formatted data?) data and send it to their servers
Are these assumptions correct?
If so i noticed in the readsb-protobug documentation that data can be forwarded directly via the command line arg --net-connector feed.site,30005,beast_out , can i set up piware to listen to that socket and forward it to flightaware? Alternatively maybe theres a place I can create a custom user link (maybe account section?) that can then be used to push data and have flightaware know its from me?
I was looking around and it seems that tar1090 can use sources (other than local json files) , does anyone know how I would set it up to use data provided by readsb-protobuf?
There just seems to be so much information to digest that varies slightly from place to place and the more I read the more I get confused so please point out anything I got wrong and thank you for any help.
The piaware data feeder installed on a RPi or computer on same local network (to which Pi zero is connected), can pull the decoded data from port 30005 of resdsb-protobuf, if piaware is configured as given below.
The piaware data feeder will then push to Flightaware the data it receives from readsb-protobuf on Pi Zero. You do NOT need any additional push server to push data to Flightaware
sudo piaware-config receiver-type other
sudo piaware-config receiver-port 30005
sudo piaware-config receiver-host 192.168.0.22
## Replace 192.168.0.22 by local IP of Pi Zero
sudo piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
## Replace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx by your site's actual feeder-id
sudo systemctl restart piaware
Now you can install other feed clients on the second box without giving it a second thought, most of them will just default to getting data from localhost:30005 where the data is rebroadcast by the locally running readsb.
While tar1090 can work with dump1090-fa … it won’t work with readsb protobuf as that doesn’t produce the required files in /run.
Really if you want to use tar1090 … just run my readsb, that’s really what it’s for.
(the readsb install linked above will just install tar1090 as well so it has a webinterface)
I suppose the tar1090 readme could use some info on that, not sure which page people usually stumble upon.
Thanks guys! I appreciate it. I plan to implement this this weekend so I may have some more questions but I think this answers everything so thanks again.
