01
Local hub, local rules
Rules execute on the hub, microseconds after the event. No round-trip to a vendor cloud.
All integrations
Local hub · no cloud
Local automation, with Mum in the dashboard.
Hubitat runs everything locally, on a hub appliance in your house. Connect Getwello and the check-in status becomes a tile in your dashboards, a trigger for any Rule Machine rule, and a data point your whole local network can react to.
Coordinator-only. Included in the £4.99 plan. Same day to set up.
Local dashboard · No cloud
Mum
OK
08:14
Porch
Off
,
Sonos
Played
08:14
Watch
Buzzed
,
Door
Locked
,
Visit
14:00
James
Why this fits Hubitat
Local-first, fast, rule-driven.
02
Dashboards out of the box
Hubitat's built-in dashboards display the virtual device next to your other tiles. No extra app needed.
03
Rule Machine for conditional logic
'If no check-in by 10:00 then escalate' is one rule. Visual editor, easy to adjust.
04
Privacy-friendly
Hubitat doesn't phone home with device events. Strong fit for families who want a smart house that isn't a snitch.
# Cloudflare Worker translating Getwello event
# into a Hubitat Maker API call
const HUB = 'https://your-hub-cloud.hubitat.com/...';
const SENSOR_ID = 123;
await fetch(`${HUB}/devices/${SENSOR_ID}/open`);
await sleep(2000);
await fetch(`${HUB}/devices/${SENSOR_ID}/close`);The hub, doing its thing
One virtual device, every rule you'd want.
The integration creates a virtual contact sensor in Hubitat called 'Mum's check-in'. Every Rule Machine rule, every dashboard, every Hubitat-aware accessory can react to its state. The hub does the rest, locally, instantly, on the network.
- Virtual contact sensor created via Maker API.
- Rule Machine rules listen for state changes.
- Dashboard tile shows time of last check-in.
- Cascade to other Hubitat devices: lights, plugs, sirens.
How to set it up
The high level. Full walkthrough in the help guide.
- 01Step 1 of 4
Enable the Maker API on the hub.
On the Hubitat hub: Apps → Add Built-In App → Maker API. Pick which devices to expose. Note the access token.
- 02Step 2 of 4
Create a virtual contact sensor.
Devices → Add Virtual Device → Type: Virtual Contact Sensor. Name it 'Mum's check-in'. Add it to the Maker API exposed list.
- 03Step 3 of 4
Wire a relay (Cloudflare Worker or similar).
Tiny script that receives our webhook and toggles the sensor via Hubitat's Maker API. Code in the help guide.
- 04Step 4 of 4
Build rules and dashboards.
Use Rule Machine to define behaviour on state changes. Add the sensor to a dashboard for a glanceable status tile.
Frequently asked questions
How is Hubitat different from Home Assistant?
Both run locally. Hubitat is a turnkey hub appliance with a polished web UI; Home Assistant is open-source software you install on your own hardware. Hubitat is faster to start, Home Assistant has more flexibility.
Does Hubitat accept webhooks?
Yes, via its Maker API. You expose a virtual switch or sensor device, then receive POST requests that toggle it. Standard pattern, well-documented.
Does the integration need cloud access?
Only for our webhook to reach the hub. Use Hubitat's built-in cloud relay, or a Cloudflare Tunnel for self-hosted privacy. Once the event arrives, all rules run locally.
Can I use the Rule Machine to build conditional logic?
Yes. Rule Machine handles 'if check-in by 09:00, do nothing; if not, escalate'. The virtual sensor is the trigger.
Will Hubitat dashboards show Mum's status?
Yes. The virtual device appears in any dashboard. Glanceable card showing the last check-in time, plus any other Hubitat devices on the same page.
Other integrations
Pair this with another.
Some families wire two or three at the same time. The webhook fans out, the API keys stay the same.
- Home AssistantOpen-source alternative.
- SmartThingsCloud-based comparison.
- n8nRun the relay self-hosted.
- SonosHubitat speaks Sonos natively.
See every integration or jump to the Developer API overview.
Connect Getwello to Hubitat.
Today.
Mint your first API key in two minutes. Coordinator-only. Included in the £4.99 family plan.
