Hubitat Connector
The Hubitat connector links a Hubitat hub to the platform's MQTT broker, in both directions: device state flows from the hub into Yggio, and commands flow from Yggio back to the hub.
What this gives you
Everything the hub speaks, Yggio speaks. This is the point of the connector. Hubitat is a local hub with radios and protocol support of its own, so connecting one brings that entire estate into Yggio as ordinary devices:
- Z-Wave
- Zigbee
- Matter and Thread
- Lutron, LAN and cloud integrations, and anything else Hubitat supports through its own drivers and community drivers
Rather than Yggio needing a radio or an integration per protocol, the hub handles the protocol and Yggio handles the data. A Z-Wave door sensor and a Zigbee plug arrive as devices like any LoRaWAN sensor: same canonical fields, same views, same rules, same reports.
Control works the same way round. Because the connector carries downlinks, a rule in Yggio can switch a Z-Wave relay or set a level on a dimmer, and the resulting state change comes straight back.
Supported operations:
- Devices from the hub appear in Yggio automatically, with their state kept in step
- Commands sent from Yggio are carried out on the hub
- Hub heartbeats are tracked, so a hub that stops reporting is visible
Before you start
The connector is the Yggio half of a larger integration. The Hubitat half, installing Sensative's app and driver on the hub and choosing which devices to share, is covered in Hubitat Integration. Do that alongside this, since each side needs values from the other.
Two things must exist in Yggio before the connector can be created:
| Prerequisite | What it is |
|---|---|
| Basic credentials set | The username and password the hub uses to reach the MQTT broker. Its _id identifies the connector's topic |
| Reserved MQTT topic | Reserves yggio/hubitat/v1/<basicCredentialsSetId> so only your hub can publish there |
Both are created through the API. See Hubitat Integration for the exact calls.
You also need the Hub UID from the Hubitat hub itself, found in its settings.
Creating the Connector
- Navigate to Connectors → New Connector → Hubitat.
- Select the retention policy and flow, then continue.
- Fill in the connector details:
| Field | Description |
|---|---|
| Name | A name for the connector |
| Basic Credentials Set ID | The _id of the basic credentials set created above, for example 66471de08fdcf621179a94ec |
| Hubitat Hub UID | The hub's unique identifier, for example 84af009e-4384-4820-ba7e-4837f21336e4, found in the Hubitat settings |
- Confirm the details and create the connector.
The MQTT topic is derived for you as yggio/hubitat/v1/<basicCredentialsSetId>/#, which is why the
reserved topic has to match the same credentials set.
Verifying
- On the hub, confirm the Sensative Yggio MQTT driver reports as connected.
- Share a device from the Hubitat app and wait for it to report.
- Check that the device appears in Yggio and that its state matches the hub.
- Change the device on the hub, a switch is easiest, and confirm the new state reaches Yggio.
- Trigger the change from Yggio and confirm the hub carries it out.
Troubleshooting
Nothing arrives in Yggio. Almost always the credentials or the topic. Confirm the hub is using
the username and password from the basic credentials set, and that the reserved topic was created
with the same basicCredentialsSetId the connector uses. The broker rejects a connection without
valid credentials whatever the topic is named.
Devices appear but do not update. Check in the Hubitat app that the device is still selected for sharing. Devices added to the hub later are not shared automatically; they must be selected and saved again.
Commands from Yggio do nothing. Confirm the device's driver supports the command being sent, and that the hub is connected rather than merely configured.
For the full walkthrough of both sides, see Hubitat Integration.