What problem does it solve? After deploying a Home Assistant change, it is easy to conclude an automation or entity works when it actually does not — the recorder database goes stale after restarts, automation entity IDs derive from alias slugs rather than IDs, and new Zigbee devices sit in unknown states. This Skill provides ground-truth verification of live HA state so "looks done" matches "is done". ## Core Features & Use Cases - Live entity and automation checks: Query current entity state, attributes, and whether an automation loaded and fired, resolving IDs, alias slugs, or full entity IDs. - Automation trace diagnosis: Inspect per-condition traces to see which condition blocked the last run, plus live error logs for render-time template failures. - Stale-data trap avoidance: Encode the recorder-DB pitfalls — WAL file requirements, pod start-time comparison for live vs stale rows, and expected unknown states for new Zigbee devices. - Use Case: After deploying a new automation, run the probe to confirm it loaded, trigger its condition, and verify last_triggered advanced — instead of trusting a stale recorder row. ## Quick Start Ask the assistant to verify whether a specific Home Assistant automation loaded and fired using the live API probe.
