Hubitat

A bridge to a Hubitat Elevation hub. Every device the hub exposes becomes a child in reMaestro, and its commands are learned from what Hubitat reports each device can do.

Connection

Two channels:

• Commands go out over Hubitat’s Maker API (HTTP).
• State comes back over Hubitat’s event socket (ws://<host>/eventsocket), which reMaestro dials out to and holds open, reconnecting with backoff if it drops.

The bridge implements IBridgeDevice, trait bridge.

Why the socket and not the webhook

Maker API can post state changes to a webhook, but that needs the Hubitat hub to reach reMaestro — which is exactly what fails when reMaestro runs in a container. The event socket is a connection reMaestro opens outward, so it works from anywhere reMaestro can reach the Hubitat hub, and nothing has to route back.

Setup

• host — the Hubitat hub address.
• appId — the Maker API app id.
• token — the Maker API access token (secret).
• device — the device to expose.

What it can do

Child commands are learned per device (via SetCommands):

Command	What it does
power_on / power_off	Turn a device on or off
refresh	Re-read device state
set_brightness	Set light brightness
set_volume	Set volume
command	Run any command the device reports, with parameters

command is the escape hatch — it runs any command Hubitat reports for a device (for example, a keyPress on a Roku TV that’s bound to Hubitat), so you’re not limited to the mapped verbs above.