adsb-wiki VS docker-readsb-protobuf

Sound like your receive hardware is subpar, consider some of those options: https://github.com/wiedehopf/adsb-wiki/wiki/adsb-receiver-shopping-list

dump1090-fa / readsb are meant to run via a systemd service. (https://github.com/wiedehopf/adsb-wiki/wiki/Generic-systemd-service)

Make it a service and read just the aircraft.json at certain intervals, sleep in python. (https://github.com/wiedehopf/adsb-wiki/wiki/Generic-systemd-service) That way the processing is better spread out.

I applied the change from the link, and it hadn't happened since: https://github.com/wiedehopf/adsb-wiki/wiki/Raspbian-dropping-off-the-network-potential-workaround

Gain was on -10 (58) before. I think it was the default. I have changed it now to 0.0 according to here https://github.com/wiedehopf/adsb-wiki/wiki/Optimizing-gain

a 5-10 year old laptop should have no problem running a feeder. just install your Linux distro of choice, plug in the SDR, and get tar1090 or readsb running. (I'd recommend the readsb-protobuf docker containers)

this sub recently turned me on to readsb-protobuf, which is a more modern decoder that fills the same role as dump1090. there's a really nice Docker container that packages it up, and includes an output to InfluxDB, a time-series database. so you could potentially build this as a set of queries against an Influx instance, rather than maintaining your own state in a JSON file.

Mikenye’s Adsb docker images are freaking amazing. Use readadsb-protobuf, piaware and graph1090 and you will have your own flight tracker and be able to feed to various sources. I’ve been running this for about a year (prior I ran it barebones).

https://github.com/mikenye/docker-readsb-protobuf This guy has a great collections of docker containers that can feed to a large number of websites and even save all messages to influxdb for later use, it can use the USB SDR directly from the container. Here is the documentation for it: https://mikenye.gitbook.io/ads-b/