Push vers Hubitat

VérifiéPrudence

Pousse du code Groovy vers un hub Hubitat, compile et rapporte le statut. Supporte les apps et drivers avec détection automatique du type et gestion des versions.

Spar Skills Guide Bot
DeveloppementIntermédiaire
4002/06/2026
Claude Code
#hubitat#groovy#home-automation#code-deployment

Recommandé pour

Notre avis

Cette compétence pousse un fichier Groovy local vers un hub Hubitat, le compile et rapporte le résultat.

Points forts

  • Automatise le déploiement de code sur Hubitat sans interface web
  • Gère la détection du type (app/driver) et l'extraction du nom
  • Identifie l'ID du code existant et gère la mise à jour avec version
  • Affiche les appareils ou instances utilisant le code après déploiement

Limites

  • Nécessite un fichier de configuration .hubitat.json avec l'IP du hub
  • Dépend de la structure exacte du répertoire (apps/, drivers/)
  • Ne crée pas de nouveau code sur le hub (utilise /hubitat-install pour cela)
Quand l'utiliser

Utilisez cette compétence pour mettre à jour rapidement un pilote ou une application Groovy existante sur votre hub Hubitat.

Quand l'éviter

Évitez de l'utiliser pour du code non encore présent sur le hub (préférez /hubitat-install) ou pour des hubs avec des configurations réseau non standards.

Analyse de sécurité

Prudence
Score qualité88/100

The skill uses Bash and curl to interact with a local Hubitat hub over HTTP, sending source code and triggering compilation. While intended for legitimate development, it involves network operations and code execution on a local device, warranting caution.

Aucun point d'attention détecté

Exemples

Push most recent Groovy file
Push the latest Groovy file to my Hubitat hub.
Push specific driver file
Push the driver at ./drivers/power-monitor.groovy to my Hubitat hub.
Push specific app file
Push the app at ./apps/light-scheduler.groovy to my Hubitat 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.

Skills similaires