Closed gregmac closed 1 year ago
Hi Greg,
You're right, the documentation could be a little bit better about enabling/disabling timers. The problem is that I changed the field from enabled to enable. My motivation for this change was that 'enable' is a command instead of a 'state'.
The message should be like this:
{
"id": "timer1",
"enable":"false"
}
or to enable again in the case of a configurable timer:
{
"id": "timer1",
"enable":"true"
}
I updated the readme and the enable field will be validated now.
Docs state:
However:
enabled
seems to be ignored. For example, the following timer triggers:Actual way to cancel a timer seems to be to omit
topic
(or set tonull
), or more intuitively just send an empty object with justid
like:I'm not sure if this is a code or just documentation issue.