Repository navigation
Frigate notification blueprint version 0.14.0.2y issue reported that is not existing #2029
|
Hello everyone... First of...awesome tool...cant imagine how much time goes into it...thx for that. |
Replies: 1 comment
|
Those two actions come from the blueprint, not from anything you wrote: Frigate Notifications 0.14.0.2y has |
Those two actions come from the blueprint, not from anything you wrote: Frigate Notifications 0.14.0.2y has
telegram_bot.send_photoandtelegram_bot.send_videosteps in choose branches that only run when{{ telegram }}is true, so every automation made from it contains them even with no chat ID set. Spook looks through every branch of a choose or if for actions, whether or not that branch can ever run (entity_filtering.py#L883-L891), and without the Telegram bot integration those actions don't exist. Pressing Ignore on those repairs is the fix here, and Spook remembers it per automation, so it only comes back if a new unknown action shows up in that automation. The other way is a local co…