I struggled long with the same problem Fradera reported (all widget easily reset to values stored on the device by virtualWrite+syncWirtual, except TimeInput), and went stripping down my application to pinpoint the issue, till I discovered that TimeInput is only reset to the values coming from device if I move the app to edit mode and run it again. In other words, it looks that TimeInput is receiving inputs but not adopting them till restarted.
I know I lack understanding of how the relationship between my device, my app and the server runs. To my eyes the server is “transparent”, in the sense that I am concerned by the app-to-hardware relationship only - a hop only, not two - and this is most probably the source of this behavour. Nevertheless, if ever possible I’d like a change in the ways TimeInput works now, by ensuring that its data are changed in push-mode like those of all other widgets. Otherwise, there might be the case where my hardware resets to default start/stop time, I am happy of the start/stop time I see on my screen, and keep going out of sync.
Btw: all the above with iOS 10.1.1 on iPhone; Blynk 0.6.1; Wemos D1 and WiFi connection; and any code including the example sketch referred.