I understand that. The intent is for the device to know start and stop times. That is meant to trigger an activity. Why not send just 1 and 0 for start and stop like how timer does? I’m unable to visualise a use case where 1 and 0 will not work for time start and stop input.
It will be worthwhile to look at how UIs like eWelink do this. They have a button for manual on/off. To this button, time schedule object(s) can be added with action (on/off). So, I can attach 3 schedules for a day, if I want to. This will be involved in Blynk. We will use 3 different Vpins and if we need to add 4 or 5, then more time objects will be needed. I wonder how this would work in a compiled app binary? Obviously, the user will not be able to add as many schedules as he wants.
