skills.rest
Isilorn
IsilornCOMMUNITY
Explore all skills by this author →
GitHub

jeedom-audit

Audit, diagnose, and explain Jeedom 4.5 home automation installations in read-only mode.

Updated Apr 27, 2026
Search Tags:#audit#diagnostics#mysql#scenario#home automation#json-rpc#jeedom
One-click install
npx skills add https://github.com/Isilorn/jeedom-skills --skill jeedom-audit-isilorn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jeedom-audit
Source: https://github.com/Isilorn/jeedom-skills/tree/main/jeedom-audit
Command: npx skills add https://github.com/Isilorn/jeedom-skills --skill jeedom-audit-isilorn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Jeedom home automation installations accumulate broken scenarios, dead commands, orphan variables, and silent plugin failures that are hard to trace through the UI. This Skill gives Claude structural knowledge of the Jeedom 4.5 database, API, and logs so it can audit, diagnose, and explain an installation without ever modifying it. ## Core Features & Use Cases - General health audit: Batch SQL and API checks produce a 12-section report covering plugins, equipments, scenarios, dead commands, dataStore variables, system messages, updates, and history quality. - Scenario diagnosis and explanation: Walks the scenarioElement/scenarioExpression tree to explain what a scenario does step by step, why it does not trigger, and which devices or scenarios depend on a given command (usage graph). - Plugin and equipment diagnostics: Deep references for jMQTT, virtual, calendar, alarm, thermostat, and script plugins, plus a generic 4-step inspection pattern for any other plugin, including daemon and log analysis. - Use Case: Ask why the "Présence Alice" scenario stopped triggering, and get its current state, last launch time, trigger values, recent log entries, and ranked probable causes with UI fix steps. ## Quick Start Ask Claude to run a general audit of your Jeedom installation after configuring SSH or API access with the setup script.

Frequently Asked Questions about jeedom-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose a Jeedom scenario that does not trigger?▼

The skill resolves the scenario by name, walks its expression tree, fetches lastLaunch and state via the JSON-RPC API, checks trigger command values, and reads recent scenario logs over SSH. It returns ranked probable causes with step-by-step UI fix instructions.

How do I audit the health of a Jeedom installation?▼

Ask for a general audit to run batch read-only SQL queries covering plugins, equipments, scenarios, dead commands, dataStore variables, system messages, updates, and history quality. The output is a 12-section report with prioritized recommended actions.

Can this skill modify my Jeedom installation?▼

No, it is strictly read-only. It only runs SELECT queries, blocks all write API methods like cmd::execCmd and scenario::changeState through a blacklist, and responds to modification requests with step-by-step UI instructions instead.

What access do I need to connect to my Jeedom box?▼

You need either an SSH alias with a read-only MySQL user configured in ~/.my.cnf on the box, or a Jeedom API key for JSON-RPC access. The setup.py script guides the configuration and stores credentials in ~/.config/jeedom-audit/credentials.json.

Which Jeedom versions are supported?▼

Jeedom 4.5.x is the nominal supported version. Versions below 4.4 are explicitly refused, 4.4 is refused with a notice, and versions 4.6 or higher trigger a warning that the database schema may differ.

What are the limitations in API-only mode without SSH?▼

In API-only mode, log files are unavailable, so log-based diagnostics are partial and the causal forensics workflow is refused entirely. Structural audits and scenario explanations still work through JSON-RPC methods.

Related Skills

Explore More Software Engineering Skills→
steipetesteipete
388.4k

healthcheck

Audit and harden OpenClaw host security across SSH, firewall, and exposure.

Community
Intermediate
ihj04982ihj04982

build-fix

Resolve TypeScript, compilation, and build errors with minimal diffs.

Community
Intermediate
HouseGarofaloHouseGarofalo
3

zigbee2mqtt

Configure and manage Zigbee devices via Zigbee2MQTT for smart home automation.

Official
Intermediate
jackmcintyrejackmcintyre

ha-mcp-debug

Inspect Home Assistant entity states and access log files for error tracing.

Community
Intermediate