BoatKit can act as a native Saillogger collector. It sends one-minute position records with supported speed, course, wind, depth, temperature, humidity, barometer, battery, engine-hour, and anchor-watch data directly to Saillogger’s device API. For battery monitoring, choose a DC battery bus or let BoatKit automatically use the highest nominal-voltage bus; BoatKit sends the bus-wide average state of charge and voltage from its enabled batteries. BoatKit follows the sensor choices and reporting cadence returned by Saillogger and sends only fresh readings from enabled sources. It can also send fresh targets heard by the boat’s local AIS receiver. Vessel identity metadata accompanies that stream so Saillogger can associate it with the correct boat. No separate Signal K server or Saillogger plugin is required.
The Collector ID is a credential. BoatKit stores it as a write-only device secret, never returns it to Viewer clients, and excludes it from portable backups. Saillogger also recommends using only one collection source per boat; stop an older PredictWind, Victron GX, or Signal K collection path before enabling BoatKit to avoid duplicate voyage points.
Local-first delivery
When the Internet is unavailable, BoatKit continues to queue minute records locally while its vessel runtime and GPS source remain active. It retries those records in order when the connection returns and bounds the queue so an extended seasonal pause cannot fill device storage. A dedicated BoatKit device is the best fit for continuous operation; an app-hosted vessel can collect only while the mobile runtime remains active.
This integration publishes telemetry for Saillogger’s logbook and monitoring experience. It does not import Saillogger logs into BoatKit or synchronize planned routes in either direction.
For the Collector ID path, connection checks, offline behavior, and troubleshooting, see the BoatKit Saillogger setup guide.
Saillogger is a third-party service. This integration does not include a Saillogger account or subscription.