It appears something is screwy with the sunrise/sunset and DST change thats just happened.
In Week 44, my config says Sunset is 4:41pm. It\'s now 5.28pm and the responses havnt kicked in as usual. Im asuming they may work at 5.41 ? The KP04 says the time is 5.28pm - as do all the CBUS DLTs, so I handled the time change ok.
Im assuming this is going to be the same every day until we find what the cause is.

Yep - it did it an hour later - ie wrong - even tho the comfort clock is correct !
 
Bug.

Same last night - was an hour out.

I check for the NightMode flag.

BUMP ! 
This is a big failure in the new sunrise/sunset code with DST. So, it causes an issue every single day.
Is this being investigated ? What workaround can we put in place now - today ?

Due to the problem on the forum hosting, we have not been receiving the forum emails for the last week. We will look into this problem

First some background as to the working of this
The sunrise and sunset times in the table are applicable without  Daylight saving changes
If you see the chart for London, sunset time

Week 40 = 17:38
Week 41 = 17:23
Week 42 = 17:07
Week 43 = 16:53
Week 44 = 16:39
Week 45 = 16:27
Week 46 = 16:16
etc

You will see that these times are applicable to non-daylight adjusted time, as there is no sudden jump of 1 hour in week 44 when the change back takes place

When daylight saving is in effect, the sunrise and sunset times will be adjusted so that they happen 1 hour later in accordance to the time change

eg
Week 40 = 18:38
Week 41 = 18:23
Week 42 = 18:07
Week 43 = 17:53


When daylight saving is not in effect, then the sunrise and sunset times should be as they are in the table

We have checked that the behaviour within and without daylight saving is as expected, described above

In your case perhaps the city you selected in the config has noto been actually downloaded into Comfort as you need to press the SET TIMES button to load the correct values. Can you upload the Sunrise/Sunset times and check that it corresponds to what you expected?

We are in Week 44.
 
My config says Sunset should be 16:41.
 
In fact, it doesnt kick in until 17:41. Hence my sugestion there is a bug. it was fine until Sunday when the DST changed. Ive not made any changes to the config since 26th oct.

Sunset was fine on Saturday evening. Sunday evening it was an hour out. The clock on the KP04 and CBUS showed the correct DST adjusted time.

As a workaround, ive set the sunset time for week 44 to 15:41. It now kicks in at 16:41 until you can find the problem.

Thats strange. I have done the same thing, set sunset time for week 44 to 15:41, and the sunset response workes at exactly that time
I also verified that the sunrise response worked at exactly the time specified
I set the time to 15:40 and let the time change to 15:41

You are on 5.113?

Can anyone else confirm what they experience?

Im on 5.113
Worked fine Sat. Went wrong Sun after the time change (which was automatic)

We cannot find this happening here, so I have asked another user to check his system
Anyone else able to test this?


The sunrise and sunset times would be out by 1 hour if Comfort thinks it is now in daylight saving. It works it out by comparing the date with the start and end of Daylight saving. Are the downloaded  dates for start and end of dayling savings correct?