This command sets the automatic start of the cleaning process. It uses a cron-like notation of the cleaning schedule. Interestingly, once executed commands are not set to inactive, would these be active next year again? Likewise, seems any command can be scheduled
| Key | Value | Comment |
|---|---|---|
| method | get_timer |
|
| id | [Integer] | is returned in the response used to link the send message to the response. |
{'id': 1, 'method': 'get_timer'}
| Key | Example | Description |
|---|---|---|
| 1498595924541 | Entry time of this schedule (Unix time) | |
| on | Is this schedule active | |
| ['38 9 28 6 *', ['start_clean', '']]] | Timing in cron-like notation. The time appears to be China timezone based (e.g. in Europe add + 6 hours to the CET time) |
┌───────────── minute (0 - 59)
│ ┌───────────── hour (0 - 23)
│ │ ┌───────────── day of month (1 - 31)
│ │ │ ┌───────────── month (1 - 12)
│ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday;
│ │ │ │ │ 7 is also Sunday)
│ │ │ │ │
│ │ │ │ │
* * * * * command to execute + parameter
['1 5 * * 0,6', ['start_clean', '']]]
{'result': [
['1498595924541', 'on', ['38 10 * * 0,6', ['start_clean', '']]],
['1498595904821', 'on', ['38 5 * * 1,2,3,4,5', ['start_clean', '']]],
['1498595882094', 'on', ['38 9 28 6 *', ['start_clean', '']]]
],
'id': 1}
| Key | Value | Comment |
|---|---|---|
| method | set_timer |
|
| params | [[Time in miliseconds , [schedule, [command,parameter]]]] |
See above for the schedule settings . Time in MS is used as sort of record id |
| id | [Integer] | is returned in the response used to link the send message to the response. |
{'id': 1, 'method': 'set_timer', 'params': [["1498595904821",["30 12 * * 1,2,3,4,5",["start_clean",""]]]] }
| Key | Value | Comment |
|---|---|---|
| method | upd_timer |
|
| params | [ "timer ID", "on/off"] |
|
| id | [Integer] | is returned in the response used to link the send message to the response. |
{'id': 1, 'method': 'upd_timer', 'params': ["1498595904821","off"] }
{ "result": 0, "id": 1 }