BoatKit connects outward to the MQTT broker already used by Home Assistant and publishes one BoatKit device through Home Assistant’s built-in MQTT Discovery support. There is no Python sidecar or custom BoatKit component to install in Home Assistant. After MQTT is configured in Home Assistant and the BoatKit connection succeeds, the device and its entities appear under the MQTT integration.
The first version is intentionally read-only. It publishes supported, user-visible normalized measurements such as tank levels, temperatures, pressure, speed, depth, heading, engine values, electrical values, and on/off state. Home Assistant receives stable entity identities, canonical units, live state, and online/offline availability without needing to understand the NMEA, marine-network, or equipment-specific source behind each value.
Local data path and privacy
Sensor state travels directly from the dedicated BoatKit device to the configured MQTT broker rather than passing through BoatKit Cloud. BoatKit does not publish vessel position through this integration, and Home Assistant cannot send equipment commands or modify BoatKit settings through it.
Use a dedicated MQTT credential with only the publish and subscription permissions required for BoatKit discovery, state, availability, and Home Assistant’s MQTT birth notification. TLS can encrypt the broker connection and verifies the broker certificate with certificate authorities trusted by the BoatKit device.
For connection steps, broker permissions, verification, and troubleshooting, see the Home Assistant setup guide.
Home Assistant is a third-party trademark. This BoatKit integration is not certified or endorsed by Home Assistant.