OpenParable
Skip to content
← Back to skills

Hubitat Publish

Apps & Automation
hubitat-publish

Hubitat Publish 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.

Publish a driver or app to other Hubitat hubs on the same account

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/integration/hubitat-publish/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/hubitat-publish, 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 Publish Skill

Publish a driver or app's code to all other Hubitat hubs linked to the same account, and report distribution status.

Instructions

Follow these steps exactly:

Step 1: Read Configuration

Read .hubitat.json from the project root to get hub_ip.

Step 2: Identify the Code and Type

Check $ARGUMENTS:

  • If a numeric ID — use it directly. You'll need to determine the type (driver or app) by checking both userDeviceTypes and userAppTypes.
  • If a filepath — determine the type from the path:
    • Path contains drivers/ → it's a driver
    • Path contains apps/ → it's an app
    • Extract the name from the file's definition() block and resolve to an ID.
  • If a name — search both userDeviceTypes and userAppTypes for a case-insensitive match. Get the id and determine the type from which list matched.
  • If no argument — find the most recently modified .groovy file using ls -t apps/*.groovy drivers/**/*.groovy 2>/dev/null | head -1, then resolve as above.

To resolve names to IDs:

  • Drivers: curl -s "http://{hub_ip}/hub2/userDeviceTypes"
  • Apps: curl -s "http://{hub_ip}/hub2/userAppTypes"

If no match is found on the hub, report the error and stop.

Step 3: Publish the Code

Initiate publishing by calling:

curl -s "http://{hub_ip}/hub/publishCode/{type}/{id}"

Where {type} is driver or app.

Report the initial response to the user. The response is JSON like:

{"success":true,"completed":false,"hubs":[{"id":"...","name":"Chalet","status":"Pending"},...]}

Step 4: Check Distribution Status

Poll the publish status endpoint:

curl -s "http://{hub_ip}/hub/publishCode/status"

The response is JSON:

{"success":true,"completed":false,"hubs":[{"id":"...","name":"Chalet","status":"Pending"},{"id":"...","name":"Maison","status":"Done"}]}
  • If completed is false, wait 2 seconds and poll again (up to 15 attempts).
  • Once completed is true (or on error/timeout), report the final status.

Step 5: Report Result

Summarize what happened:

  • Name, type (driver/app), and ID that was published
  • A markdown table of target hubs with columns: Hub Name, Status
  • Any errors encountered