| Posted: Thursday Mar 31st, 2016 04:59 am |
|
1st Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
I have been having problems with Comfort failing to apply the hour DST offset since the clocks went forward on the weekend.
I checked the SNTP settings in CSM and all seems fine. The correct time is shown and it is set to send the time to Comfort every twenty minutes. It was necessary to use the 'Submit' button before Comfort displayed the correct time. Unfortunately, it forgets again at the beginning of each day.'The event log clearly shows what is happening. Up until midnight there are regular 'Date/Time Change UCM 1' entries every 20 minutes with the final one logged at 23:52. The first one after midnight reveals the issue - it is logged at 23:12 so Comfort has clearly stopped applying the DST offset at this point. The time on the keypad confirms this. Curiously, further Date/Time changes also cease thereafter. To correct the time, it is necessary to manually submit it again via CSM, after which the regularly time updates recommence until just after midnight.
Any ideas what is going on?
I never had this problem last year but I have updated the firmware since which could account for the current problems.
The Controller firmware is 7.093 and the UCM firmware is 7.076 and Eth3GE-v2.20
Craig
|
| Posted: Thursday Mar 31st, 2016 05:35 am |
|
2nd Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5500 |
| Status: |
Offline
|
back to top
|
The topic at http://www.comfortforums.com/view_topic.php?id=4026&forum_id=113 explains how the ETH03 works with Daylight savings
ETH03 sends the time without Daylight saving adjustments to Comfort. Comfort will make the adjustment for DST based on the Schedule> sunrise/sunset times. So make sure that you have the correct settings for your city/location in Sunrise/Sunset
You have the latest firmware for everything so it should work in this wayLast edited on Thursday Mar 31st, 2016 05:37 am by slychiu
|
| Posted: Thursday Mar 31st, 2016 12:02 pm |
|
3rd Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
Thank you for your reply. I am aware of how the system is meant to work and my location is correctly programmed in Sunrise/Sunset.
The event log shows that Comfort is correctly applying the DST offset throughout the day until it crosses midnight but then reverts back upon the next Date/Time Change from the UCM. I studied this closely last night before reporting the issue and Comfort's time was correct before and after midnight until that Date/Time Change was received.
As I said before, the system was working perfectly last year before, during and after the DST period and the only thing that's changed is firmware.Last edited on Thursday Mar 31st, 2016 12:04 pm by Craig Robins
|
| Posted: Thursday Mar 31st, 2016 01:03 pm |
|
4th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5500 |
| Status: |
Offline
|
back to top
|
can you send your cclx file to support@cytech.biz please
|
| Posted: Thursday Mar 31st, 2016 07:37 pm |
|
5th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
Another curiosity. Despite the event log showing regular automatic Time/Date Change entries, I just found Comfort's time to be out by 43 seconds. I did a manual change using the submit button in CSM and it was then 50 seconds out! So I did another manual change after which it was 35 seconds out.
So it would appear there is something very odd going with time in general on my system, not just with DST.
|
| Posted: Friday Apr 1st, 2016 10:34 am |
|
6th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5500 |
| Status: |
Offline
|
back to top
|
I think there may be a problem with sunday 27 March only where the time update is wrong
Do you still have the wrong time today?
does anyone else have this problem?
Last edited on Friday Apr 1st, 2016 10:49 am by slychiu
|
| Posted: Friday Apr 1st, 2016 11:26 am |
|
7th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
I observed the same thing earlier today - the time and date was correct both sides of midnight until the first Date/Time Change was received from the UCM. At that point, the time jumps back an hour.
I manually sent the date and time from Comfigurator to correct things and then disabled time updates from the UCM to prevent this recurring each day. This is only intended as a short term fix while a proper solution is found.
|
| Posted: Friday Apr 1st, 2016 11:38 am |
|
8th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5500 |
| Status: |
Offline
|
back to top
|
that seems strange especially if nobody else sees the issue
can you re-upgrade the ETh03 to 2.20?
|
| Posted: Friday Apr 1st, 2016 08:18 pm |
|
9th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
Yes, I'll try that and see how I get on.
|
| Posted: Saturday Apr 2nd, 2016 04:25 am |
|
10th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
Unfortunately, that didn't work.
However, I can shed some more light on what is going on. It's more complicated than I first thought. As before, the time jumped back an hour on receipt of the first Date/Time Change from CSM after midnight. What I hadn't realised though is that after it crosses midnight for the second time an hour later, the next Date/Time Change results in DST being correctly applied so the time jumps forward an hour.
Although I hadn't noticed this before, there is no doubt in my mind that it has been doing this all week because it explains why my heating was failing to turn off at 00.59 am since the clocks went forward. This would also possibly explain why other people haven't noticed this bug as the time is only wrong for around one hour a day and if they don't have anything timed to happen in that window, they would remain blissfully unaware of what is actually going on.Last edited on Saturday Apr 2nd, 2016 03:03 pm by Craig Robins
|
| Posted: Saturday Apr 2nd, 2016 09:04 am |
|
11th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5500 |
| Status: |
Offline
|
back to top
|
No need to send the evemt log. We managed to duplicate the problem as you reported
|
| Posted: Saturday Apr 2nd, 2016 03:00 pm |
|
12th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
That's good. I look forward to the fix. In the meanwhile, I've offset the timer that switches off my heating so it happens the other side of 1am.
|
| Posted: Monday Apr 4th, 2016 05:55 am |
|
13th Post |
| Posted: Monday Apr 4th, 2016 07:46 pm |
|
14th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
Thank you. I'll do that.
|
| Posted: Tuesday Apr 5th, 2016 04:14 am |
|
15th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
Mixed results with the new firmware.
I'm afraid I am still getting exactly the same issue with the time/date jumping backwards then forwards again between 12am and 1am.
However, it does appears to have had a positive effect on the accuracy of the time in general. Prior to the firmware upgrade, every Date/Time Change was recorded in the event log. I believe such instances are only logged when the time is more than four seconds out. However, since the upgrade at 5pm yesterday such logged changes are rare outside of the 12am to 1am window when Comfort mistakenly thinks its time is an hour out.
I'm going to send you event log so you can see for yourself.
Regards,
CraigLast edited on Tuesday Apr 5th, 2016 04:25 am by Craig Robins
|
| Posted: Thursday Apr 7th, 2016 11:43 am |
|
16th Post |
| Posted: Thursday Apr 7th, 2016 03:34 pm |
|
17th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
Thanks. I'll let you know what happens at the end of the day.
|
| Posted: Friday Apr 8th, 2016 03:08 am |
|
18th Post |
Craig Robins
Member
| Joined: | Monday Mar 3rd, 2014 |
| Location: | |
| Posts: | 43 |
| Status: |
Offline
|
back to top
|
That appears to have fixed it. Thanks.
|
| Posted: Friday Apr 8th, 2016 05:26 am |
|
19th Post |
slychiu
Administrator
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5500 |
| Status: |
Offline
|
back to top
|
Thanks for the confirmation. The other changes in the firmware will be revealed soon
|
| Posted: Wednesday Apr 27th, 2016 04:25 pm |
|
20th Post |
|
