QSL and confirmations

• Each service’s confirmations are recorded separately: LoTW, Club Log and paper QSL. HAMORA never merges them into a single “confirmed”.
• A service never creates a QSO, never replaces a paper or manual confirmation, and never downgrades one.
• For a paper card, open the QSO and mark QSL card received.
• The Logbook can filter by confirmed (any service), confirmed in HAMORA, LoTW confirmed, Club Log, or not confirmed. Exports follow the filter.

Beta Connect your accounts in More→QSL & Confirmations. This is being validated with the live LoTW and Club Log services.

LoTW

New to LoTW? ARRL’s getting started guide (opens in a new tab) walks you through it, in five steps:

1. Install TQSL (opens in a new tab) (free, for Windows and Mac; on Linux, from your system’s software store).
2. In TQSL, request a callsign certificate. ARRL checks your licence: by postcard for US callsigns, or with copies of your licence and an ID for other callsigns.
3. When ARRL’s email arrives, open the certificate in TQSL to accept it.
4. In TQSL, describe your station location.
5. Log in to the LoTW website with the username and password from ARRL’s email.

Then, in HAMORA:

• Open More→QSL & Confirmations and sign in with your LoTW website username and password.
• HAMORA downloads your QSL confirmations, and which of your QSOs LoTW already holds (shown as Uploaded). After the first sync, only what’s new is downloaded.
• Uploading to LoTW needs TQSL: see Exporting for TQSL.

Club Log

• Club Log needs an app password, not your normal password. Sign in on the Club Log website (opens in a new tab), open Settings → App Passwords and create one.
• In HAMORA, sign in with your Club Log email, that app password, and your callsigns.
• HAMORA uploads your QSOs and downloads log matches, shown as “Log match”.
• If Club Log refuses your login, HAMORA stops using it until you reconnect.

Your logins and data

• Logins are checked with the service, then kept only in your phone’s secure storage: never in your logbook, HAMORA Cloud or any log.
• HAMORA sends each service only what it needs for your QSOs: never your notes, the other station’s name or grid, your equipment, or anything from HAMORA Cloud.
• Sync now works at most once a minute per service. The first sync can take a while for a long history.
• On a new phone, reconnect each service: signing in to HAMORA Cloud never connects them.
• Disconnecting deletes the login and pending reviews, but never confirmations.

Uploading to LoTW needs a signature from your LoTW certificate in TQSL, ARRL’s signing program. HAMORA never reads, stores or handles certificate material.

1. Open More→QSL & Confirmations→LoTW and choose Export for TQSL, or select QSOs in the Logbook and choose TQSL.
2. HAMORA writes an ADIF file of the QSOs LoTW doesn’t have yet (or a date range, or your selection), for one station callsign at a time, because each certificate covers one callsign.
3. Open the file in TQSL to sign and upload it.
4. The next LoTW sync marks the QSOs LoTW received as Uploaded.

When a confirmation could match more than one QSO, or none, HAMORA doesn’t guess: it’s listed in Review with the possible QSOs. Attach records it on the QSO you choose; Dismiss hides it. Items are checked again at every sync, so they often resolve themselves once the QSO is in your logbook.

Lifetime Beta HAMORA can sync confirmations by itself when you open the app, at most every 12 hours per service, and upload new QSOs to Club Log. After a failure it waits longer before trying again. It never runs in the background, and logging never waits for it.