Hubitat Run
Apps & Automationhubitat-runHubitat Run is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Send commands to Hubitat devices or interact with app instances
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/integration/hubitat-run/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/hubitat-run, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Hubitat Run Skill
Send commands to devices or interact with app instances on the Hubitat hub.
Instructions
Follow these steps exactly:
Step 1: Read Configuration
Read .hubitat.json from the project root to get hub_ip and check if maker_api credentials are configured (both app_id and token must be non-null).
Step 2: Parse Arguments
$ARGUMENTS can be one of:
{device_id} {command}— a numeric device ID and a command to send (e.g.,42 on,42 off,42 setLevel 50){device_id}— just a device ID to show its current status{filepath}— a.groovyfilename to discover which devices/apps use it- No arguments — prompt the user for what they want to do
Step 3: Smart Discovery (if filepath given)
If the argument looks like a file path (contains / or ends in .groovy):
- Read the file and extract the
namefrom thedefinition()block - Determine if it's an app or driver (based on
apps/ordrivers/in path) - Query the hub:
- Drivers:
curl -s "http://{hub_ip}/hub2/userDeviceTypes"→ find by name → getusedBylist - Apps:
curl -s "http://{hub_ip}/hub2/userAppTypes"→ find by name → getusedBylist
- Drivers:
- Display the list of devices/instances using this code with their IDs and names
- Ask the user which device they want to interact with
Step 4: Execute Command
If Maker API is configured:
To send a command:
curl -s "http://{hub_ip}/apps/api/{app_id}/devices/{device_id}/{command}?access_token={token}"
For commands with arguments (e.g., setLevel 50), the format is:
curl -s "http://{hub_ip}/apps/api/{app_id}/devices/{device_id}/{command}/{value}?access_token={token}"
To get device status:
curl -s "http://{hub_ip}/apps/api/{app_id}/devices/{device_id}?access_token={token}"
Display the device's current attributes in a readable format.
If Maker API is NOT configured:
Maker API is required for sending commands. Tell the user:
- They need to install "Maker API" on their hub
- Add the target device(s) to Maker API's allowed devices
- Update
.hubitat.jsonwith theapp_idandtokenfrom Maker API - Provide the direct link to the device in the hub UI:
http://{hub_ip}/device/edit/{device_id}
Even without Maker API, you can still show device info by querying:
curl -s "http://{hub_ip}/hub2/devicesList"
Find the device by ID and display its current states and attributes.
Step 5: Report Result
After sending a command:
- Wait 1 second for the device to process
- Query the device status again to confirm the state changed
- Report the result: what command was sent, what the device's new state is
Step 6: App Instances
For interacting with app instances (if the user specifies an app):
- Provide the configuration link:
http://{hub_ip}/installedapp/configure/{instance_id} - Show the app's current status from the hub's app list