Spook provides new triggers to Home Assistant. This reference page lists them all and points you to the right documentation for that trigger.
All of these happenedΒΆ
Fires when every one of several triggers has fired inside the same window of time, in any order. Home Assistantβs own triggers are a list where any one of them is enough; this is the other one. #and #together #combination
spook.all_of, documentation π
Cron scheduleΒΆ
Fires on a crontab schedule, for the times Home Assistantβs own time triggers cannot express, like every weekday at seven or the last Friday of the month. #crontab
spook.cron, documentation π
Entity came backΒΆ
Fires when an entity returns after having been unavailable for a while, so a router rebooting does not read as everything in the house recovering. #recovered #back #unavailable
spook.recovered, documentation π
Entity fell silentΒΆ
Fires when nothing has written to an entity for a while, which catches the device that died quietly instead of going unavailable. #stale #silent #dead
spook.stale, documentation π
Integration failed to set upΒΆ
Fires when a configuration entry has been unable to set itself up for a while, past the point where Home Assistantβs own retries would have sorted it out. #integration #broken #config-entry
spook.integration_failed, documentation π
Once it settlesΒΆ
Fires once a trigger has stopped firing for a while, so a burst of them arrives as one. A motion sensor does not report motion once, it reports it twenty times. #debounce #burst #quiet
spook.debounce, documentation π
Repair issue createdΒΆ
Fires when a new repair issue turns up, so you hear about one without visiting the repairs page. Can be narrowed by integration and severity. #repairs #issue
spook.repair_issue_created, documentation π
Repair issue resolvedΒΆ
Fires when a repair issue goes away, either fixed or no longer reported. #repairs #issue
spook.repair_issue_removed, documentation π
Condition turned trueΒΆ
Fires when a condition goes from false to true, using the same condition building blocks as anywhere else. #condition #template
spook.condition_met, documentation π
Triggers in orderΒΆ
Fires when several triggers happen one after another, in the order given, optionally within a time limit. #sequence #order #timeout
spook.sequence, documentation π
While a condition holdsΒΆ
Fires when a condition turns true and keeps firing on an interval for as long as it stays true, without holding a script run open. #condition #repeat #reminder
spook.while, documentation π
WatchdogΒΆ
Fires when something that was expected to happen does not happen in time, without needing a helper entity and a timer to arrange it. #absence #timeout #watchdog
spook.watchdog, documentation π
Entity will not settleΒΆ
Fires when an entity changes state more often than it should within a stretch of time, which is how a failing device usually announces itself. #flapping #device-health #unavailable
spook.flapping, documentation π