Menu
Resolve user-facing IoT scene/effect names to opaque IDs with a cached catalog and safe fallback behavior.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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
| name | iot-name-to-id-resolver |
| description | Resolve user-facing IoT scene/effect names to opaque IDs with a cached catalog and safe fallback behavior. |
| domain | iot |
| confidence | medium |
| source | earned |
Use this when an IoT driver or integration exposes effects, scenes, presets, or animations through opaque IDs but the automation surface should accept human-readable names.
displayName -> id) and preserve the original display name for logging/UI.id -> activation payload) alongside the display-name map.drivers/gemstone-lights/gemstone-lights.groovy
refreshEffectCatalog()setEffect(String name)finalizeEffectCatalogRefresh()