signalk-chiplog 2.0.0 → 2.1.0

package/CHANGELOG.md

@@ -1,62 +1,169 @@
 # Changelog
 
-All notable changes to Chiplog are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project uses [Semantic Versioning](https://semver.org/).
+All notable changes to Chiplog are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project uses
+[Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [2.1.0] - 2026-09-17
+
+### Added
+
+- Crew list: a per-passage roster of who is aboard, shown as a compact list on the tablet's main screen and editable
+  from a dialog that picks from — and can extend — a global crew roster (name + optional role, e.g. skipper/crew),
+  without an admin login the same way a place name can be corrected. A name typed there is added to the roster and
+  picked at once, immediately correctable or permanently removable with its own icons, right alongside every other name.
+  A new passage starts with the same crew as the one before it, still adjustable. Shown read-only, one member per line,
+  in its own card on the webapp's passage page, and in the PDF logbook's departure line; included in the JSON export
+  (`GET /entries/:id`'s `crew`, `GET /crew`, `PATCH`/`DELETE /crew/:id`, `PUT /entries/:id/crew`).
+- Marine weather forecast: fetched near the departure position for the next 24 hours when a passage opens (Open-Meteo
+  Forecast and Marine, free and keyless, can be turned off with its own setting), shown — titled with the departure
+  place — on the passage page as a table every 3 hours (sky and rain, wind as a Beaufort force with direction, speed and
+  gusts, waves, swell, pressure, visibility, air and sea temperature, and current), in a full-width block of its own
+  above the day's table in the PDF logbook, and in the JSON export (`GET /entries/:id/weather`). Far from the sea, the
+  atmospheric part is kept on its own.
+- PDF logbook: the tide forecast's high and low times and heights, and the tanks and batteries noted as the passage
+  opened, now print side by side in a block of their own, below the weather forecast and above the day's table.
+
+### Changed
+
+- A passage now closes as soon as the boat stops, instead of 30 minutes later: its arrival is named, its arrival reading
+  taken and the USB copy written straight away. Leaving again within that tolerance reopens the same passage, the stop
+  being kept on its timeline as a stopover line naming the place, as a merge does, followed by a departure line at the
+  time the boat set off again — with its instrument reading, and in the PDF as "Departure from" the stopover's place. A
+  passage closed from the webapp is never reopened. Casting off from the tablet within the tolerance of an arrival goes
+  to the passage that just ended, which carries on once the boat moves. The "Stop duration that ends a passage" setting
+  (`stopClosureMinutes`, unchanged) is now titled "Stop duration within which a new departure continues the passage".
+- The "Tide service" setting is now titled "Marine service", since the weather forecast also reads the sea state and
+  current from it. The setting itself (`tideUrl`) is unchanged.
+
+### Fixed
+
+- A new passage's tide and weather forecasts are fetched as soon as it opens, instead of up to a minute later — or up to
+  an hour later when an earlier passage's fetch had kept failing while offline, since the retry delay carried over from
+  one passage to the next.
+- On a phone, the webapp no longer scrolls sideways: the top navigation wraps onto a second line when it does not fit,
+  and the cards shown side by side on a wide screen (tide, engine and sail, boat status) now shrink to the screen width
+  instead of staying 420 px wide.
+
 ## [2.0.0] - 2026-09-16
 
 ### Added
 
-- The passage page has a **Boat status** card: each engine's hour counter, at departure and arrival, and every tank's level (and volume) and every battery's charge, voltage and current as noted at departure. Tanks and batteries are noted once on the passage as it opens (`startTanks`, `startBatteries`), whether detection or the crew opens it, and included in the JSON export.
-- Merging two entries now keeps a record of the stop between them: a `stopover` line on the surviving passage's timeline, naming the place and its position — previously that information was silently lost once the merge took the later entry's arrival as its own.
-- The passage page's track map now shows a small boat marker at the selected point, pointing along its heading, and a scrubber under the map to step back and forth through the track's history — it defaults to the latest point, doubling as the current position on a passage in progress. A band below it shows that point's time, SOG, COG, STW, TWS, TWD, TWA and AWA. Speed through water now rides along with every track point like wind and heading already did, not just the hourly instrument snapshot.
-- Retrospective analysis: a new **Retrospective** page reconstructs past passages for a date range from a [signalk-to-influxdb](https://github.com/tkurki/signalk-to-influxdb) history (InfluxDB 1.x, local or remote — a new recommended companion plugin), through the exact same detection pipeline used live rather than a separate implementation. Runs in the background with a progress bar, refuses a range that overlaps a passage already on record, refuses to run at all while a passage is under way (it would be driving that same live passage through the replay's detector at the same time), and can be cancelled mid-way without losing what it already reconstructed. Data is matched to this server's own vessel identity by default, overridable (`influxSelfContext`) for running it from a different Signal K server than the one that wrote the history; a mismatch fails with the vessel contexts actually found, rather than reconstructing nothing with no explanation. An InfluxDB that never answers — unreachable, or overloaded — fails after 30 seconds with the actual connection problem, rather than hanging indefinitely on a generic "fetch failed". A quick first pass reads one mean speed per minute to find when the boat moved, and only those stretches are then fetched — one value per track interval — and replayed, committing once per ten simulated minutes, and the page sums up what a run added (passages, distance, engine and sail time, track points, events): a month now takes seconds rather than the best part of an hour, and no longer holds every raw reading of the range in memory. Requests stay bounded (a week for the scan, six hours for a stretch) with a short pause between them, so a multi-week reconstruction cannot overwhelm a database sharing a resource-constrained host (a Raspberry Pi) with Signal K itself; cancelling works at any stage. A replay wakes the place-naming lookup immediately once it finishes, rather than leaving newly-reconstructed departures and arrivals waiting out whatever backoff that chain was already in. Signal K alarms are not reconstructed, since a typical InfluxDB history does not archive notifications the way it does a numeric reading, nor are weather events while the boat lay still between passages, nor the extra track points live recording adds on turns and speed changes.
+- The passage page has a **Boat status** card: each engine's hour counter, at departure and arrival, and every tank's
+  level (and volume) and every battery's charge, voltage and current as noted at departure. Tanks and batteries are
+  noted once on the passage as it opens (`startTanks`, `startBatteries`), whether detection or the crew opens it, and
+  included in the JSON export.
+- Merging two entries now keeps a record of the stop between them: a `stopover` line on the surviving passage's
+  timeline, naming the place and its position — previously that information was silently lost once the merge took the
+  later entry's arrival as its own.
+- The passage page's track map now shows a small boat marker at the selected point, pointing along its heading, and a
+  scrubber under the map to step back and forth through the track's history — it defaults to the latest point, doubling
+  as the current position on a passage in progress. A band below it shows that point's time, SOG, COG, STW, TWS, TWD,
+  TWA and AWA. Speed through water now rides along with every track point like wind and heading already did, not just
+  the hourly instrument snapshot.
+- Retrospective analysis: a new **Retrospective** page reconstructs past passages for a date range from a
+  [signalk-to-influxdb](https://github.com/tkurki/signalk-to-influxdb) history (InfluxDB 1.x, local or remote — a new
+  recommended companion plugin), through the exact same detection pipeline used live rather than a separate
+  implementation. Runs in the background with a progress bar, refuses a range that overlaps a passage already on record,
+  refuses to run at all while a passage is under way (it would be driving that same live passage through the replay's
+  detector at the same time), and can be cancelled mid-way without losing what it already reconstructed. Data is matched
+  to this server's own vessel identity by default, overridable (`influxSelfContext`) for running it from a different
+  Signal K server than the one that wrote the history; a mismatch fails with the vessel contexts actually found, rather
+  than reconstructing nothing with no explanation. An InfluxDB that never answers — unreachable, or overloaded — fails
+  after 30 seconds with the actual connection problem, rather than hanging indefinitely on a generic "fetch failed". A
+  quick first pass reads one mean speed per minute to find when the boat moved, and only those stretches are then
+  fetched — one value per track interval — and replayed, committing once per ten simulated minutes, and the page sums up
+  what a run added (passages, distance, engine and sail time, track points, events): a month now takes seconds rather
+  than the best part of an hour, and no longer holds every raw reading of the range in memory. Requests stay bounded (a
+  week for the scan, six hours for a stretch) with a short pause between them, so a multi-week reconstruction cannot
+  overwhelm a database sharing a resource-constrained host (a Raspberry Pi) with Signal K itself; cancelling works at
+  any stage. A replay wakes the place-naming lookup immediately once it finishes, rather than leaving
+  newly-reconstructed departures and arrivals waiting out whatever backoff that chain was already in. Signal K alarms
+  are not reconstructed, since a typical InfluxDB history does not archive notifications the way it does a numeric
+  reading, nor are weather events while the boat lay still between passages, nor the extra track points live recording
+  adds on turns and speed changes.
 
 ### Fixed
 
-- The arrival instrument snapshot (`entry_end`) is now dated from the moment the passage actually ended, not from the later tick that found out about it once the stop had held past the closure threshold (up to `stopClosureMinutes`) — it could otherwise sort after an hourly reading taken during that wait, even though the passage had already ended before that reading was taken.
+- The arrival instrument snapshot (`entry_end`) is now dated from the moment the passage actually ended, not from the
+  later tick that found out about it once the stop had held past the closure threshold (up to `stopClosureMinutes`) — it
+  could otherwise sort after an hourly reading taken during that wait, even though the passage had already ended before
+  that reading was taken.
 
 ## [1.2.0] - 2026-09-15
 
 ### Added
 
-- The tablet app's handwriting pad now fills the whole screen and has a toolbar: fine pen, thick pen, highlighter, eraser, undo and a choice of colour (kept to the theme's colour in night mode). The eraser removes only the points it touches, splitting a stroke instead of deleting all of it; undo now steps back through erasing too, not just strokes. A stroke's colour and tool travel with it to the webapp's timeline and the PDF export, not just the tablet.
+- The tablet app's handwriting pad now fills the whole screen and has a toolbar: fine pen, thick pen, highlighter,
+  eraser, undo and a choice of colour (kept to the theme's colour in night mode). The eraser removes only the points it
+  touches, splitting a stroke instead of deleting all of it; undo now steps back through erasing too, not just strokes.
+  A stroke's colour and tool travel with it to the webapp's timeline and the PDF export, not just the tablet.
 
 ### Fixed
 
-- The tablet app's stylus canvas now prevents the default action on every contact, not just the pen's — a resting palm's touch was left to the browser, which could hijack it as a gesture and cancel the pen's in-progress stroke, or show a native text-selection highlight over the canvas. iOS Safari's long-press selection callout on the canvas needed the whole entry app, not just the canvas, to opt out of selection to reliably stay away, plus blocking `selectstart`/`contextmenu`/`dragstart` directly since the CSS alone is unreliable on some iOS versions.
-- Quickly lifting and reapplying the pen could have its next stroke silently dropped: the previous contact's pointerup can arrive after the next one's pointerdown, which read as "still drawing" and refused to start the new stroke.
-- Worked around an iPadOS Safari/Scribble bug that could swallow a pen's pointer events mid-stroke, dropping strokes or having them mistakenly typed into the comment field, by also preventing the canvas's underlying touch events directly, not just the pointer ones.
-- An autopilot engagement, disengagement or mode change now takes an instrument snapshot like every other automatic event, instead of logging the change with no conditions attached.
+- The tablet app's stylus canvas now prevents the default action on every contact, not just the pen's — a resting palm's
+  touch was left to the browser, which could hijack it as a gesture and cancel the pen's in-progress stroke, or show a
+  native text-selection highlight over the canvas. iOS Safari's long-press selection callout on the canvas needed the
+  whole entry app, not just the canvas, to opt out of selection to reliably stay away, plus blocking
+  `selectstart`/`contextmenu`/`dragstart` directly since the CSS alone is unreliable on some iOS versions.
+- Quickly lifting and reapplying the pen could have its next stroke silently dropped: the previous contact's pointerup
+  can arrive after the next one's pointerdown, which read as "still drawing" and refused to start the new stroke.
+- Worked around an iPadOS Safari/Scribble bug that could swallow a pen's pointer events mid-stroke, dropping strokes or
+  having them mistakenly typed into the comment field, by also preventing the canvas's underlying touch events directly,
+  not just the pointer ones.
+- An autopilot engagement, disengagement or mode change now takes an instrument snapshot like every other automatic
+  event, instead of logging the change with no conditions attached.
 
 ## [1.1.0] - 2026-09-15
 
 ### Added
 
-- A summary above the logbook's day-grouped list: number of passages, total distance and total time, across every passage logged rather than just the pages currently loaded (`GET /entries/stats`).
-- Tide forecast: fetched near the departure position for the next 24 hours when a passage opens (Open-Meteo Marine, free and keyless, configurable and can be turned off), shown on the passage page with the departure's place, the date, time and height of each high/low tide, and the water height curve. Sits next to the engine/sail card, each taking about half the width on a wide screen instead of the full width. Heights are relative to mean sea level, not the chart datum nautical tide tables use, and the app says so (`datum: "msl"` in the API).
-- Editing and deleting logbook lines from the webapp's passage page: any line's comment can be corrected, and a manoeuvre or note the crew logged themselves can be deleted (automatic lines — alarms, autopilot, weather, corrections — can only be annotated).
-- Highest speed and wind seen on a passage, shown alongside the average speed on the passage page (`maxSpeed`/`maxWindSpeed` in the API). Wind (true and apparent) and heading now ride along with every track point, not just the hourly instrument snapshot, so a gust between snapshots is no longer missed.
-- Automatic engine/sail switches now show as a line in the passage log, not just on the engine/sail strip, with the conditions at that moment (`propulsion_change` event).
-- Facsimile PDF logbook: A4 landscape, a page per day in ship's time, with time, position, course, speed, wind, barometer, depth, engine or sail and remarks; departure and arrival lines with passage totals, day totals, handwritten notes drawn. Downloadable from the export page in the webapp's language and the device's time zone.
-- Engine hours of every engine: each engine's hour counter is recorded in readings, shown at departure and arrival with the hours run on the passage page and in the PDF, and exported as one CSV column per engine and in the JSON (`engineRuntimes`).
-- One PDF per passage in the USB copy, in the new logbook language and ship's time zone settings. Existing copies gain their PDFs at the next copy.
+- A summary above the logbook's day-grouped list: number of passages, total distance and total time, across every
+  passage logged rather than just the pages currently loaded (`GET /entries/stats`).
+- Tide forecast: fetched near the departure position for the next 24 hours when a passage opens (Open-Meteo Marine, free
+  and keyless, configurable and can be turned off), shown on the passage page with the departure's place, the date, time
+  and height of each high/low tide, and the water height curve. Sits next to the engine/sail card, each taking about
+  half the width on a wide screen instead of the full width. Heights are relative to mean sea level, not the chart datum
+  nautical tide tables use, and the app says so (`datum: "msl"` in the API).
+- Editing and deleting logbook lines from the webapp's passage page: any line's comment can be corrected, and a
+  manoeuvre or note the crew logged themselves can be deleted (automatic lines — alarms, autopilot, weather, corrections
+  — can only be annotated).
+- Highest speed and wind seen on a passage, shown alongside the average speed on the passage page
+  (`maxSpeed`/`maxWindSpeed` in the API). Wind (true and apparent) and heading now ride along with every track point,
+  not just the hourly instrument snapshot, so a gust between snapshots is no longer missed.
+- Automatic engine/sail switches now show as a line in the passage log, not just on the engine/sail strip, with the
+  conditions at that moment (`propulsion_change` event).
+- Facsimile PDF logbook: A4 landscape, a page per day in ship's time, with time, position, course, speed, wind,
+  barometer, depth, engine or sail and remarks; departure and arrival lines with passage totals, day totals, handwritten
+  notes drawn. Downloadable from the export page in the webapp's language and the device's time zone.
+- Engine hours of every engine: each engine's hour counter is recorded in readings, shown at departure and arrival with
+  the hours run on the passage page and in the PDF, and exported as one CSV column per engine and in the JSON
+  (`engineRuntimes`).
+- One PDF per passage in the USB copy, in the new logbook language and ship's time zone settings. Existing copies gain
+  their PDFs at the next copy.
 - Screenshots for the Signal K App Store listing (`signalk.screenshots` in `package.json`).
 
 ### Changed
 
-- The tablet app's comment and delete actions on a recent entry are now icon buttons, keeping the same touch target size.
+- The tablet app's comment and delete actions on a recent entry are now icon buttons, keeping the same touch target
+  size.
 - Times are shown on the 24-hour clock in English too.
 
 ### Fixed
 
-- The log reading in instrument snapshots now comes from `navigation.log` (the total, non-resettable distance log), not `navigation.trip.log`, which a crew resetting the trip counter could zero out mid-passage.
-- Renaming a departure or arrival now also renames that place on every later passage that already reused it, as documented; an earlier passage keeps the name it recorded.
+- The log reading in instrument snapshots now comes from `navigation.log` (the total, non-resettable distance log), not
+  `navigation.trip.log`, which a crew resetting the trip counter could zero out mid-passage.
+- Renaming a departure or arrival now also renames that place on every later passage that already reused it, as
+  documented; an earlier passage keeps the name it recorded.
 - An alarm's message is no longer repeated as its comment in the passage log.
-- The arrival correction field no longer appears, and is refused by the API (`409 entry_active`), on a passage still in progress — it has no arrival yet, only a moving last-seen position.
-- A note or handwritten sketch logged live now takes an instrument snapshot too, like a manoeuvre already did, so the conditions it was written in show in the log.
-- The App Store icon (`signalk.appIcon`) pointed at a non-existent `icon.svg` at the package root; the icon has always lived at `public/icon.svg`.
+- The arrival correction field no longer appears, and is refused by the API (`409 entry_active`), on a passage still in
+  progress — it has no arrival yet, only a moving last-seen position.
+- A note or handwritten sketch logged live now takes an instrument snapshot too, like a manoeuvre already did, so the
+  conditions it was written in show in the log.
+- The App Store icon (`signalk.appIcon`) pointed at a non-existent `icon.svg` at the package root; the icon has always
+  lived at `public/icon.svg`.
 
 ## [1.0.0] - 2026-09-13
 
@@ -66,19 +173,29 @@ First release.
 
 #### Logbook
 
-- One logbook entry per passage, opened when the boat gets under way and closed when it arrives, with a configurable tolerance for short stops (30 minutes by default).
-- Under way or stopped decided from `navigation.state` published by [signalk-autostate](https://github.com/meri-imperiumi/signalk-autostate), or from speed over ground averaged over 3 minutes when it is absent. Departures and arrivals are dated from raw speed, so the passage starts where the boat actually left.
-- signalk-autostate's value is preferred when another source, such as the boat's own AIS transponder, also publishes `navigation.state`. When detection works from speed alone, the apps say why.
+- One logbook entry per passage, opened when the boat gets under way and closed when it arrives, with a configurable
+  tolerance for short stops (30 minutes by default).
+- Under way or stopped decided from `navigation.state` published by
+  [signalk-autostate](https://github.com/meri-imperiumi/signalk-autostate), or from speed over ground averaged over 3
+  minutes when it is absent. Departures and arrivals are dated from raw speed, so the passage starts where the boat
+  actually left.
+- signalk-autostate's value is preferred when another source, such as the boat's own AIS transponder, also publishes
+  `navigation.state`. When detection works from speed alone, the apps say why.
 - Passages closed at their last movement after a power cut; passages split by a long stop can be merged back.
-- GPS track at a configurable interval (15 s by default), with extra points on turns and speed changes; distance from the track.
-- Engine and sail periods from engine revolutions, engine state, `navigation.state` or a configurable default, with manual correction.
+- GPS track at a configurable interval (15 s by default), with extra points on turns and speed changes; distance from
+  the track.
+- Engine and sail periods from engine revolutions, engine state, `navigation.state` or a configurable default, with
+  manual correction.
 - Instrument readings at departure, every hour on the hour (configurable), at arrival and with each live manoeuvre.
-- Automatic events: Signal K alarms and emergencies, autopilot changes, true wind crossing configurable thresholds, barometer falling over 3 hours.
-- Departure and arrival names from known places, then online geocoding (any Nominatim-compatible service, can be turned off); a renamed place is remembered for later passages.
+- Automatic events: Signal K alarms and emergencies, autopilot changes, true wind crossing configurable thresholds,
+  barometer falling over 3 hours.
+- Departure and arrival names from known places, then online geocoding (any Nominatim-compatible service, can be turned
+  off); a renamed place is remembered for later passages.
 
 #### Logbook webapp
 
-- Status bar, passages grouped by day, passage page with map (OpenStreetMap and OpenSeaMap), engine and sail periods, and the log of readings and events, handwritten notes included.
+- Status bar, passages grouped by day, passage page with map (OpenStreetMap and OpenSeaMap), engine and sail periods,
+  and the log of readings and events, handwritten notes included.
 - Corrections: rename departure or arrival, switch an engine or sail period, close, merge and delete passages.
 - Export of the whole logbook or a date range as JSON, CSV (nautical units) or GPX.
 - English and French.
@@ -86,7 +203,8 @@ First release.
 #### Tablet entry app
 
 - Installable app at `/signalk-chiplog/entry/`, designed for gloves and wet fingers, with a red night mode.
-- Manoeuvre shortcuts, with the sail picked on a sail change; casting off or weighing anchor opens the passage before the boat moves.
+- Manoeuvre shortcuts, with the sail picked on a sail change; casting off or weighing anchor opens the passage before
+  the boat moves.
 - Keyboard notes and stylus handwriting with pressure and palm rejection.
 - Undo and comment right after each entry; latest entries with edit and delete.
 - Entries kept on the tablet while the Wi-Fi is down and sent in order when it is back, never twice.
@@ -94,15 +212,18 @@ First release.
 
 #### Abandon-ship copy
 
-- One JSON, CSV and GPX file per passage on a USB drive, named to sort by date, written only when new or changed, with obsolete files removed.
-- Copied automatically every 15 minutes and at each arrival (both configurable), or on demand; a missing drive is reported in the plugin status and on the export page.
+- One JSON, CSV and GPX file per passage on a USB drive, named to sort by date, written only when new or changed, with
+  obsolete files removed.
+- Copied automatically every 15 minutes and at each arrival (both configurable), or on demand; a missing drive is
+  reported in the plugin status and on the export page.
 
 #### API and data
 
 - 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.0.0...HEAD
+[Unreleased]: https://github.com/ricard33/signalk-chiplog/compare/v2.1.0...HEAD
+[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
 [1.2.0]: https://github.com/ricard33/signalk-chiplog/compare/v1.1.0...v1.2.0
 [1.1.0]: https://github.com/ricard33/signalk-chiplog/compare/v1.0.0...v1.1.0