From 2135c5acd6fe1fd0ea8a0cab202936156e599d3c Mon Sep 17 00:00:00 2001 From: Alan Hargreaves Date: Thu, 14 May 2026 11:04:10 +1000 Subject: [PATCH 1/2] Move the QRZ.COM credetials settings to the Integrations Page --- src/components/SettingsPanel.jsx | 538 +++++++++++++++---------------- 1 file changed, 269 insertions(+), 269 deletions(-) diff --git a/src/components/SettingsPanel.jsx b/src/components/SettingsPanel.jsx index d3ebefb0..616a85ae 100644 --- a/src/components/SettingsPanel.jsx +++ b/src/components/SettingsPanel.jsx @@ -2738,80 +2738,287 @@ export const SettingsPanel = ({ /> + -
- +
+ 📡 QRZ.com Callsign Lookup + {qrzStatus?.configured && ( + + {qrzStatus.hasSession ? '● Connected' : '○ Configured'} + {qrzStatus.source === 'env' ? ' (env)' : ''} + + )} +
+
+ Enables precise station locations from{' '} + - Learn how -
- + QRZ.com + {' '} + user profiles (user-supplied coordinates, geocoded addresses, grid squares). Without this, locations + fall back to HamQTH (country-level only). Requires a QRZ Logbook Data subscription. +
+ Note this is a server setting and is not related to clicking a callsign to go to + qrz.com. If you are not running a server, you will likely not have the permissions to change this. + + {qrzStatus?.source === 'env' ? (
-
- Quick start (Local Only): + ✓ Credentials configured via{' '} + + QRZ_USERNAME + {' '} + /{' '} + + QRZ_PASSWORD + {' '} + in .env file + {qrzStatus.lookupCount > 0 && ( + + {' '} + — {qrzStatus.lookupCount} lookups this session + + )} +
+ ) : ( + <> +
+ setQrzUsername(e.target.value)} + style={{ + flex: 1, + padding: '8px 12px', + background: 'var(--bg-primary)', + border: '1px solid var(--border-color)', + borderRadius: '4px', + color: 'var(--text-primary)', + fontSize: '12px', + fontFamily: 'var(--font-mono)', + boxSizing: 'border-box', + }} + /> + setQrzPassword(e.target.value)} + style={{ + flex: 1, + padding: '8px 12px', + background: 'var(--bg-primary)', + border: '1px solid var(--border-color)', + borderRadius: '4px', + color: 'var(--text-primary)', + fontSize: '12px', + fontFamily: 'var(--font-mono)', + boxSizing: 'border-box', + }} + />
+
+ + {qrzStatus?.configured && qrzStatus.source !== 'env' && ( + + )} + {qrzStatus?.configured && qrzStatus.lookupCount > 0 && ( + + {qrzStatus.lookupCount} lookups this session + + )} +
+ {qrzMessage && ( +
+ {qrzMessage.type === 'success' ? 'âś“' : 'âś—'} {qrzMessage.text} +
+ )} + + )} +
-
    -
  1. - Run OpenHamClock locally: -
    npm start
    - Open the local URL shown in your terminal (example: http://127.0.0.1:3001). -
    2. - -
  2. - Install the N3FJP bridge on the same PC (or LAN machine) that can access your N3FJP logger. -
    3. - -
  3. - Edit the bridge config.json file and set: -
    - "OHC_BASE_URL": "http://127.0.0.1:3001" -
    - (Use the exact URL printed by OpenHamClock.) -
    4. - -
  4. - Ensure: -
    "ENABLE_OHC_HTTP": true
    -
    5. - -
  5. - Start the bridge script (PowerShell or VBS launcher). You should see log messages when QSOs are - entered. -
    6. +
    + + Learn how + -
  6. - Enable this integration here, then turn on - Logged QSOs (N3FJP) in - Settings → Map Layers. -
    7. -
+
+
+ Quick start (Local Only): +
-
- Tip: If you see “connection refused,” verify that OpenHamClock is running locally and that the - port matches your - OHC_BASE_URL setting. -
+
    +
  1. + Run OpenHamClock locally: +
    npm start
    + Open the local URL shown in your terminal (example: http://127.0.0.1:3001). +
    2. + +
  2. + Install the N3FJP bridge on the same PC (or LAN machine) that can access your N3FJP logger. +
    3. + +
  3. + Edit the bridge config.json file and set: +
    + "OHC_BASE_URL": "http://127.0.0.1:3001" +
    + (Use the exact URL printed by OpenHamClock.) +
    4. + +
  4. + Ensure: +
    "ENABLE_OHC_HTTP": true
    +
    5. + +
  5. + Start the bridge script (PowerShell or VBS launcher). You should see log messages when QSOs are + entered. +
    6. + +
  6. + Enable this integration here, then turn on + Logged QSOs (N3FJP) in + Settings → Map Layers. +
    7. +
+ +
+ Tip: If you see “connection refused,” verify that OpenHamClock is running locally and that the port + matches your + OHC_BASE_URL setting. +
-
- Note: This integration cannot work on the hosted site because it requires access to your local - N3FJP logger and LAN services. -
+
+ Note: This integration cannot work on the hosted site because it requires access to your local N3FJP + logger and LAN services.
-
- + + )} @@ -4215,213 +4422,6 @@ export const SettingsPanel = ({ )} - {/* QRZ.com XML API Credentials */} -
-
- 📡 QRZ.com Callsign Lookup - {qrzStatus?.configured && ( - - {qrzStatus.hasSession ? '● Connected' : '○ Configured'} - {qrzStatus.source === 'env' ? ' (env)' : ''} - - )} -
-
- Enables precise station locations from{' '} - - QRZ.com - {' '} - user profiles (user-supplied coordinates, geocoded addresses, grid squares). Without this, locations - fall back to HamQTH (country-level only). Requires a QRZ Logbook Data subscription. -
- Note this is a server setting and is not related to clicking a callsign to go to - qrz.com. If you are not running a server, you will likely not have the permissions to change this. -
- {qrzStatus?.source === 'env' ? ( -
- ✓ Credentials configured via{' '} - - QRZ_USERNAME - {' '} - /{' '} - - QRZ_PASSWORD - {' '} - in .env file - {qrzStatus.lookupCount > 0 && ( - - {' '} - — {qrzStatus.lookupCount} lookups this session - - )} -
- ) : ( - <> -
- setQrzUsername(e.target.value)} - style={{ - flex: 1, - padding: '8px 12px', - background: 'var(--bg-primary)', - border: '1px solid var(--border-color)', - borderRadius: '4px', - color: 'var(--text-primary)', - fontSize: '12px', - fontFamily: 'var(--font-mono)', - boxSizing: 'border-box', - }} - /> - setQrzPassword(e.target.value)} - style={{ - flex: 1, - padding: '8px 12px', - background: 'var(--bg-primary)', - border: '1px solid var(--border-color)', - borderRadius: '4px', - color: 'var(--text-primary)', - fontSize: '12px', - fontFamily: 'var(--font-mono)', - boxSizing: 'border-box', - }} - /> -
-
- - {qrzStatus?.configured && qrzStatus.source !== 'env' && ( - - )} - {qrzStatus?.configured && qrzStatus.lookupCount > 0 && ( - - {qrzStatus.lookupCount} lookups this session - - )} -
- {qrzMessage && ( -
- {qrzMessage.type === 'success' ? 'âś“' : 'âś—'} {qrzMessage.text} -
- )} - - )} -
- {/* Open-Meteo API Key (optional) */}
Date: Thu, 14 May 2026 11:15:24 +1000 Subject: [PATCH 2/2] Move teh N3FJP "LearnHow" detail back to teh correct place --- src/components/SettingsPanel.jsx | 146 +++++++++++++++---------------- 1 file changed, 73 insertions(+), 73 deletions(-) diff --git a/src/components/SettingsPanel.jsx b/src/components/SettingsPanel.jsx index 616a85ae..3295c080 100644 --- a/src/components/SettingsPanel.jsx +++ b/src/components/SettingsPanel.jsx @@ -2738,6 +2738,79 @@ export const SettingsPanel = ({ />
+ +
+ + Learn how + + +
+
+ Quick start (Local Only): +
+ +
    +
  1. + Run OpenHamClock locally: +
    npm start
    + Open the local URL shown in your terminal (example: http://127.0.0.1:3001). +
    2. + +
  2. + Install the N3FJP bridge on the same PC (or LAN machine) that can access your N3FJP logger. +
    3. + +
  3. + Edit the bridge config.json file and set: +
    + "OHC_BASE_URL": "http://127.0.0.1:3001" +
    + (Use the exact URL printed by OpenHamClock.) +
    4. + +
  4. + Ensure: +
    "ENABLE_OHC_HTTP": true
    +
    5. + +
  5. + Start the bridge script (PowerShell or VBS launcher). You should see log messages when QSOs are + entered. +
    6. + +
  6. + Enable this integration here, then turn on + Logged QSOs (N3FJP) in + Settings → Map Layers. +
    7. +
+ +
+ Tip: If you see “connection refused,” verify that OpenHamClock is running locally and that the + port matches your + OHC_BASE_URL setting. +
+ +
+ Note: This integration cannot work on the hosted site because it requires access to your local + N3FJP logger and LAN services. +
+
+
{/* QRZ.com XML API Credentials */} @@ -2946,79 +3019,6 @@ export const SettingsPanel = ({ )} - -
- - Learn how - - -
-
- Quick start (Local Only): -
- -
    -
  1. - Run OpenHamClock locally: -
    npm start
    - Open the local URL shown in your terminal (example: http://127.0.0.1:3001). -
    2. - -
  2. - Install the N3FJP bridge on the same PC (or LAN machine) that can access your N3FJP logger. -
    3. - -
  3. - Edit the bridge config.json file and set: -
    - "OHC_BASE_URL": "http://127.0.0.1:3001" -
    - (Use the exact URL printed by OpenHamClock.) -
    4. - -
  4. - Ensure: -
    "ENABLE_OHC_HTTP": true
    -
    5. - -
  5. - Start the bridge script (PowerShell or VBS launcher). You should see log messages when QSOs are - entered. -
    6. - -
  6. - Enable this integration here, then turn on - Logged QSOs (N3FJP) in - Settings → Map Layers. -
    7. -
- -
- Tip: If you see “connection refused,” verify that OpenHamClock is running locally and that the port - matches your - OHC_BASE_URL setting. -
- -
- Note: This integration cannot work on the hosted site because it requires access to your local N3FJP - logger and LAN services. -
-
-
)}