I have noticed when writing programs and testing them that the time shown clicking away in the corner of the gui is different than ISY's internal clock.

 

For example, this morning, I was testing a program. It was set to trigger at 8:49. By the gui clock 8:49 came and went, then at 8:50:30 (by the gui clock) the program ran. The "last run time" on the gui showed 8:49:00 after that.

Hello apostolakisl,

 

The accuracy of the clock on the Admin Console is within the past 5 minutes. So, Admin Console gets the time from ISY, does it's one incrementing, and then synchs after 5 minutes again (to reduce the load on ISY).

 

With kind regards,

Michel

Michel,

 

I am not sure I understand you. What do you mean by "does it's one incrementing"?

 

Are you saying that the gui runs its own clock and then every 5 minutes synchs with the ISY?

 

Does it seem right to you that the gui would have been almost 2 minutes different?

 

Lou

Hi,

 

Yes, that's what I mean. 2 minutes is unlikely but I am not sure whether or not you were looking at Program Summary while testing ... is it possible that Admin Console lost connection to ISY?

 

With kind regards,

Michel

I was following the program summary page looking for run times and true/false changes. I was looking at the clock that was running in the upper left corner of the gui. The connection is good I assume, since the program summary did change true/false and did update the run times as I watched.

How long was the Admin Console on?

 

With kind regards,

Michel

Can't say. I don't remember if it was already up or if I just opened it up right before I started working. It could have been up for more than 24 hours. I suppose you are suspecting that it was up for a long time and the clocks were running at different speeds, but how does that fit into the "sync every 5 minutes" concept.

Hi apostolakisl,

 

It is very important to know how long the AC was left on. If 24 hours and they were not in synch, then I suspect a bug.

 

With kind regards,

Michel