After running into this issue, I added a bugfix for timer.finish here: https://github.com/home-assistant/core/pull/48549
I’m working around it for now by avoiding timer.finish (instead using timer.start with a 1s duration)
That sounds promising. I rarely call timer.finish anyway, and think that I have still seen it stop, after just calling frequent timer.starts… I think there may be a similar issue with the start code occasionally not cancelling any previous callbacks.
As my cancel/finish is done in a script for convenience I will certainly try using your 1s start as a workaround…
Thanks