signalk-chiplog 2.2.0 → 2.3.0

package/CHANGELOG.md

@@ -6,6 +6,23 @@ All notable changes to Chiplog are documented here. The format follows
 
 ## [Unreleased]
 
+## [2.3.0] - 2026-09-18
+
+### Added
+
+- **InfluxDB query timeout** setting (`influxQueryTimeoutSeconds`, 30 s by default): how long a retrospective replay
+  waits for the InfluxDB server to answer before giving up on it as unreachable or overloaded, now configurable instead
+  of a fixed 30 seconds — useful against a Raspberry Pi that is simply slow to answer a six-hour chunk.
+
+### Fixed
+
+- **Retrospective replay backfilling a gap before passages already logged live** no longer dated every reconstructed
+  passage to the most recent existing passage's end time. Detection's guard against an out-of-order departure looked at
+  the latest `end_time` in the whole logbook rather than only at passages that actually preceded the new one, so filling
+  in an earlier gap — installing Chiplog after the fact, or after a stop — pinned every reconstructed departure to that
+  unrelated, later date, and the replay summary reported no passage found for the requested period even though entries
+  had been created.
+
 ## [2.2.0] - 2026-09-18
 
 ### Added
@@ -249,7 +266,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.2.0...HEAD
+[Unreleased]: https://github.com/ricard33/signalk-chiplog/compare/v2.3.0...HEAD
+[2.3.0]: https://github.com/ricard33/signalk-chiplog/compare/v2.2.0...v2.3.0
 [2.2.0]: https://github.com/ricard33/signalk-chiplog/compare/v2.1.0...v2.2.0
 [2.1.0]: https://github.com/ricard33/signalk-chiplog/compare/v2.0.0...v2.1.0
 [2.0.0]: https://github.com/ricard33/signalk-chiplog/compare/v1.2.0...v2.0.0

package/README.md

@@ -1,7 +1,7 @@
 # Chiplog
 
-An automated logbook for [Signal K](https://signalk.org). Chiplog writes the logbook from the data already on your
-boat's Signal K server — passages, track, engine and sail, instrument readings, alarms — and lets the crew add what
+An automated nautical logbook for [Signal K](https://signalk.org). Chiplog writes the logbook from the data already on
+your boat's Signal K server — passages, track, engine and sail, instrument readings, alarms — and lets the crew add what
 sensors cannot know from a tablet at the helm: manoeuvres, notes and handwriting.
 
 - **One entry per passage**, opened when the boat leaves and closed as soon as it arrives, carrying on after short stops
@@ -348,6 +348,7 @@ In the Signal K admin, **Apps & Plugins → Configuration → Chiplog**.
 | InfluxDB database                                                | —                                             |                                                                                                                                                                                  |
 | InfluxDB username / password                                     | —                                             | Leave empty if the database needs none.                                                                                                                                          |
 | InfluxDB protocol                                                | http                                          | `http` or `https`.                                                                                                                                                               |
+| InfluxDB query timeout                                           | 30 s                                          | Each retrospective query gives up and reports an error past this, instead of hanging against an unreachable or overloaded database.                                              |
 | InfluxDB vessel context                                          | this server's own                             | Only needed running the replay from a different Signal K server than the one that wrote the history, e.g. development pointed at a production database.                          |
 
 ## Signal K data used 🔌
@@ -497,9 +498,10 @@ context** in the plugin configuration.
 ### A retrospective analysis takes minutes then fails with no clear reason
 
 The InfluxDB server did not answer — unreachable, overloaded, a firewall or a VPN not connected. Each query now gives up
-after 30 seconds with the connection problem it ran into, rather than hanging until some far longer, less informative
-failure; check that the server named in the plugin configuration is reachable from wherever Signal K runs, and that it
-is not overloaded.
+after **InfluxDB query timeout** (30 seconds by default) with the connection problem it ran into, rather than hanging
+until some far longer, less informative failure; check that the server named in the plugin configuration is reachable
+from wherever Signal K runs, and that it is not overloaded — or raise the timeout if it is simply slow to answer a
+six-hour chunk.
 
 ### A retrospective analysis over several days makes the InfluxDB server unresponsive
 

package/index.js

@@ -256,6 +256,14 @@ module.exports = function (app) {
         enum: ['http', 'https'],
         default: INFLUX_DEFAULTS.influxProtocol
       },
+      influxQueryTimeoutSeconds: {
+        type: 'number',
+        title: 'InfluxDB query timeout (seconds)',
+        description:
+          'Each retrospective query is given up on and reported as an error past this, rather than hanging indefinitely against an unreachable or overloaded database',
+        default: INFLUX_DEFAULTS.influxQueryTimeoutSeconds,
+        minimum: 1
+      },
       influxSelfContext: {
         type: 'string',
         title: 'InfluxDB vessel context',
@@ -384,6 +392,8 @@ module.exports = function (app) {
         influxUsername: config.influxUsername || null,
         influxPassword: config.influxPassword || null,
         influxProtocol: config.influxProtocol || INFLUX_DEFAULTS.influxProtocol,
+        influxQueryTimeoutSeconds:
+          config.influxQueryTimeoutSeconds ?? INFLUX_DEFAULTS.influxQueryTimeoutSeconds,
         influxSelfContext: config.influxSelfContext || null
       };
 

package/lib/detection.js

@@ -314,11 +314,16 @@ function createPassageDetector({ db, readSelfPath, settings, clock = Date.now })
   }
 
   function openPassage(now, position, departure) {
+    const startIso = iso(departure.time);
+    // Only a passage that actually precedes this departure can push it later
+    // -- not just whichever entry happens to hold the latest end_time. A
+    // retrospective replay filling a gap before passages logged live (SPEC
+    // §4.10) would otherwise have every reconstructed departure clamped to
+    // the most recent (unrelated, later) passage's end.
     const previousEnd = db
-      .prepare('SELECT MAX(end_time) AS endTime FROM log_entries')
-      .get().endTime;
-    const startTime =
-      previousEnd && iso(departure.time) < previousEnd ? previousEnd : iso(departure.time);
+      .prepare('SELECT MAX(end_time) AS endTime FROM log_entries WHERE start_time < ?')
+      .get(startIso).endTime;
+    const startTime = previousEnd && startIso < previousEnd ? previousEnd : startIso;
     const start = departure.position ?? position;
     const place = initialPlaceName(db, start, settings.placeMatchRadius);
 

package/lib/influx-history.js

@@ -12,7 +12,9 @@ const { AUTOSTATE_SOURCE_PREFIX, MAX_AGE_MS, UNDERWAY_STATES } = require('./dete
 // packets, a VPN not connected) can otherwise hang far longer than this --
 // Node's fetch has no default timeout of its own -- for an error that is no
 // clearer once it finally arrives, so `query` bounds every request itself.
-const QUERY_TIMEOUT_MS = 30 * 1000;
+// Configurable (`influxQueryTimeoutSeconds`): a Raspberry Pi under load can
+// need longer than the default to answer a six-hour chunk.
+const DEFAULT_QUERY_TIMEOUT_SECONDS = 30;
 
 // A resource-constrained host (a Raspberry Pi running both Signal K and
 // InfluxDB) can be brought down by one query spanning weeks across every
@@ -34,7 +36,8 @@ const INFLUX_DEFAULTS = {
   influxPort: 8086,
   influxDatabase: '',
   influxUsername: '',
-  influxPassword: ''
+  influxPassword: '',
+  influxQueryTimeoutSeconds: DEFAULT_QUERY_TIMEOUT_SECONDS
 };
 
 // Everything detection, track recording and observations read live (SPEC
@@ -107,9 +110,11 @@ function createInfluxHistory({
   username,
   password,
   selfContext,
+  queryTimeoutSeconds = INFLUX_DEFAULTS.influxQueryTimeoutSeconds,
   fetch = globalThis.fetch,
   signal
 }) {
+  const queryTimeoutMs = queryTimeoutSeconds * 1000;
   // path -> [{ time, node }], ascending by time; `node` is what readSelfPath
   // answers, built once here rather than on every read.
   const series = new Map();
@@ -131,7 +136,7 @@ function createInfluxHistory({
       epoch: 'ms',
       q: statements.join(';')
     });
-    const timeout = AbortSignal.timeout(QUERY_TIMEOUT_MS);
+    const timeout = AbortSignal.timeout(queryTimeoutMs);
     let response;
     try {
       response = await fetch(url, {
@@ -146,7 +151,7 @@ function createInfluxHistory({
       }
       if (err.name === 'TimeoutError') {
         throw new Error(
-          `InfluxDB at ${protocol}://${host}:${port} did not answer within ${QUERY_TIMEOUT_MS / 1000}s`,
+          `InfluxDB at ${protocol}://${host}:${port} did not answer within ${queryTimeoutSeconds}s`,
           { cause: err }
         );
       }

package/lib/replay-job.js

@@ -71,6 +71,7 @@ function createReplayJob({
       username: settings.influxUsername,
       password: settings.influxPassword,
       selfContext: settings.influxSelfContext || app.selfContext,
+      queryTimeoutSeconds: settings.influxQueryTimeoutSeconds,
       fetch,
       signal
     });

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "signalk-chiplog",
-  "version": "2.2.0",
-  "description": "Automated digital logbook plugin for Signal K, with keyboard/handwritten entry on tablet",
+  "version": "2.3.0",
+  "description": "Nautical logbook for Signal K: automatic entries, handwritten notes",
   "main": "index.js",
   "files": [
     "index.js",