Add Shelly from BoatKit’s Automation & IoT integration catalog. BoatKit automatically starts its authenticated MQTT transport on the trusted vessel network, and the Shelly adapter translates recognized topics and payloads into stable, named BoatKit signals. Those signals can participate in dashboards, retained history, availability and threshold alerts, and—when the adapter exposes a confirmed writable output—the common switch-control system.
The first adapter understands Shelly Gen1 conventions and modern RPC-based Shelly conventions. Numeric measurements, boolean inputs, device availability, and supported relay or light outputs are normalized; diagnostic Wi-Fi details and unknown topics are intentionally left out. An MQTT connection by itself is not enough to create a useful BoatKit signal—the device’s message convention must have a BoatKit adapter.
Connecting Shelly devices
On a dedicated BoatKit device, guided discovery scans directly attached vessel networks, reads a Shelly’s identity and MQTT status, and can configure the selected device to use BoatKit’s generated broker credentials. Password-protected Shelly devices ask for their device password at configuration time. App-hosted vessels can accept manually configured MQTT clients while the runtime remains active, but do not currently offer the guided discovery/configuration workflow.
Choose hardware for the real circuit and environment. A Shelly Plus Uni is a low-cost option for low-voltage sensing and dry-contact work and is represented in BoatKit’s current tests. Newer products such as Shelly 1 Gen4 advertise local MQTT, but should be confirmed against the current BoatKit adapter and firmware before purchase. Consumer modules need suitable enclosure, fusing, conductor protection, voltage conversion, and isolation for a marine installation.
The shared broker’s credentials, listener status, and raw-traffic diagnostics live under Settings > Advanced > MQTT Broker. That page appears while Shelly or another MQTT-backed integration is enabled, and can keep the broker running independently when a generic MQTT endpoint is useful.
MQTT, Shelly, and their marks belong to their respective owners. BoatKit’s independent integration does not imply certification or endorsement.