Have the Notifications tell us which automation triggered a change

Automations have names.

If we could ID which Automation triggered a change it’d be much easier to track down incorrectly functioning automations. Just on the history where it days “Fibery (rule)” add the rule in question so we can backtrack things faster. If a rule is miswritten and is doing the wrong thing it can be painful to track down, but it could be very quick.

Hi @JackC
I feel your pain. We are aware of the issue, but there are some technical obstacles which have blocked us from fixing this so far.
Will keep you posted.

3 Likes