hubitat-drivers

Pattern for keeping a rolling temperature-trend sample buffer in Hubitat state, computing slope over a configurable window, and classifying rising/falling/steady/unknown.

Implement Tuya Local v3.3 Groovy drivers on Hubitat using rawSocket, AES-128-ECB, queued retries, and defensive frame parsing.

Use Hubitat async HTTP plus a request queue to authenticate with Cognito, cache tokens in state, refresh proactively, and replay a single 401-failed request.

When two agents produce overlapping skills in one session, consolidate by merging unique content into the highest-confidence existing skill.

Never let cached-state dedup bypass session validity in cloud-backed Hubitat drivers.

Standard guard pattern for async HTTP response callbacks in Hubitat drivers

Correct formula for converting lat/lng degree differences to miles, with pole clamp for numerical stability

End-users discover drivers via root packageManifest.json and README, not per-driver folder manifests

Cloud polling drivers should call refresh() from updated() for immediate user feedback

Convert sensor temperatures to hub's configured scale (°C or °F) before emitting events

Add opt-in MQTT subscriber support to a Hubitat Groovy driver: connect/disconnect lifecycle, LWT, exponential-backoff reconnect, poll-cadence reduction, and parse() routing.

How to audit an existing community Hubitat driver before deciding to build a competing or replacement driver.

OAuth2 Device Flow for Bosch Home Connect API — app registration, Device Flow auth (no redirect URI), token refresh, rate limits, and fridge door event keys.

How to evaluate whether a cloud IoT API is permanently dead vs temporarily broken, and what to check before writing a new driver.

Template for a Hubitat App + child Driver pair that performs OAuth2 authorization code flow against a cloud API, discovers appliances, and exposes per-appliance children as ContactSensor (or other capability).

Why reverse-engineered consumer auth flows (WebSocket/MQTT/SSO scraping) are dead ends for Hubitat drivers — and what to check before going down that path.

Avoid flooding Hubitat's live-log view by curating catalog dumps, large lists, and error messages.

2026 map of all known Tuya local_key extraction paths — which are portal-free, which require iot.tuya.com, and which are broken. Must re-verify annually.

Diagnose ARGB vs ABGR byte-order mismatches when IoT device colors render wrong after an RGB setColor call.

Capability profile and architecture patterns for heat-only thermostat drivers (electric floor heating, baseboard heat) on Hubitat.

Architecture and lifecycle patterns for a Hubitat parent/child cloud driver where a parent manages auth and discovery, and children hold per-device capability surfaces.

Azure AD B2C auth flow for the Watts® Home API (home.watts.com) used by SunStat Connect Plus and Tekmar WiFi thermostats.

Submit PRs to upstream community JSON registries without mangling formatting or diff hygiene

Prepare Hubitat repository.json metadata and automate GitHub releases from packageManifest version bumps.

Call AWS Cognito InitiateAuth correctly from a Hubitat driver and log failures without leaking secrets.

Avoid Hubitat sandbox and HTTP client failures caused by cross-@Field initializers, blocked JDK APIs, and non-standard content types.

Resolve user-facing IoT scene/effect names to opaque IDs with a cached catalog and safe fallback behavior.

Prepare a local project for a first public GitHub release without leaking internal AI/session artifacts.

{what this skill teaches agents}