Unexpected behaviour in Timer add-on?

[chas_iot (Charles JC)]

When a timer is started and expires, the timerHandle is left in place. It can be cleared by the Reset action.

What this means to a novice user of the gateway / Timer is that once a timer is used in a rule, it can’t be reused until the Add-ons are reloaded or the gateway is restarted.

I’m not sure whether it is better to change the behaviour to clear the timerHandle or to change the documentation to make it more obvious to a noob like me.

[chas_iot (Charles JC)]

There’s a third possibility - to add a Boolean configuration property to auto-reset on time out. I’ll see if I can work out how to do this and submit a PR on the Timer Add-on

[mstegeman]

The timer adapter is a third party add-on, so it would be easiest to open an issue/PR on the repo. The author is very responsive.

[lacojim (Lexridge)]

The way it works is a bit of a kludge. This is how I handle the reset/start action. Doesn’t seem very logical, but it does work.