Connect BoatKit to Saillogger

Connect BoatKit to Saillogger to use the vessel positions and trip telemetry BoatKit already receives for automated logging and remote monitoring. BoatKit sends this information directly to Saillogger over the Internet. You do not need a separate Signal K runtime, and uploads do not pass through BoatKit Cloud.

What you need

• Administrator access to the vessel in BoatKit.
• Completed BoatKit vessel setup and registration.
• A Saillogger account with collection available under its current trial or subscription terms.
• BoatKit receiving a recent, trusted GPS position. No Saillogger-specific hardware or separate Signal K runtime is required.
• An outbound Internet connection for live uploads. BoatKit can queue records during an outage, as described under Offline operation.

Saillogger maintains its own boat connection instructions and account requirements.

Use only one collector

Before enabling BoatKit, stop any PredictWind, Victron GX, or Signal K Saillogger collector configured for the same Saillogger boat. Running more than one collector can produce duplicate voyage points.

Connect BoatKit

1. Sign in to Saillogger and open Settings > Boat > Identity.
2. Copy the Collector ID. Saillogger treats this value as a credential, so protect it like a password.
3. In BoatKit, open Settings > Integrations.
4. Select Add Integration, then Cloud Logging > Saillogger.
5. Enter the Collector ID.
6. Enable Saillogger integration.

BoatKit begins making direct outbound collector requests to Saillogger. No Signal K configuration is needed.

Confirm it is working

In the BoatKit Saillogger panel, check the following:

• The connection message says Saillogger is receiving BoatKit collector requests.
• Last upload shows a recent successful upload. Before the first successful upload, the panel shows the most recent attempt instead.
• The number of records waiting to upload falls to zero when the Internet connection is available.

A zero queue is healthy when BoatKit also has a current GPS position, shows a recent successful upload, and Saillogger reports the boat online. A zero queue by itself does not confirm position collection because BoatKit does not create a record without a recent, trusted GPS position.

Next, open Settings > Boat in Saillogger and check its boat status card. Saillogger may take a few minutes to show Online. See Check Your Connection for Saillogger's status guidance.

Trip finalization is separate from collector connectivity. Saillogger normally finalizes a trip after the vessel arrives, and its first trip may take about an hour to appear.

What BoatKit sends

Every minute, when a recent trusted GPS position is available, BoatKit queues one collector record containing the position and supported current trip telemetry. When available and current, this can include:

• Speed over ground and course over ground
• Apparent wind
• True and magnetic heading
• Fresh port and starboard engine hours
• The active BoatKit anchor-watch circle, distance, and alarm state

BoatKit asks Saillogger which offered readings the owner selected under Settings > Sensors, then includes those readings by their Signal K path in each sample. BoatKit currently offers its available navigation, wind, and engine-runtime readings. It does not claim to export every BoatKit sensor.

When the owner enables local AIS traffic in Saillogger and BoatKit is receiving AIS aboard, BoatKit also sends periodic snapshots of fresh NMEA 2000 or NMEA 0183 targets. Cloud-sourced AIS targets are not echoed back to Saillogger.

Saillogger's boat settings receive these BoatKit values:

• Boat name uses the canonical name under Settings > BoatKit System > Vessel Info. BoatKit leaves the field unchanged until that cloud-owned name is available; it never substitutes the vessel make and model.
• MMSI uses the vessel MMSI under Settings > Charts & Routes > Charts. BoatKit leaves it unknown rather than inventing an MMSI when that setting is empty.
• Monitoring device identifies the BoatKit hardware target and platform.
• Plugin version reports BoatKit's Saillogger integration compatibility version. BoatKit currently reports 3.0.0 so Saillogger enables the corresponding device-integration features.

Saillogger's v2 device API does not define a make-and-model metadata field. That value remains managed in Saillogger instead of being placed in the boat-name field.

BoatKit sends identity once when the collector starts, again after a one-minute startup warm-up, whenever Saillogger asks for a refresh, and hourly thereafter.

Offline operation

An Internet outage does not stop local collection while BoatKit, its vessel runtime, and the GPS source remain active. BoatKit queues unsent minute records locally and retries them in order when connectivity returns.

The recovery queue is bounded to a rolling 31 days of one-minute records so a seasonal subscription pause cannot fill the device's storage. BoatKit retries an inactive Saillogger boat slowly and resumes ordered delivery when the boat becomes active. Saillogger's live monitoring remains stale until queued records can be uploaded.

A dedicated BoatKit device can collect continuously while the device, BoatKit runtime, and GPS source remain running. An app-hosted mobile vessel collects only while the BoatKit app and its vessel runtime remain active; it is not an always-on collection path.

Collector ID and backups

BoatKit stores the Collector ID as a write-only device secret. It is never returned to Viewer clients and is excluded from portable backups. Review Saillogger's account and privacy documentation for Saillogger-owned credential and account behavior.

Replacing the Collector ID or removing the Saillogger integration clears all queued Saillogger records. This prevents stored locations from being delivered to a different Saillogger boat. There is no separate credential-clear control. The recovery queue is also excluded from portable backups.

After restoring a BoatKit portable backup, enter the Collector ID again before enabling the integration.

Current limitations

The integration currently publishes vessel telemetry to Saillogger. It does not:

• Pull Saillogger logs into BoatKit
• Synchronize planned routes in either direction
• Upload DSC calls
• Accept Saillogger anchor-watch commands or expose other Saillogger controls inside BoatKit

Saillogger is a third-party service. BoatKit does not supply the Saillogger account, subscription, privacy policy, or service availability.

Troubleshooting

Symptom	What to check
Saillogger is not available under Add Integration	Confirm that you have administrator access and that BoatKit is up to date. If Saillogger is marked Added, open the existing integration instead.
Saillogger did not recognize the Collector ID	Copy the Collector ID again from the correct boat under Settings > Boat > Identity. Do not use an account password or an ID from another boat.
Boat name or MMSI is Unknown in Saillogger	Set the vessel name under Settings > BoatKit System > Vessel Info and the nine-digit MMSI under Settings > Charts & Routes > Charts. Allow a minute for startup refresh, then reload Saillogger.
BoatKit is connected, but no position records appear	Confirm that BoatKit currently shows a valid position from a trusted GPS source. BoatKit does not queue a minute record when the position is missing or no longer recent.
Could not reach Saillogger	Check the vessel's Internet connection. BoatKit connects directly outbound to Saillogger, so BoatKit Cloud connectivity does not carry these uploads.
The number of records waiting to upload keeps growing	Check the connection message and the most recent upload attempt. BoatKit is collecting locally but Saillogger has not acknowledged those records, commonly because the Internet path or Saillogger service is unavailable. Keep the Collector ID unchanged if you want BoatKit to retain the queued positions.
Zero records are waiting to upload	This is normal when the last upload is recent, BoatKit has current GPS data, and Saillogger reports the boat online. If those other checks fail, zero records may instead mean that BoatKit has not received a recent trusted position.
Saillogger is online, but the trip is not finalized	Check again after arrival and allow about an hour for the trip to appear. Collector connectivity can be healthy before Saillogger finishes processing a trip.
Trips or voyage points are duplicated	Stop any PredictWind, Victron GX, or Signal K collector still sending data for the same Saillogger boat. Only one collector should remain active.

For Saillogger-owned connection status and service behavior, continue with Saillogger's connection checks.