My guess is that the button you are double-pressing may occasionally be detected as two consecutive double-presses. The first one triggers the automation and, while it’s opening the cover and unlocking the lock, the second double-press is detected. However, because the automation is set to single mode, the second double-press is ignored (but reported).
If you want to continue ignoring the second double-press but don’t want a message logged each time it happens, add this line to the automation:
I checked, and that trace only shows one detected firing of the tiger. Also, the reason I looked into it is cause one of the locks was not unlocking and the garage door was not opening.
My understanding is that there won’t be a trace of the second double-press because it’s automatically rejected (due to the automation’s mode ). That’s why there’s just an error message and nothing more.
Anyway, it’s your choice if you want to try my suggestion or not. Good luck.
Find the Back Door automation in the displayed list
Look in the Attributes column and find the automation’s current attribute.
The attribute’s value should be 0. Any other value means the automation was triggered and is currently busy executing its actions.
Your automation’s two actions shouldn’t take more than a second or two to complete so it will normally be nearly impossible to see a value greater than 0. However, if you do see the value is constantly 1 then it implies something has gone seriously wrong with one of the two actions and the automation is waiting for it to finish.
If this happens, the next time you double-press the button, even if it is several minutes or hours later, the automation will reject it.
Beyond that scenario, I am unaware of another one that would cause Home Assistant to report that error message.
Currently it shows it’s 0, however I’ll keep an eye on things.
After the Dec update, I’ve had a few automations mess up on me and I’m starting to thing it may be something to do with modes so this will help trouble shoot them too.