I have an ISY 99i that is working great, however it seems to gain time. It is about 1 minute fast. I have it synchronizing with NTP server every 24 hours.

 

When I choose "sync now" the time is corrected.

 

Any thoughts?

Hi Moshe,

 

That is very odd unless ISY is not actually synchronizing with NTP every 24 hours. So, is ISY 1 minute fast every day or every month or every time you check it?

 

With kind regards,

Michel

 

I have an ISY 99i that is working great, however it seems to gain time. It is about 1 minute fast. I have it synchronizing with NTP server every 24 hours.

 

When I choose "sync now" the time is corrected.

 

Any thoughts?

It seems to gain time every couple of weeks. When I resync the problem is corrected.

Hi Moshe,

 

Can you check your logs to see if you have any -6000x errors? It seems as if ISY is not synching with your NTP properly.

 

With kind regards,

Michel

 

It seems to gain time every couple of weeks. When I resync the problem is corrected.

Hi Moshe,

 

That is very odd unless ISY is not actually synchronizing with NTP every 24 hours. So, is ISY 1 minute fast every day or every month or every time you check it?

 

I am seeing the same problem. Version is 2.7.0

 

I have the NTP server Enabled and set to sync every hour. I run my own local NTP server

so I know it is not a connection problem. Upon a ISY device reboot, I see the initial

time sync....

 

(.130 is the ISY device and .50 is the server running NTP)

 

9:47:17.89708 172.22.22.130 -> 172.22.22.50 NTP client (Wed Feb 6 22:28:16 2036)

9:47:17.89761 172.22.22.50 -> 172.22.22.130 NTP server (Sun Apr 12 09:47:17 2009)

 

Then nothing, ever. If I do a manual "Synchronize now", I get another valid time

sync....

 

16:22:46.36672 172.22.22.130 -> 172.22.22.50 NTP client (Wed Feb 6 22:28:16 2036)

16:22:46.36844 172.22.22.50 -> 172.22.22.130 NTP server (Mon Apr 13 16:22:46 2009)

 

Also note the initial date/time from the ISY device

trosmus, thanks SO very much. Your invaluable log provided me with enough to actually find a very rare bug the finding of which would've been impossible otherwise.

 

Moshe, thanks for finding this bug.

 

It's all fixed now and included in 2.7.3 (hopefully to be dropped any day now).

 

With kind regards,

Michel

 

Hi Moshe,

 

That is very odd unless ISY is not actually synchronizing with NTP every 24 hours. So, is ISY 1 minute fast every day or every month or every time you check it?

 

I am seeing the same problem. Version is 2.7.0

 

I have the NTP server Enabled and set to sync every hour. I run my own local NTP server

so I know it is not a connection problem. Upon a ISY device reboot, I see the initial

time sync....

 

(.130 is the ISY device and .50 is the server running NTP)

 

9:47:17.89708 172.22.22.130 -> 172.22.22.50 NTP client (Wed Feb 6 22:28:16 2036)

9:47:17.89761 172.22.22.50 -> 172.22.22.130 NTP server (Sun Apr 12 09:47:17 2009)

 

Then nothing, ever. If I do a manual "Synchronize now", I get another valid time

sync....

 

16:22:46.36672 172.22.22.130 -> 172.22.22.50 NTP client (Wed Feb 6 22:28:16 2036)

16:22:46.36844 172.22.22.50 -> 172.22.22.130 NTP server (Mon Apr 13 16:22:46 2009)

 

Also note the initial date/time from the ISY device

I am also seeing this behavior (time gains about 2 minutes per week); manual NTP time sync corrects. I look forward to seeing the fix in 2.7.3.

I have had this problem also, without resolution, having tried all the suggested remedies. Hopefully, this will fix mine, as well.

Michel -

 

Thanks for the feed back. I will update to new version when available.

 

Moshe

Same issue here. When will the fix be released?

AutomationNut,

 

Aha, now I understand the context of your previous post. Yes, 2.7.4 + all fix this issue.

 

May I humbly recommend waiting for 2.7.6 which is filled with new features?

 

With kind regards,

Michel

 

Same issue here. When will the fix be released?

I will wait for 2.7.6

 

thanks