BoatKit can publish its current categorized readings directly to compatible Signal K applications over the local vessel network. Clients can find the endpoint through Signal K discovery, traverse a full read-only REST model, or subscribe to live delta updates over WebSocket. No separate Signal K server or plugin engine is required.
The initial integration presents BoatKit readings as custom sensors below the self vessel. It preserves recognizable BoatKit category names and converts supported measurements to Signal K’s SI wire units, but it does not yet remap those values onto canonical navigation, environment, or electrical paths. Applications that show only predefined Signal K paths may therefore connect without displaying the custom sensors.
Read-only by design
The endpoint does not expose commands, settings, history, or writable control paths. REST writes and WebSocket put requests are rejected, making this a deliberate data-output boundary rather than another route for controlling equipment.
Access can remain open on a trusted vessel LAN or require a BoatKit-managed Signal K username and password. Authentication restricts who can read the endpoint, but ordinary local HTTP and WebSocket connections are not encrypted unless BoatKit is served through TLS.
For setup, authentication, verification, and troubleshooting, see the Signal K output guide.
Signal K is an open data format and ecosystem maintained by the Signal K project. BoatKit compatibility does not imply endorsement or certification by the Signal K project.