Time is wrong.

Also, if the time doesn’t change, that means it’s not getting NTP sync signal. Check if you have a valid Internet connection, and make sure the NTP port (123) is not blocked by your router.

Did you look at my second reply above? I still suspect that maybe your controller is not getting NTP sync signal.

One easy test to try is to take out the RTC battery (the CR1220 coin battery), wait for a minute, and then put the battery back and restart the controller. If it doesn’t get your current time, it means the controller is not getting NTP signal, that’s why it cannot update its time.

I suggest that you figure out the NTP problem because otherwise the controller time will start to drift. Are you connecting the controller to your router directly through wired connection, or are you using a WiFi adapter?

Unfortunately the firmware does not leave a way to manually set the clock (I didn’t think there would be a situation where you have Internet connection but no NTP sync). There are several ways you can set the clock (for example, plug it into another network which permits NTP sync, or upload an Arduino program that manually sets the clock. But in any case, I don’t recommend using the system without NTP, because the time will drift and after several months you may have to do the same trick again.

I’m having similar issues but I think I may have tracked it down to a NTP refresh interval which may be lengthy interval. In other words, your clock doesn’t refresh every few seconds and likely updates every few minutes/hours since it’s not something that needs to be regularly adjusted once it’s set. When I change my time zone within the options the device time displays the proper offset (-7 in my case for Mountain Time US) but the previous time is still displayed. I left it and came back to it the next morning and the proper time was displayed (well, not proper since I had left it at -5 30 as I was experimenting) so my guess is that when you adjust the offset to NTP (only way to adjust the time) you have to wait until the device polls the NTP for time, applies your offset and adjusts local time. I have nothing to confirm this yet as I just set it to the proper (for me) offset and am waiting to see if my theory proves accurate. So, you may try setting your proper offset and giving it some time. I agree this isn’t the most attractive way to address this but if this is indeed the case it should set itself properly on the next refresh/poll. Perhaps Ray can chime in on what this interval is set at and if my guess is accurate. Adding an option to manually set the time or even using PC time (I have several items set to poll the PC for current time which I prefer since you have one less port open to the public, one less device polling an outside source that has potential to become a way into the network) would be a good way to give more flexibility for end users or possibly have it poll immediately after making a change to reflect the proper time instantly would resolve such issues.

Just thinking out loud I guess and hoping someone with more knowledge on inner workings can chime in since I just received mine.

I’m having similar issues. I’ve set it to GMT-8 and the time is still wrong. I’ve rebooted and power-cycled both open sprinkler and my gateway router. I’ve also verified that computers on the same network and see an NTP server. Not sure what to try next.

Thanks, Ray. I just found the issue…bad gateway config. I’m not sure why I did not think of that. It works now.

It looks like there is no daylight saving time adjustment…is that true? Not a big problem…just want to know.

G