BoatKit rules work with the same named, unit-aware data used by gauges and histories. A rule can follow a selected freshwater tank, a particular battery, or a specific engine measurement without requiring the user to understand the protocol message that supplied it.
Conditions can be a single comparison or a nested combination of all and any groups. One-time rules are useful for questions such as “tell me when the tank reaches 80%”; recurring rules can continue watching for a condition, and any rule can be paused without deleting its configuration. BoatKit retains the latest evaluated state across restarts so an ordinary restart does not look like a new threshold crossing.
From condition to action
Rules can produce supported BoatKit notifications or alarms. Trigger events use the normal delivery and event-history paths, and a completed one-time rule remains visible rather than silently disappearing.
Administrators can build and manage rules in BoatKit itself. On supported platforms, Siri and Shortcuts provide an opt-in way to read vessel data or make confirmed changes, while the Amazon Alexa integration can read supported data and create confirmed rules through BoatKit Cloud. Voice assistants do not bypass BoatKit access controls or the confirmation required for a configuration change.