Jump to content

daylight saving not working


drw

Recommended Posts

I have found that daylight saving adjustment did not occur overnight.

 

I also find that I cannot adjust the time manually. I have tried to synchronize with my computer. Or manually adjust time. The result is the same: "request failed".

 

I had the ISY-26 set to sync with the NTP server. I tried turning that off and it did not help my manual adjustment.

 

I am running the version 2.7 (recent) release. I am using a Mac with Safari 4 (beta) browser. Other things seem to operate normally.

 

On further investigation,

My programs seem to be happening at the correct time (sunset-30 for example). But the display of current time and the sunset time are one hour off. So this seems to be a display problem.

 

I have also opened the Admin console with Firefox and the time of day displayed is standard time (incorrect).

Link to comment

drw, This sounds very much like a Java cache issue. The display is using a new display with old data. Please see this page

 

Clearing_Your_Java_Cache.

 

I have also noticed some persistent events even when performing those actions. Often it's as simple as closing the application and reopening.

 

I am really believing it is a combo browser-java-PC-network, etc. has everyone watching everyone and it takes some time before the trust goes through. A good thing. Minor updates on the ISY appear to pass quickly here.

 

Rand

Link to comment

sub-routine,

I cleared the Java cache as described in the instructions. It did not change the display of time (standard time shown). I repeated the cache clear procedure and the time display is still wrong. As before, when I attempt to adjust the time manually, I get the "request failed" response.

 

The saving grace is that the programs seem to be executing at the proper time regardless of the display.

Link to comment
sub-routine,

I cleared the Java cache as described in the instructions. It did not change the display of time (standard time shown). I repeated the cache clear procedure and the time display is still wrong. As before, when I attempt to adjust the time manually, I get the "request failed" response.

 

The saving grace is that the programs seem to be executing at the proper time regardless of the display.

 

Okay. Thank you, you have given us more info. This is a big help.

 

Thank you,

Rand

Link to comment
Just a note of question!

 

I just upgraded to a 99 (from a 26), at the same time I installed 2.7. Last night as well passed through DST, I noted all my "Last Run", Last Finish", and "Next Scheduled" boxes became empty? Also I have one program that "Runs at Start-up". The program no longer showed that it should run at start-up. I (remotely) re-set the run at startup. I'm concerned how this happened and wheter there are any other un-seen things lurking!

 

aLf

 

Michel:

 

Posted this earlier on another thread and never got a response. I've since corrected the time issues by "forcing" them through toggling Home & Away. None are a big deal, but wondered if there is a simple answer to why it happened. The Run at Startup is the most troubling. To fix that I physically had to go in (remotely) and re-add the run at startup call to that particular program. I assume that at DST the time moved and therefore the last runs and next runs couldn't keep up? Just wanted you to have a picture of what I saw.

 

aLf

Link to comment

Hi aLf,

 

Sorry I must of missed it.

 

When the time changes (either through DST or otherwise), all the last run time, next run time, etc. will be reset till the next time that they are calculated.

 

As far as Run at Start Up, this is an in-memory/display bug but it has ZERO impact on the operation of ISY: in case your ISY reboots, all those programs that were supposed to run at start up would still run at start up and the flag reappears.

 

With kind regards,

Michel

 

Just a note of question!

 

I just upgraded to a 99 (from a 26), at the same time I installed 2.7. Last night as well passed through DST, I noted all my "Last Run", Last Finish", and "Next Scheduled" boxes became empty? Also I have one program that "Runs at Start-up". The program no longer showed that it should run at start-up. I (remotely) re-set the run at startup. I'm concerned how this happened and wheter there are any other un-seen things lurking!

 

aLf

 

Michel:

 

Posted this earlier on another thread and never got a response. I've since corrected the time issues by "forcing" them through toggling Home & Away. None are a big deal, but wondered if there is a simple answer to why it happened. The Run at Startup is the most troubling. To fix that I physically had to go in (remotely) and re-add the run at startup call to that particular program. I assume that at DST the time moved and therefore the last runs and next runs couldn't keep up? Just wanted you to have a picture of what I saw.

 

aLf

Link to comment
Hello drw,

 

Would you be kind enough to let me know which URL do you use? Do you use: http://www.unviersal-devices.com/99i OR do you access your ISY's URL directly?

 

With kind regards,

Michel

 

I am using

http://www.universal-devices.com/99i/

 

Further observation,

As noted before, programs set to run at sunset-x seem to run at the correct time. But I have noticed that programs set to run at specific times (e.g. 10 PM) are running an hour late (11 PM).

Link to comment

Michel:

 

Thanks for your insight again! I kinda figured that the run times were just messed up due to the change. As far as your comment re: "in memory display bug". Do you mean that this is a bug being worked on, just discovered, or don't let it bother you Tim? I did manually go in and re-checked the box and it now show "run at start up again".

 

Thanks,

 

aLf

Link to comment

Hi aLf,

 

Do not let it bother you ... if it does, simply reboot ISY and it will show you the flags again.

 

It's a bug that's being worked on but with a very low priority since it has zero impact on the correct operation of ISY.

 

With kind regards,

Michel

 

Michel:

 

Thanks for your insight again! I kinda figured that the run times were just messed up due to the change. As far as your comment re: "in memory display bug". Do you mean that this is a bug being worked on, just discovered, or don't let it bother you Tim? I did manually go in and re-checked the box and it now show "run at start up again".

 

Thanks,

 

aLf

Link to comment

further information,

During some experimentation, I ended up rebooting the ISY. After the reboot, the displayed time was correct (daylight) time. None of my programs have run to determine if all is on schedule but the display is now correct.

 

The "synchronize with computer time" and "manually set time" appear to also work after the reboot.

Link to comment

DEGoodrich,

 

Do you have the DST checkbox checked?

 

What were the symptoms with your IES touchscreen? And, are you saying that NONE of your programs worked?

 

With kind regards,

Michel

 

I had a similar problem.

After the DST change, my clock did not update.

Also all of my programs ceased to function.

Lat run and next run were all blank.

My IES TS ceased to function also.

I reset the ISY-99 and the IES. All is fine now.

I am running 2.7.1

 

:|

Link to comment

I am just getting back from a week away, and noticed that my DST did not automatically adjust. For the record, my clock also has never synched with the pool.ntp.org, either. I cleared the java cache, and rebooted (unplugged, replugged) ISY. Still time is an hour off.

Link to comment

Hello oberkc,

 

Please make sure you have Daylight Saving box checked in the configuration page without which ISY does not automatically adjust for DST.

 

As far as not synching with pool.ntp.org, please make sure ISY has access to the Internet.

 

With kind regards,

Michel

 

I am just getting back from a week away, and noticed that my DST did not automatically adjust. For the record, my clock also has never synched with the pool.ntp.org, either. I cleared the java cache, and rebooted (unplugged, replugged) ISY. Still time is an hour off.
Link to comment

The box was (and is currently) checked, and the access to the internet is enabled, and confirmed by my ability to access it remotely. I posted a similar comment on another thread (more related to the NTP thing) in which I also stated that the DST seemed to be fixed when I found a better NTP address. Go figure.

Link to comment

Do that you know all the details that I can think would be relevant....

 

I have had "daylight savings" button checked for as long as I have been using the device. I can't remember when I purchased it, but it is possible that this is the first daylight savings transition I have experienced with the ISY.

 

I have always had the automatic time synch with internet checked, but it has never worked in my experience. I used the default site. As you suggested earlier, though, this may have been due to the fact that I have not always had internet access enabled. Internet access on my machine was activated a couple weeks ago, well ahead of daylight savings transition. This did not fix my synching problem. I was able to access my ISY from other locations using my laptop, which gave me some level of confidence that internet access was working.

 

Daylight savings transition time came and went, and the ISY did not adjust time. It appeared, however, to recognize new sunrise and sunset times based on the one-hour advance in time.

 

I unplugged the cat-5 cable/power from the back of the ISY in the hopes of "rebooting" the ISY. No synch. No DST.

 

I noticed recently that there was a red exclamation point at the configuration tab where the daylight savings box is checked. I tried a couple of the other sites suggested on another threat for time and found one that appeared to work. It believe it was a numeral-based IP address. Unfortunately, I cannot confirm that because the ISY has now defaulted back to the pool.ntp.org site. At this point, there is no red exclamation point and the clock appears accurate.

Link to comment
Do that you know all the details that I can think would be relevant....

 

We appreciate your time. Thank you.

 

I have had "daylight savings" button checked for as long as I have been using the device. I can't remember when I purchased it, but it is possible that this is the first daylight savings transition I have experienced with the ISY.

 

We thought we had fixed this last year. Are you using a Custom Location? This is wrong and must be fixed.

 

I have always had the automatic time synch with internet checked, but it has never worked in my experience. I used the default site. As you suggested earlier, though, this may have been due to the fact that I have not always had internet access enabled. Internet access on my machine was activated a couple weeks ago, well ahead of daylight savings transition. This did not fix my synching problem. I was able to access my ISY from other locations using my laptop, which gave me some level of confidence that internet access was working.

 

You do not need Internet Access Enabled for the ISY to read the NTP server.

 

Daylight savings transition time came and went, and the ISY did not adjust time. It appeared, however, to recognize new sunrise and sunset times based on the one-hour advance in time.

 

This could be a GUI error as the programs are running as scheduled.

 

I unplugged the cat-5 cable/power from the back of the ISY in the hopes of "rebooting" the ISY. No synch. No DST.

 

There is a Reboot button on the Config/System panel (v2.7) so you no longer have to unplug unless you need to reset the PLM. Please try this as it is a softer reset.

 

I noticed recently that there was a red exclamation point at the configuration tab where the daylight savings box is checked. I tried a couple of the other sites suggested on another threat for time and found one that appeared to work. It believe it was a numeral-based IP address. Unfortunately, I cannot confirm that because the ISY has now defaulted back to the pool.ntp.org site. At this point, there is no red exclamation point and the clock appears accurate.

 

Sometimes NTP servers become overloaded and do not respond, thus the exclamation point. Google NTP for a server near you. If you didn't Save the IP address the ISY will forgot it.

 

Rand

Link to comment

Also, I do not percieve this as a GUI problem. Yes, the programs ran as scheduled. Yes, the ISY updated the sunrise/sunset times to reflect the DST condition. Unforunately, the ISY clock was an hour behind, and the programs executed one hour late compare to real time, including those based on sunrise and sunset. This does not strike me as a GUI problem. Everything ran per the ISY settings.

Link to comment
Also, I do not percieve this as a GUI problem. Yes, the programs ran as scheduled. Yes, the ISY updated the sunrise/sunset times to reflect the DST condition. Unforunately, the ISY clock was an hour behind, and the programs executed one hour late compare to real time, including those based on sunrise and sunset. This does not strike me as a GUI problem. Everything ran per the ISY settings.

 

Okay, thank you.

 

Rand

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...