Wavelog

2026-04-29T11:50:03Z

DJ7NT: Wavelog integration

= Wavelog Integration =

Wolf integrates with [https://github.com/wavelog/wavelog Wavelog], a self-hosted web-based logging application, via its REST API over Wi-Fi.

== Settings ==

Navigate to '''System Menu → WiFi → Wavelog'''.

{| class="wikitable"
! Setting !! Description
|-
| '''Wavelog Enabled''' || Master switch. Enables all Wavelog features.
|-
| '''Wavelog URL''' || Base URL of your Wavelog instance (e.g. <code>http://192.168.1.10/wavelog</code>). HTTP and HTTPS are both supported. Max 64 characters.
|-
| '''Wavelog API Key''' || API key from your Wavelog user profile. Max 64 characters.
|-
| '''Station ID''' || Select from stations fetched live from your Wavelog instance via ''Wavelog Settings → Station ID''. The station list is retrieved on demand using <code>/api/station_info/<key></code>.
|-
| '''Wavelog Radio''' || Logical radio name sent with each CAT update (identifies the radio in Wavelog). Max 32 characters.
|}

Wi-Fi must be connected and the URL/API key must be set for any feature to function.

== Features ==

=== CAT / Radio Update (Real-Time Frequency Tracking) ===

Wolf automatically posts the current VFO frequency and mode to Wavelog's <code>/api/radio</code> endpoint whenever you tune to a new frequency. This keeps the Wavelog "Live" view in sync with the radio. Chose the Radioname you set at "Wavelog Radio" at the Station-Tab within Wavelog.

'''Behavior:'''
* Triggered after a 1-second settle time once the frequency or mode stops changing — avoids flooding during fast tuning.
* Fires only when not transmitting.
* Posts TX frequency (the <code>frequency</code> field); in '''Split''' mode, the RX frequency is sent as <code>frequency_rx</code>.
* Reported power is taken from the RF Gain setting.

'''Mode mapping:'''

{| class="wikitable"
! Wolf mode !! Wavelog mode string
|-
| LSB || <code>LSB</code>
|-
| USB / all others || <code>USB</code>
|-
| CW || <code>CW</code>
|-
| NFM / WFM || <code>FM</code>
|-
| AM / DSB / SAM || <code>AM</code>
|-
| RTTY || <code>RTTY</code>
|-
| PSK31 || <code>PSK31</code>
|-
| DIGI-U / DIGI-L || <code>FT8</code>
|}

=== QSO Logging ===

Wolf logs completed QSOs to Wavelog automatically after a contact is confirmed in the FT8/FT4 engine.

* The ADIF record is sent to <code>/api/qso</code> including: callsign, grid square, RST sent/received, date/time on and off, band, frequency, station callsign, and locator.
* The configured Station ID is included in the JSON payload so the QSO is attributed to the correct station in Wavelog.
* Logging is queued and sent asynchronously; if a previous request is still in progress, it is retried on the next processing cycle.
* The QSO is also written to the SD card log file (<code>FT8_QSO_Log_<CALL>.adi</code> / <code>FT4_QSO_Log_<CALL>.adi</code>) in parallel.
* Important: Doublecheck the station_id. Locator and own call must match to those settings in Wavelog

=== Spot Lookup (DX Cluster Integration) ===

When both the DX Cluster and Wavelog are enabled, Wolf queries Wavelog's <code>/api/private_lookup</code> endpoint for each incoming DX spot to determine whether the spotted callsign has already been worked or confirmed on that band.

'''Lookup result colors''' (applied to DX spot markers on the waterfall/spectrum):

{| class="wikitable"
! Color !! Status
|-
| style="color:green;" | '''Green''' || '''Confirmed''' — QSO is confirmed (e.g. via LoTW/QSL)
|-
| style="color:orange;" | '''Orange''' || '''Worked''' — QSO logged but not yet confirmed
|-
| '''White''' || '''Never worked''' — no previous contact on this band, or not looked up
|}

'''Implementation details:'''
* Lookups are processed sequentially (one at a time, 5-second timeout per spot).
* Results are cached per spot for '''15 minutes'''. When the DX cluster list is refreshed, cached statuses are preserved for spots with matching callsigns.
* Color coding is only active when Wavelog is enabled; otherwise all markers use the default color.

Wolf TRX - Вклад [ru]

Wavelog