Chris
33cab10cef
Syncs project memory, custom agents, and commands across machines. Excludes secrets (settings.json), session state, and runtime files. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
969 B
969 B
name, description, type
| name | description | type |
|---|---|---|
| Check for stale/duplicate entities when automations partially fail | HA automations that notify but don't actuate devices — look for duplicate entities from re-paired devices | feedback |
When an HA automation fires (notifications work) but device actions silently fail, check for duplicate entities. Devices that get re-paired create new entities with raw addresses (e.g., switch.0xa4c138...) while the old named entity goes stale.
Why: Chicken sprinkler automation sent notifications fine but switch.turn_on went to a dead entity. The working device had a new entity with a Zigbee address. Silent failure — no error in HA.
How to apply: When debugging partial automation failures, list all entities matching the device name and check last_changed dates. If the named entity hasn't changed in days but a raw-address entity is active, the device was re-paired. Fix by removing the stale entity and renaming the live one.