Timer
Does something on a repeat, for as long as the dashboard is open. Use it to poll a device that doesn’t report on its own, or to send a command at a fixed interval.
Settings
| Field | What it does |
|---|---|
| Action | What to do each time — Ask for status or Send command |
| Command to send | The command, when the action is Send command |
| Timer label | Wording shown on the element |
| Repeat Every (ms) | Interval in milliseconds. 5000 is every five seconds |
| Color | The element colour |
| Admin only | Hide it from everyone who isn’t an admin of the device — see Sharing a device |
The two actions
Ask for status asks the device to report its values again. Everything else on the dashboard refreshes as a result. This is the one to use when a device only reports when asked, and you want a dashboard that keeps itself current.
Send command sends the text in Command to send, exactly as a Button would, on every tick.
It only runs while you’re watching
A timer is part of the dashboard, not the device. It ticks while the dashboard is open in your browser and stops when you close it.
For something that must happen whether or not anyone is looking — a nightly reset, a reading every minute into history — put the schedule in your firmware instead.
Choosing an interval
Milliseconds, so 1000 is one second. Short intervals mean more traffic and more work for
the device; a few seconds is usually plenty for a dashboard you’re watching.
Take care with Send command on a short interval — it will send that command over and over for as long as the page is open, which is rarely what you want for anything that moves a motor or writes to flash.