signalk-chiplog 2.12.0 → 2.13.0

package/CHANGELOG.md

@@ -6,6 +6,22 @@ All notable changes to Chiplog are documented here. The format follows
 
 ## [Unreleased]
 
+## [2.13.0] - 2026-10-24
+
+### Added
+
+- **Remove the pairing** from the Export page, after a confirmation: the plugin forgets its token and the backup stops.
+  What is already on the service stays there.
+
+### Changed
+
+- **Online backup says why the service cannot be reached.** Instead of "fetch failed", pairing, backup and restore name
+  the host and the cause (name not resolved, connection refused, certificate refused, no answer in time), with a hint
+  for the common ones — a wrong clock behind a certificate refused. A pairing that cannot start is written to the server
+  log.
+- **Pairing no longer asks for the service address.** It is `https://app.tibord.com` for a new plugin; another one, for
+  testing or development, is set in the plugin configuration.
+
 ## [2.12.0] - 2026-10-24
 
 ### Added
@@ -495,7 +511,8 @@ First release.
 - REST API under `/plugins/signalk-chiplog/api`, documented in [docs/API.md](docs/API.md).
 - Single SQLite database through Node's built-in `node:sqlite`: no native module to build.
 
-[Unreleased]: https://github.com/ricard33/signalk-chiplog/compare/v2.12.0...HEAD
+[Unreleased]: https://github.com/ricard33/signalk-chiplog/compare/v2.13.0...HEAD
+[2.13.0]: https://github.com/ricard33/signalk-chiplog/compare/v2.12.0...v2.13.0
 [2.12.0]: https://github.com/ricard33/signalk-chiplog/compare/v2.11.0...v2.12.0
 [2.11.0]: https://github.com/ricard33/signalk-chiplog/compare/v2.10.0...v2.11.0
 [2.10.0]: https://github.com/ricard33/signalk-chiplog/compare/v2.9.0...v2.10.0

package/README.md

@@ -537,14 +537,17 @@ Keep a copy of the logbook off the boat, on the Ti Bord online service. What it
 and how you can share your passages and voyages from it, is at [tibord.com](https://tibord.com), which the **Online
 backup** card links to as well.
 
-1. On the **Export** page, under **Online backup**, enter the service address and choose **Get a pairing code**.
+1. On the **Export** page, under **Online backup**, choose **Get a pairing code**.
 2. On the service, signed in to your account, enter the code shown (e.g. `K7QF-3MXB`) and choose your boat — or scan the
    QR code beside it with your phone, which opens the service with the code filled in. The code is valid for 15 minutes.
-3. The page soon says the boat is paired: Chiplog has saved the service address and its own token in the plugin
-   configuration and turned the backup on.
+3. The page soon says the boat is paired: Chiplog has saved its own token in the plugin configuration and turned the
+   backup on.
 
-You can also paste a token by hand: turn **Back the logbook up online** on in the plugin configuration, fill in the
-**Online service address** and the **Device token**.
+You can also paste a token by hand: turn **Back the logbook up online** on in the plugin configuration and fill in the
+**Device token**. The **Online service address** is `https://app.tibord.com`; change it only to test another instance.
+
+**Remove the pairing**, on the same card, asks for a confirmation, then forgets the token and stops the backup. What is
+already on the service stays there; revoke the device from your account on the service to stop it for good.
 
 From then on, whenever the boat has a connection, Chiplog sends:
 

package/index.js

@@ -278,7 +278,9 @@ module.exports = function (app) {
       cloudSyncUrl: {
         type: 'string',
         title: 'Online service address',
-        description: 'The address of the Ti Bord service: https://app.tibord.com'
+        description:
+          'The address of the Ti Bord service. Leave it as it is unless you test another instance',
+        default: CLOUD_SYNC_DEFAULTS.cloudSyncUrl
       },
       cloudSyncToken: {
         type: 'string',
@@ -591,6 +593,28 @@ module.exports = function (app) {
     });
   }
 
+  // Forgets the pairing from the Export page: the token leaves the plugin configuration and the
+  // backup turns off; the service address stays. What the service holds stays there.
+  function removePairing() {
+    const next = { ...savedConfig, cloudSyncEnabled: false };
+    delete next.cloudSyncToken;
+    return new Promise((resolve, reject) => {
+      app.savePluginOptions(next, (err) => {
+        if (err) {
+          reject(err);
+          return;
+        }
+        savedConfig = next;
+        if (settings) {
+          settings.cloudSyncEnabled = false;
+          settings.cloudSyncToken = null;
+        }
+        cloudPairing?.cancel();
+        resolve();
+      });
+    });
+  }
+
   // Declares the link costly or cheap from the Export page, saved like the rest of the
   // configuration. Back to cheap, a run starts at once: full passages have been waiting.
   function saveCostlyLink(costly) {
@@ -654,7 +678,7 @@ module.exports = function (app) {
             ? SUMMARY_MAIL_DEFAULTS.summaryMailTileUrl
             : config.summaryMailTileUrl,
         cloudSyncEnabled: config.cloudSyncEnabled ?? CLOUD_SYNC_DEFAULTS.cloudSyncEnabled,
-        cloudSyncUrl: config.cloudSyncUrl || null,
+        cloudSyncUrl: config.cloudSyncUrl || CLOUD_SYNC_DEFAULTS.cloudSyncUrl,
         cloudSyncToken: config.cloudSyncToken || null,
         cloudSyncIntervalMinutes:
           config.cloudSyncIntervalMinutes ?? CLOUD_SYNC_DEFAULTS.cloudSyncIntervalMinutes,
@@ -765,6 +789,7 @@ module.exports = function (app) {
     });
     cloudPairing = createCloudPairing({
       db: database,
+      serviceUrl: () => settings.cloudSyncUrl,
       userAgent: `signalk-chiplog/${version}`,
       log,
       onPaired: ({ url, token }) => savePairing(url, token)
@@ -886,6 +911,7 @@ module.exports = function (app) {
           cloudSync,
           nudgeCloudSync: () => cloudSchedule?.nudge(),
           saveCostlyLink,
+          removePairing,
           cloudPairing,
           cloudRestore,
           replayJob,

package/lib/api.js

@@ -778,16 +778,36 @@ function registerRoutes(router, { getContext, logError }) {
     })
   );
 
+  // Forgets the pairing: the device token is removed from the plugin configuration and the
+  // backup turns off. The service keeps what it holds, and the device until revoked there.
+  admin.delete(
+    '/api/cloud-sync/token',
+    handle(async ({ cloudSync, cloudPairing, cloudRestore, removePairing }) => {
+      try {
+        await removePairing();
+      } catch (err) {
+        throw conflict('cloud_sync_save_failed', err.message);
+      }
+      return {
+        ...cloudSync.status(),
+        pairing: cloudPairing.status(),
+        restore: cloudRestore.status()
+      };
+    })
+  );
+
   // Asks the service for a pairing code, then waits in the background for someone to claim
-  // it; GET /cloud-sync follows the pairing.
+  // it; GET /cloud-sync follows the pairing. The service is the configured one unless `url`
+  // names another.
   admin.post(
     '/api/cloud-sync/pairing',
     handle(async ({ cloudPairing }, req) => {
-      if (typeof req.body?.url !== 'string' || req.body.url.trim() === '') {
-        throw badRequest('url is required');
+      const url = req.body?.url;
+      if (url !== undefined && (typeof url !== 'string' || url.trim() === '')) {
+        throw badRequest('url must be a non-empty string');
       }
       try {
-        return await cloudPairing.start(req.body.url.trim());
+        return await cloudPairing.start(url?.trim());
       } catch (err) {
         if (err.code === 'invalid_url') {
           throw badRequest(err.message);

package/lib/cloud-pairing.js

@@ -1,5 +1,6 @@
 const { getLogbookId } = require('./cloud-sync');
 const { qrCode } = require('./qr');
+const { fetchExplained } = require('./network-error');
 
 const REQUEST_TIMEOUT_MS = 30 * 1000;
 // When the service is out of reach mid-pairing: keep asking, as long as the code lives.
@@ -32,6 +33,8 @@ function serviceUrl(text) {
 // given the service address and the token, to save them in the plugin configuration.
 function createCloudPairing({
   db,
+  // The address to pair with when none is given: the one in the plugin configuration.
+  serviceUrl: configuredUrl = () => null,
   userAgent,
   onPaired,
   log,
@@ -44,16 +47,20 @@ function createCloudPairing({
   let timer = null;
 
   async function call(url, path, body) {
-    const response = await fetch(`${url}/v1${path}`, {
-      method: 'POST',
-      headers: {
-        'content-type': 'application/json',
-        'user-agent': userAgent,
-        'x-chiplog-version': userAgent.split('/')[1] ?? ''
+    const response = await fetchExplained(
+      fetch,
+      `${url}/v1${path}`,
+      {
+        method: 'POST',
+        headers: {
+          'content-type': 'application/json',
+          'user-agent': userAgent,
+          'x-chiplog-version': userAgent.split('/')[1] ?? ''
+        },
+        body: JSON.stringify(body)
       },
-      body: JSON.stringify(body),
-      signal: AbortSignal.timeout(REQUEST_TIMEOUT_MS)
-    });
+      REQUEST_TIMEOUT_MS
+    );
     const data = await response.json().catch(() => ({}));
     if (!response.ok) {
       throw new PairingError(data.message ?? `The service answered ${response.status}`, {
@@ -87,6 +94,7 @@ function createCloudPairing({
         state = { state: 'expired', at: new Date(clock()).toISOString() };
       } else if (!(error instanceof PairingError)) {
         // Out of reach for a moment: the code is still good.
+        log('debug', `Online backup pairing: ${error.message}; retrying`);
         schedule(current, RETRY_MS);
       } else {
         attempt = null;
@@ -119,16 +127,22 @@ function createCloudPairing({
 
   return {
     // Asks the service for a code and starts waiting for it to be claimed. A pairing already
-    // under way is dropped: its code was not used.
-    async start(text) {
-      const url = serviceUrl(text);
+    // under way is dropped: its code was not used. Without an address, the configured one.
+    async start(text = configuredUrl()) {
+      const url = serviceUrl(text ?? '');
       if (!url) {
         throw new PairingError('The service address must be an http or https URL', {
           code: 'invalid_url'
         });
       }
       this.cancel();
-      const pairing = await call(url, '/pairings', { logbookId: getLogbookId(db) });
+      let pairing;
+      try {
+        pairing = await call(url, '/pairings', { logbookId: getLogbookId(db) });
+      } catch (error) {
+        log('error', `Online backup pairing could not start: ${error.message}`);
+        throw error;
+      }
       const current = {
         url,
         pairingId: pairing.pairingId,

package/lib/cloud-restore.js

@@ -1,6 +1,7 @@
 const { withTransaction } = require('./database');
 const { getLogbookId, isRestoring } = require('./cloud-sync');
 const { TRACK_READINGS, OBSERVATION_READINGS } = require('./passage-import');
+const { fetchExplained } = require('./network-error');
 
 const REQUEST_TIMEOUT_MS = 2 * 60 * 1000;
 
@@ -250,15 +251,19 @@ function createCloudRestore({
   const isEmpty = () => db.prepare('SELECT count(*) AS n FROM log_entries').get().n === 0;
 
   async function call(path) {
-    const response = await fetch(`${settings.cloudSyncUrl.replace(/\/+$/, '')}/v1${path}`, {
-      method: 'GET',
-      headers: {
-        authorization: `Bearer ${settings.cloudSyncToken}`,
-        'user-agent': userAgent,
-        'x-chiplog-version': userAgent.split('/')[1] ?? ''
+    const response = await fetchExplained(
+      fetch,
+      `${settings.cloudSyncUrl.replace(/\/+$/, '')}/v1${path}`,
+      {
+        method: 'GET',
+        headers: {
+          authorization: `Bearer ${settings.cloudSyncToken}`,
+          'user-agent': userAgent,
+          'x-chiplog-version': userAgent.split('/')[1] ?? ''
+        }
       },
-      signal: AbortSignal.timeout(REQUEST_TIMEOUT_MS)
-    });
+      REQUEST_TIMEOUT_MS
+    );
     if (!response.ok) {
       let detail = {};
       try {

package/lib/cloud-sync.js

@@ -9,9 +9,13 @@ const { allSegments } = require('./propulsion');
 const { getTideForecast } = require('./tide-forecaster');
 const { allObservations, allTrackPoints } = require('./track');
 const { getWeatherForecast } = require('./weather-forecaster');
+const { fetchExplained } = require('./network-error');
 
 const CLOUD_SYNC_DEFAULTS = {
   cloudSyncEnabled: false,
+  // Where every boat backs up; another address is for testing and development, set in the
+  // plugin configuration.
+  cloudSyncUrl: 'https://app.tibord.com',
   cloudSyncIntervalMinutes: 15,
   cloudSyncCostlyLink: false
 };
@@ -180,12 +184,16 @@ function createCloudSync({
       headers['content-encoding'] = 'gzip';
       payload = zlib.gzipSync(JSON.stringify(body));
     }
-    const response = await fetch(`${base()}${path}`, {
-      method,
-      headers,
-      body: payload,
-      signal: AbortSignal.timeout(REQUEST_TIMEOUT_MS)
-    });
+    const response = await fetchExplained(
+      fetch,
+      `${base()}${path}`,
+      {
+        method,
+        headers,
+        body: payload
+      },
+      REQUEST_TIMEOUT_MS
+    );
     if (!response.ok) {
       let detail = {};
       try {

package/lib/network-error.js

@@ -0,0 +1,72 @@
+// Node's fetch says only "fetch failed" when no answer came back; the reason — a name that does
+// not resolve, a refused connection, a certificate refused — is in `cause`, which the plugin
+// would otherwise lose. These turn such a failure into one sentence for the log and the page.
+
+// A hint for the causes a boat meets most, where the fix is not obvious from the code alone.
+const HINTS = [
+  [/^(ENOTFOUND|EAI_AGAIN)$/, 'check the address and that this server can resolve names (DNS)'],
+  [
+    /^(CERT_|UNABLE_TO_VERIFY|SELF_SIGNED|DEPTH_ZERO|ERR_TLS_CERT)/,
+    "check this server's clock: a wrong date makes valid certificates look invalid"
+  ],
+  [/^(ECONNREFUSED|ECONNRESET|EHOSTUNREACH|ENETUNREACH)$/, 'check the address and the network']
+];
+
+function describeCause(cause) {
+  if (!cause) {
+    return null;
+  }
+  // Several addresses tried (IPv4 and IPv6): each has its own reason.
+  if (Array.isArray(cause.errors) && cause.errors.length > 0) {
+    const parts = [
+      ...new Set(cause.errors.map((each) => describeCause(each)?.text).filter(Boolean))
+    ];
+    return { code: cause.code ?? cause.errors[0].code ?? null, text: parts.join('; ') };
+  }
+  const message = cause.message || String(cause);
+  const code = cause.code ?? null;
+  const text = code && !message.includes(code) ? `${code}: ${message}` : message;
+  return { code, text };
+}
+
+// The error a failed `fetch(url)` threw, explained. An answer the service gave is not this
+// function's: only failures where no answer came back are rewritten; anything else is returned
+// as it was.
+function networkError(error, url, timeoutMs) {
+  let host;
+  try {
+    host = new URL(url).host;
+  } catch {
+    host = url;
+  }
+  if (error?.name === 'TimeoutError') {
+    const result = new Error(
+      `No answer from ${host} within ${Math.round(timeoutMs / 1000)} s: check the network`
+    );
+    result.code = 'timeout';
+    result.cause = error;
+    return result;
+  }
+  if (!(error instanceof TypeError) || error.message !== 'fetch failed') {
+    return error;
+  }
+  const cause = describeCause(error.cause);
+  const hint = cause?.code && HINTS.find(([pattern]) => pattern.test(cause.code))?.[1];
+  const result = new Error(
+    `Cannot reach ${host}${cause ? ` (${cause.text})` : ''}${hint ? `: ${hint}` : ''}`
+  );
+  result.code = cause?.code ?? 'fetch_failed';
+  result.cause = error;
+  return result;
+}
+
+// `fetch`, with what went wrong said when no answer came back.
+async function fetchExplained(fetch, url, options, timeoutMs) {
+  try {
+    return await fetch(url, { ...options, signal: AbortSignal.timeout(timeoutMs) });
+  } catch (error) {
+    throw networkError(error, url, timeoutMs);
+  }
+}
+
+module.exports = { networkError, fetchExplained };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "signalk-chiplog",
-  "version": "2.12.0",
+  "version": "2.13.0",
   "description": "Nautical logbook for Signal K: automatic entries, handwritten notes",
   "main": "index.js",
   "files": [

package/public/app.css

@@ -1153,12 +1153,6 @@ button.preset-on {
   margin-bottom: 1rem;
 }
 
-.pairing-form label {
-  display: grid;
-  gap: 0.25rem;
-  flex: 1 1 16rem;
-}
-
 .pairing-code .code {
   font-family: ui-monospace, SFMono-Regular, Menlo, monospace;
   font-size: 2rem;

package/public/js/components/CloudBackup.mjs

@@ -105,27 +105,16 @@ function PairingState({ pairing, onCancel }) {
   return null;
 }
 
-function PairingForm({ initialUrl, onStart, busy }) {
+function PairingForm({ onStart, busy }) {
   const { t } = useLocale();
-  const [url, setUrl] = useState(initialUrl ?? '');
   return html`
     <form
       class="pairing-form"
       onSubmit=${(event) => {
         event.preventDefault();
-        onStart(url);
+        onStart();
       }}
     >
-      <label>
-        ${t('cloud.serviceUrl')}
-        <input
-          type="url"
-          required
-          placeholder="https://"
-          value=${url}
-          onInput=${(event) => setUrl(event.currentTarget.value)}
-        />
-      </label>
       <button type="submit" disabled=${busy}>${t('cloud.pair')}</button>
     </form>
   `;
@@ -279,6 +268,17 @@ export function CloudBackup() {
           onStart=${(logbookId) => act('POST', '/cloud-sync/restore', { logbookId })}
         />`
       }
+      ${
+        status?.configured &&
+        html`<button
+          type="button"
+          class="danger"
+          disabled=${busy}
+          onClick=${() => confirm(t('cloud.unpairConfirm')) && act('DELETE', '/cloud-sync/token')}
+        >
+          ${t('cloud.unpair')}
+        </button>`
+      }
       ${
         status?.pairing &&
         html`<${PairingState}
@@ -293,11 +293,7 @@ export function CloudBackup() {
           <details open=${!ready}>
             <summary>${ready ? t('cloud.pairAgain') : t('cloud.pairTitle')}</summary>
             <p>${t('cloud.pairIntro')}</p>
-            <${PairingForm}
-              initialUrl=${status.url}
-              busy=${busy}
-              onStart=${(url) => act('POST', '/cloud-sync/pairing', { url })}
-            />
+            <${PairingForm} busy=${busy} onStart=${() => act('POST', '/cloud-sync/pairing', {})} />
           </details>
         `
       }

package/public/js/i18n.mjs

@@ -452,11 +452,13 @@ export const MESSAGES = {
     'cloud.restored': 'Logbook restored: {count} passages brought back.',
     'cloud.restoreRefused': '{count} could not be written; see the server log.',
     'cloud.restoreFailed': 'The restore stopped: {message}',
-    'cloud.pairAgain': 'Pair with another account or service',
+    'cloud.pairAgain': 'Pair with another account',
+    'cloud.unpair': 'Remove the pairing',
+    'cloud.unpairConfirm':
+      'Remove the pairing? The backup stops and this plugin forgets its token. What is already on Ti Bord stays there; revoke the device from your account to stop it for good.',
     'cloud.pairIntro':
-      'Enter the service address and ask for a code, then enter the code on the service, signed in to your account. The backup turns on as soon as it is claimed.',
+      'Ask for a code, then enter it on Ti Bord, signed in to your account. The backup turns on as soon as it is claimed.',
     'cloud.learnMore': 'More about the backups, and about sharing your passages and voyages:',
-    'cloud.serviceUrl': 'Service address',
     'cloud.pair': 'Get a pairing code',
     'cloud.enterCode': 'Enter this code on the service:',
     'cloud.openClaim': 'Open the service to enter it',
@@ -1037,12 +1039,14 @@ export const MESSAGES = {
     'cloud.restored': 'Journal restauré : {count} navigations récupérées.',
     'cloud.restoreRefused': '{count} n’ont pas pu être écrites ; voir le journal du serveur.',
     'cloud.restoreFailed': 'La restauration s’est arrêtée : {message}',
-    'cloud.pairAgain': 'Appairer avec un autre compte ou service',
+    'cloud.pairAgain': 'Appairer avec un autre compte',
+    'cloud.unpair': 'Supprimer l’appairage',
+    'cloud.unpairConfirm':
+      'Supprimer l’appairage ? La sauvegarde s’arrête et ce plugin oublie son jeton. Ce qui est déjà sur Ti Bord y reste ; révoquez l’appareil depuis votre compte pour l’arrêter définitivement.',
     'cloud.pairIntro':
-      'Indiquez l’adresse du service et demandez un code, puis saisissez ce code sur le service, connecté à votre compte. La sauvegarde s’active dès qu’il est utilisé.',
+      'Demandez un code, puis saisissez-le sur Ti Bord, connecté à votre compte. La sauvegarde s’active dès qu’il est utilisé.',
     'cloud.learnMore':
       'Plus d’informations sur les sauvegardes et sur le partage de vos navigations et de vos voyages :',
-    'cloud.serviceUrl': 'Adresse du service',
     'cloud.pair': 'Obtenir un code d’appairage',
     'cloud.enterCode': 'Saisissez ce code sur le service :',
     'cloud.openClaim': 'Ouvrir le service pour le saisir',