Sorry I was away for a long weekend. Grant thank you so much for your support on this one and stating a case for the Timer Widget, you managed to articulate my frustration at the lack of it a lot better than I could. I spent quite a bit of time on the weekend wondering how to convince @Dmitriy when I got back 
The Timer Input in my opinion is one of the pivotal Blynk 1.0 widgets, and once you master the code (which is not that difficult or hard) it is super easy to implement. Besides my Geyser Timer project (Time Scheduler and Power Energy Monitor) I use the Timer function extensively in an irrigation project where I have several timers running schedules. I also use it to pre-program a RTC with the schedules as in some cases I do not have WiFi connectivity and use my phone as a hotspot to update the changes.
The implementation of the Timer Widget in 1.0 is elegant and neat and I find it difficult to understand why the change! I sincerely hope that we see it back as a widget rather than in its current form of implementation. It looks like the topic is taking traction and look forward to the idea of an Automation widget from a device viewpoint.
Les