Hi,
I have a sunset response that triggeres z-wave lights, since the change uk DST at the weekend the response is still triggering at the time set in the sunset/sunrise schedual. I have set to a local city near me and ticked the box to say use DST.
Any thoughts?
Best Regards
Lee
If the sunset Response is programmed to trigger at say 18:15 before the daylight saving time change, then after the change the Sunrise and Sunset Times are unchanged. ie the Sunset Time is still 18:15
However the time in Comfort has been adjusted 1 hour forward so the sunset Response will happen 1 hour later when compared to GMT
I have the same issue also in the UK. I also have the DST box ticked.
All my time programmes such as auto arm to night mode etc. are still running at GMT not UK time (DST in Summer).
I also have tried resetting the time from PC using Comfigurator. The time shown on the keypad is still also GMT not UK DST.
I am still a newbie so presumably have something wrong.
Henley
Sorry, this still don\'t make sense ?:-)
If you put the clock forward on day one by one hour then you trigger the response one hour earlier by my calculations.
Day 1 Day 2
GMT 6:15 RT 5:15
DST 7:15 6:15 RT
RT response Trigger Time
[user=4179]HenleyBranch[/user] wrote: Quote:I have the same issue also in the UK. I also have the DST box ticked.
All my time programmes such as auto arm to night mode etc. are still running at GMT not UK time (DST in Summer).
I also have tried resetting the time from PC using Comfigurator. The time shown on the keypad is still also GMT not UK DST.
I am still a newbie so presumably have something wrong.
Henley
The time on Comfort should be moved forward by 1 hour on Sunday Morning so your time programs should still run on the same time according to the Comfort Time
In \"real\" time, the time programs should occur 1 hour later
If you set the time again from the PC then the keypad should show the same time as your PC
See attached screen grab.
Time on PC has automatically adjusted for DST 14:19, but the time written to Comfort in the I/O Monitor is 13:19 (and 35 seconds), I am presuming that the time the PC writes to Comfort is without any DST adjustment, and Comfort should have applied the adjustment on Sunday when DST came in in the UK (as per window open in screenshot it was 25th so should have happened then). Except in my case it hasn\'t and Comfort is currently running without adjustment for DST.
Any idea what am I doing wrong?
Henley
I dont know why the non-adjusted time was sent to Comfort. I would have expected that the adjusted time would be sent. we wil check howo the software sends it
Comfort does not do any adjustment on the time sent to it as it expects the time to be adjusted. The only time it does a time adjustment is at 2 AM on the day that the chnge takes place, in the recent case on Sundayu Morning 25th March
[user=4179]HenleyBranch[/user] wrote:Quote:Time on PC has automatically adjusted for DST 14:19, but the time written to Comfort in the I/O Monitor is 13:19 (and 35 seconds), I am presuming that the time the PC writes to Comfort is without any DST adjustment, and Comfort should have applied the adjustment on Sunday when DST came in in the UK (as per window open in screenshot it was 25th so should have happened then). Except in my case it hasn\'t and Comfort is currently running without adjustment for DST.
Any idea what am I doing wrong?
Henley
Comfigurator gets the local time from the PC which should be adjusted for daylight saving to send in the DT command
We have confirmed that other PCs are not having this problem
Are you getting the time from another server which may be on unadjusted time?