BoatKit discovers a Victron GX device on the vessel network and translates supported MQTT and Modbus data into its common power, tank, and temperature models. Batteries, solar chargers, inverter/chargers, converters, AC sources, generator state, and other available measurements can be understood as one electrical system rather than a collection of product pages.
That normalized state is available to saved power views, history, alarms, and remote monitoring through BoatKit Cloud. On supported installations, administrators can also adjust an active AC input current limit or request generator state with the controls beside the broader electrical picture.
Tanks and temperatures
Enable Modbus TCP on the GX to bring supported tanks and temperatures into BoatKit’s normal Sensors settings, dashboards, history, and warnings, even when GX NMEA 2000 output is disabled. These readings work on the vessel network without Internet access and continue independently of MQTT.
BoatKit links a tank’s direct and NMEA sources when GX forwarding metadata proves an unambiguous match. Ruuvi temperatures mirrored through Signal K use the established identity matching rules. Sensor settings show linked sources and let administrators keep a pair separate. Uncertain matches and ambiguous legacy Modbus addresses remain separate.
See Connect a Victron Cerbo GX for setup and troubleshooting.
Connecting a GX device
The GX device must be reachable on the same local network as the BoatKit host, with local MQTT enabled and its security-profile password supplied when configured. A tablet can connect while its app-hosted runtime is active on the vessel Wi-Fi; a dedicated BoatKit device keeps discovery, history, alarms, and supported controls running continuously.
Available data and controls depend on the Victron equipment and GX configuration. BoatKit’s support is independent and does not imply endorsement or certification by Victron Energy.