General configuration

(In the "Config" tab of the web interface)

Wifi mode (0/1/2/3/4) (wifi)

• 0: Wifi disabled
• 1: Wifi station mode. Connects to AP in background and dynamically obtains an IP address (connection ok: IP address shown in display). Connection is made to a network configured in the WiFi tab/network.txt with best RSSI value. Automatically re-connnects in case of connection failure.
• 2: Wifi AP mode. Creates an access point (AP symbol + IP address 192.168.4.1. shown in display). Clients (PC or phone) gets an IP via DHCP
• 3: Wifi station/AP autoselect. On startup, shows result of network scan on display and tries to connect to the first available network in network.txt. If no network in network.txt is available at startup time, board starts in AP mode.
• 4: Wifi station mode without scanning. Connects to first configured network only. No scanning, so faster connect and support for hidden SSID. [added starting devel20240107].

In Wifi mode 1 and 4, you can press any button during the initial WiFi scan/connection at startup to switch to AP mode.

Ephemeris data for RS92 decoding is downloaded only in station mode, only if an RS92 sonde is active in the configuration on startup, and only if WiFi connection succeeds during startup. (no download if RS92 is configured later, or if connection is established later - you need to reboot in this case)

Network mDNS name

Offers name-to-IP-address lookup, so you can use http://rdzsonde.local/ (assuming rdzsonde is the configured mDNS name) instead of http://<ip address>/ for accessing the TTGO web interface. Works only if the TTGO and your device is on the same local subnet and if your devices/browser supports mDNS discovery.

FTP server for ephemeris data (RS92 decoder)

A RS92 sonde does not transmit fully decoded GPS position, but only raw GPS data that needs to be transformed into position information using ephemeris data downloaded from the internet. Needs a server that supports anonymous FTP download.

Debug / log level (debug)

Controls how much is printed on the serial console (and, for some values, extra on-screen hints). Log lines use four levels: errors, warnings, info, debug (module-tagged).

• 0 — errors only
• 1 — errors + warnings
• 2 — errors + warnings + info
• 3 — everything including debug-level messages

Add 10 to any of the above to enable ANSI color prefixes on the serial log (terminal must support escape codes). Examples: 10 = errors only, with color; 13 = full verbosity with color (i.e. base level + 10).

Some older code paths still treat debug == 1 as “a bit more detail” in isolated places (e.g. QRG parsing); the levels above are the main behaviour via the shared logger.

maximum number of QRG entries (maxsonde)

Number of entries in the "QRG" tab. Must be less than 50. Must be larger than 0 as well :-)

Receiver fixed latitude/longitude/altitude (rxlat, rxlon, rxalt)

Static position of the receiver. If the TTGO does not have a GPS receiver (or if the GPS receiver does not have a GPS fix), then this fixed position information is used whenever the TTGO position is needed, such as distance and direction display on the local display, for SondeHub (displaying the receiver location on sondehub.org), for the initial map position of the LiveMap, etc.

Button 2 / medium press mutes LED or buzzer (b2mute)

Duration in minutes (integer). 0 disables this behaviour.

While receiving, the firmware usually blinks the configured LED. If b2mute is not zero, a medium press on button 2 (roughly 1.5–4 s) starts a mute window: LED blinking is suppressed for that many minutes, so the LED stays off. A second medium press on button 2 ends the mute early (before the timer expires).