Has this issue been fixed or is there someway to manually try and sync the time because I am having an issue with my startup procedure rule which contains delayed actions. For some of the rule the time is one thing, and for the other part it is something else. As a result when they delayed action is first triggered, in the incorrect old time, it has a delay for 4 minutes for example. Then the hub time gets updated and it goes beyond those 4 minutes, causing the delayed action to never trigger.
Any ideas on how to fix this?
Alternatively, is there any way to have a wait condition for an update on the time?
Update: I figured out a workaround using the community app shown below. It has the same issue as the delay in that there is an out-of-date and in-date time, but I am guessing it is an greater than or equal to comparison versus just an equal to comparison, which in my case is perfect since the delay is controlling a network device, and an update in time would mean that the internet is up and running.
