Push Groovy vers Hubitat

VérifiéSûr

Pousse un fichier Groovy local vers un hub Hubitat, le compile et rapporte le statut. Supporte les apps et drivers.

Spar Skills Guide Bot
DeveloppementIntermédiaire
3002/06/2026
Claude Code
#groovy#hubitat#iot#home-automation#code-push

Recommandé pour

Notre avis

Pousse un fichier Groovy local vers un concentrateur Hubitat, le compile et rapporte le résultat.

Points forts

  • Automatise le déploiement de code Groovy sur un Hubitat sans interface manuelle.
  • Détecte automatiquement le type d'application ou de pilote à partir du chemin du fichier.
  • Affiche les erreurs de compilation directement dans le terminal.
  • Gère l'incrémentation de version et les dépendances via les API du hub.

Limites

  • Nécessite un fichier de configuration `.hubitat.json` avec l'adresse IP du hub.
  • Ne fonctionne que pour les fichiers déjà présents sur le hub ; sinon invoque une autre compétence.
  • Dépend de l'API interne de Hubitat, qui peut changer.
Quand l'utiliser

Utilisez cette compétence pour déployer rapidement un script Groovy local vers votre concentrateur Hubitat après l'avoir développé.

Quand l'éviter

Évitez de l'utiliser pour des modifications de configuration ou pour des scripts qui n'ont pas encore été créés sur le hub.

Analyse de sécurité

Sûr
Score qualité93/100

The skill uses curl to push code to a local Hubitat hub via HTTP, which is its intended function. No destructive commands, external data exfiltration, or obfuscation. The network tool usage is legitimate and contained.

Aucun point d'attention détecté

Exemples

Push a specific driver file
Push the file 'drivers/my-driver.groovy' to the Hubitat hub and show compilation status.
Push the most recent Groovy file
Push the latest modified .groovy file from the project to Hubitat and report any errors.
Push an app file
Push the app file 'apps/my-app.groovy' to Hubitat and list installed instances.

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.

Skills similaires