Push Hubitat Groovy

VerifiedCaution

Push a local Groovy file to a Hubitat hub, compile it, and report the compile status. It identifies the file type (app or driver), extracts the name, finds or creates the entity on the hub, updates the code, and lists devices or apps using it.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#hubitat#groovy#iot#home-automation#push-code

Recommended for

Automated summary

Pushes a local Groovy file (app or driver) to a Hubitat hub, compiles it, and reports the result.

Strengths

  • Automates deployment of code to a Hubitat hub without the web interface
  • Automatically detects the type (app/driver) and name from the file
  • Handles incremental updates via the Hubitat API (version)
  • Reports compilation errors and lists devices/instances using the code

Limitations

  • Requires a .hubitat.json configuration file at the project root
  • Does not create a new code entity if it does not exist on the hub (delegates to another skill)
  • Depends on the hub's HTTP API without authentication (limited security)
When to use it

When developing Groovy apps or drivers for Hubitat and you want to quickly deploy changes to the local hub.

When not to use it

If the hub is not on the local network or you need to manage multiple hubs simultaneously (the skill only handles one hub per project).

Security analysis

Caution
Quality score95/100

The skill uses bash and curl to communicate with a local Hubitat hub on the network, which is legitimate but involves network operations and file system reads. No destructive or exfiltrating actions are present.

No concerns found

How this analysis is made

Examples

Push latest Groovy driver
Push the most recently modified .groovy driver file to the Hubitat hub.
Push specific app file
Push the file apps/my-app.groovy to the Hubitat hub and show me the compilation status.
Push all updated drivers
Find all .groovy files modified in the last hour and push them to the hub.

name: hubitat-push description: Push Groovy app or driver code to Hubitat hub and report compile status argument-hint: "[filepath]" allowed-tools: Bash, Read, Glob, Grep

Hubitat Push Skill

Push a local Groovy file to the Hubitat hub, compile it, and report the result.

Instructions

Follow these steps exactly:

Step 1: Read Configuration

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

Step 2: Identify the File

  • If $ARGUMENTS contains a filepath, use that file.
  • Otherwise, find the most recently modified .groovy file using: ls -t apps/*.groovy drivers/**/*.groovy 2>/dev/null | head -1
  • Confirm the file exists and read its contents.

Step 3: Determine Type (App vs Driver)

  • If the file path contains apps/ → it's an app
  • If the file path contains drivers/ → it's a driver
  • This determines the API endpoints to use:
    • Driver: /hub2/userDeviceTypes, /driver/ajax/code, /driver/ajax/update
    • App: /hub2/userAppTypes, /app/ajax/code, /app/ajax/update

Step 4: Extract Name from Source

Read the file and extract the name value from the definition() block. The format looks like:

definition(
    name: "My Driver Name",
    namespace: "iamtrep",
    ...
)

Extract the name string (the value after name:).

Step 5: Find the Hub ID

Query the hub for the list of user code to find the matching ID:

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

The response is a JSON array. Find the entry where name matches the name extracted in Step 4. Get the id field. Also note the usedBy field for later.

If no match is found, the code is not yet on the hub. Use the /hubitat-install skill to create it, then stop (install will handle creation and report the result). Tell the user you are invoking /hubitat-install.

Step 6: Get Current Version

Fetch the current version number (required for the update API):

  • Drivers: curl -s "http://{hub_ip}/driver/ajax/code?id={ID}"
  • Apps: curl -s "http://{hub_ip}/app/ajax/code?id={ID}"

Extract the version field from the JSON response.

Step 7: Push the Code

POST the updated source to the hub:

  • Drivers: POST http://{hub_ip}/driver/ajax/update
  • Apps: POST http://{hub_ip}/app/ajax/update

Use curl with:

curl -s -X POST "http://{hub_ip}/{type}/ajax/update" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  --data-urlencode "id={ID}" \
  --data-urlencode "version={VERSION}" \
  --data-urlencode "source@{FILEPATH}"

Where {type} is driver or app.

Note: --data-urlencode "source@{FILEPATH}" reads and URL-encodes the file contents automatically.

Step 8: Report Result

Parse the JSON response:

  • On success: {"id":..., "version":..., "status":"success"}
    • Report: "Successfully pushed {name} to hub (version {new_version})"
  • On error: The response will contain error/status details
    • Report the compilation errors clearly so the user can fix them

Step 9: Show Usage

From the data retrieved in Step 5, show which devices or app instances use this code:

  • For drivers: list the devices using this driver (from usedBy in the userDeviceTypes response)
  • For apps: list the installed instances (from usedBy in the userAppTypes response)

Format as a simple list with device/app IDs and names.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/push-hubitat-groovy-mmh8qrqx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/push-hubitat-groovy-mmh8qrqx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/push-hubitat-groovy-mmh8qrqx/download' --output '.skill-downloads/push-hubitat-groovy-mmh8qrqx/SKILL.md.part' && mv '.skill-downloads/push-hubitat-groovy-mmh8qrqx/SKILL.md.part' '.skill-downloads/push-hubitat-groovy-mmh8qrqx/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash, Read, Glob, Grep

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/push-hubitat-groovy-mmh8qrqx/SKILL.md' && test -s '.skill-downloads/push-hubitat-groovy-mmh8qrqx/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/hubitat-push' && cp -R '.skill-downloads/push-hubitat-groovy-mmh8qrqx' '.claude/skills/hubitat-push'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/push-hubitat-groovy-mmh8qrqx'

openskills read 'push-hubitat-groovy-mmh8qrqx'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/push-hubitat-groovy-mmh8qrqx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills