Isilorn
Community@Isilorn · France
Read-only auditing and diagnostics for Jeedom 4.5 home automation installations, covering scenarios, devices, daemons, plugins, and logs.
Agent Skills by Isilorn
Showing 1 vetted skills indexed across 1 GitHub repositories.
Frequently Asked Questions About Isilorn
FAQPage SchemaWhat tasks can I perform with the jeedom-audit skill?▼
You can diagnose misbehaving Jeedom scenarios, get step-by-step explanations of what a scenario does, map device-to-scenario dependencies, audit installation health (dead commands, orphan equipments, daemon and plugin status), assess history quality, and interpret Jeedom logs — all read-only.
Who is the jeedom-audit skill designed for?▼
It targets Jeedom 4.5 home automation users and administrators, including French-speaking users, who need to understand, troubleshoot, or clean up an existing installation. It triggers on Jeedom-specific terms like eqLogic, scenarioElement, virtual switch, jMQTT, dataStore, or #ID# command references.
Does jeedom-audit modify my Jeedom installation?▼
No. The skill is strictly read-only and never modifies the install. It describes issues and suggests cleanups or refactors verbally, providing UI walkthroughs so the user can apply changes manually through the Jeedom interface.
What does the installation health audit cover?▼
The audit checks for dead commands, orphan equipments, daemon status, plugin issues, and history data quality. It then suggests cleanup or refactoring steps verbally, guiding the user through the relevant Jeedom UI screens without making any direct changes.
When does the jeedom-audit skill trigger automatically?▼
It triggers whenever a user asks about an existing Jeedom installation, even without naming Jeedom explicitly. Context clues like eqLogic, scenarioElement, MQTT broker, jMQTT, dataStore, virtual switches, or a French-speaking user describing home automation problems activate it.