If you already have a feeder ID, do NOT claim as above. Instead configure piaware with it by following command
(Replace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx by you actual feeder-d
Does the file piaware-repository_7.2 ~ bpo10+1_all.deb differ from this file I allready had downloaded: piaware-repository_7.2_all.deb?
I only use raspberry to my weatherstation and feeding FR24. Don’t know much about debian, linux and all the other - I know much more about dos and windows!
I just have to try to read a bit about MLAT and a possible solution.
You have done an excellent job. Maybe you should make a little guide about these hints - in the same way as your very excellent guides in the FR24 forum
Please also post config of fr24feed as you are using Pi24 image. In Pi24 image, fr24feed controls decoder
(When posting here, replace fr24 key by xxxxx for privacy reasons)
Just curious to know weather you used option-1 or option-2. Although both options solve the problem, they have different strategies.
In Pi24 image, the dump1090-mutability is configured to be controlled by fr24feed, and only fr24feed can get its feed directly, but data availability on network at its ports 30002, 30003, 30005 are blocked. Hence other sites feeding software say dump1090 is not running, although it is running.
In option-1, a line procargs=" --net " is added. This open the dump1090-mutability’s data ports on network, and other sites feeder start getting data from dump1090-mutabity.
In option-2, the lines added (receiver=avr-tcp and host=127.0.0.1:30002), pull out dump1090-mutability from control of fr24feed, and blockage of its ports 30002, 30003, and 30005 is removed. Other sites feeder softwsre now start getting data from it.
There was one more restriction put on dump1090-mutability by fr24feed. It was blocked from starting automatically at boot. It was started by fr24feed when it started. To remove this restriction, in file /etc/default/dump1090-mutability , the setting START_DUMP1090=no was changed from no to yes.