Advanced Setup

CSS Theme
Temperature information
▶ More information
  • DHT11 or DHRT22 temperature sensor connected to GPIO pins 1 (Vcc), 7 (Data) and 9 (Ground) on a Raspberry Pi
  • BME280 temperature sensor connected to I2C pins on a Raspberry Pi
  • TEMPer USB temperature sensor
Skystats
Skystats is a much extended ADS-B statistics package that provides more detailed data about the aircraft found by the receiver, the most common types, the most common routes and airports, and a list of most interesting aircraft.
▶ More information
Skystats uses a PostgreSQL database to store and analyze aircraft positions, flights, and patterns. This will cause additional write activity on the system (which has otherwise been optimized for minimum disk writes). If you are running this on an SBC with an SD card, this may cause wear on the card and could lead to reduced lifespan. In the advanced configuration below, you can configure the database host, port, user, and password in order to run that database on a different machine instead. Note that this database MUST exist on that machine.
▶ Advanced Configuration
Healthcheck
▶ More information
Healthcheck Ping URL, for example from healthchecks.io but can be any URL.
Set empty URL to disable.
Every 60 minutes a simple http POST request will be performed on this URL if the system is considered healthy.
If the system is at any point considered unhealthy for more than 5 minutes, a simple http POST request will be performed with /fail added to the URL. The reason for the failure will be displayed on the Feeder Homepage and passed as a body in the POST request.
Health status will not include feeds as that is pretty much always not an issue on the receiver side but rather an issue with the aggregator (bad MLAT sync may be added in the future).
No planes / messages for a configurable period of time will mean the system is considered unhealthy. The default is 24 hours but if you have traffic around the clock this can safely be reduced to 1 or 2 hours.
Decoder failures will mean the system is considered unhealthy (1090 + 978 only).

Fail Healthcheck for the following events (only when decoding frequency; set 0 to disable):
Reboot on missing SDR
▶ More information
Sometimes an SDR will drop from USB, but will reappear after a reboot. Usually this is an indication of a real hardware issue (dying SDR, bad power, USB connector issues, etc), but especially with hard to get to feeder setups it can be useful to limp along by forcing a reboot when a configured SDR disappears.
The wait time allows for temporary glitches; only if the SDR is missing for longer than the given time will the reboot be considered.
The max retries prevents infinite reboot loops. If after that many reboots the SDR is still missing, the system keeps running as it did before.
Enable non-ADS-B containers
In addition to tracking ADS-B data, it is possible to enable a number of others SDR-based tracking containers in this image. The SDRs can be assigned on the SDR Setup page once the protocols are enabled here. Similarly, data sharing can be configured on the main Data Sharing page.
The feed IDs below are typically in the form of FL-ICAO-ACARSn where FL are your initials (two or three letters), ICAO is the closest airport, ACARS should be the respective protocol (ACARS, VDL, HFDL) and n is a number to distinguish your feeds if necessary.

Based on your location, these ACARS frequencies appear to carry the most messages:
131.475; 131.525; 131.550; 131.725; 131.825; 131.850

Based on your location, these VDL2 frequencies appear to carry the most messages:
136.675; 136.725; 136.775; 136.825; 136.875; 136.900; 136.975

No SDR is assigned for VDL2 - you can change that on the SDR Setup page.