Scheduler

[kris969]

I am using the scheduler on a Sonoff DUAL to turn on an equipment from hours (2AM to 6AM).
I have set 4 schedules, the first two ones are enable the last two are actually disabled, I will use it later.
Unfortunately The schedule seems not to start at 2AM, I was awake at this later time and had a check it. I turn it on manually.
I will procced some tests around this in the next days, to try to reproduce this issue, if so I will come back to you.

Working on this, I had the following Idea.
I think it could be interesting, to replace setting of independent schedule with the setting of sequence, each sequence should be a start time and an ending time. During the sequence the relay could be ON or OFF, depending of needs. With such approach, it could be possible to periodically check if the GPIO is in the right state regarding to an available sequence, and to activate it again in case of nonsense.

What do you think about this?

Regards

[xoseperez]

Sure that's an idea and it would fit into a more versatile schedule. One that could take into account different inputs like relay status, time of day (of course), sensor values,...

[kris969]

I could propose you to participate in writing code.
it could be interesting to start in writing a little document to specify what we expect to do, in reality it seems we have started in that way.

I'm not sure to be efficient on the GUI, but I could work on the scheduler itself.

Do you agree?

[kris969]

Hi,
A new discussion...
Of course it is a question of point of view.

Don't you think it could be nonsense to use scheduler when using MQTT on Epurna?
I'm thinking about this because I started for one of my devices with Epurna Scheduler, then afet having deployed a new Mosquitto broker somewhere in the Internet, I switched using MQTT on it, and...

I forgot to clear the local Epurna Scheluder. Of course the scheduler and MQTT actions were working together! It takes me few minutes to understand I got a conflicting settings.

What do you think about this?

[xoseperez]

The scheduler works in parallel to any other means of switching the relays, that includes MQTT, the REST API or the physical button. The initial goal was to provide different options for the user (some will do MQTT, other prefer to have a standalone device (hence using the schedule).

[mcspr]

fwiw, current version does scan all declared schedules for the specified action target-id and launches the last one
but, only when there's a schedule restore setting on

espurna/code/espurna/scheduler.cpp

Line 65 in e22f67e

return 1 == SCHEDULER_RESTORE_LAST_SCHEDULE;

e22f67e#diff-e8b9a5d04af16462e032b4ceb5900c29571415364a39b566b9ca03ac55749fcf

[mcspr]

Closing, ref. #2417