DST doesn't work correctly (at least for CET/CEST) - Happy anniversary!

Community Playground General Discussions
1

The following applies to Vera V1@1.1.1186 (should be the same for Vera V2@1.1.1234):

Last night (2011-03-27) there was a clock shift from 02:00 CET to 03:00 CEST due to DST.

DAD updates the data for sun and moon once a day using a Luup timer (between 00:00:01 and 00:01:00).

2011-03-26 23:00:54 DAD[16872]: Timer: 2011-03-26 04:22:21 SunTwilightAstronomicalBegin, result: -1
2011-03-26 23:00:54 DAD[16872]: Timer: 2011-03-26 05:05:00 SunTwilightNauticalBegin, result: -1
2011-03-26 23:00:54 DAD[16872]: Timer: 2011-03-26 05:45:25 SunTwilightCivilBegin, result: -1
2011-03-26 23:00:54 DAD[16872]: Timer: 2011-03-26 06:19:18 SunRise, result: -1
2011-03-26 23:00:55 DAD[16872]: Timer: 2011-03-26 18:52:19 SunSet, result: -1
2011-03-26 23:00:55 DAD[16872]: Timer: 2011-03-26 19:26:14 SunTwilightCivilEnd, result: -1
2011-03-26 23:00:55 DAD[16872]: Timer: 2011-03-26 20:06:42 SunTwilightNauticalEnd, result: -1
2011-03-26 23:00:55 DAD[16872]: Timer: 2011-03-26 20:49:29 SunTwilightAstronomicalEnd, result: -1
2011-03-26 23:00:55 DAD[16872]: Timer: 2011-03-26 02:30:00 MoonRise, result: -1
2011-03-26 23:00:55 DAD[16872]: Timer: 2011-03-26 10:22:00 MoonSet, result: -1
2011-03-26 23:00:55 DAD[16872]: Timer: 2038-01-19 02:14:07 PossibleImpact2007VK184, result: 0
2011-03-26 23:00:55 DAD[16872]: Timer: 2038-01-19 02:14:07 PossibleImpact2011AG5, result: 0

Lua (first timestamp) gets it right, LuaUPnP gets it wrong …

In addition, a scene scheduled for 2011-03-27 01:00 CET was executed at 2011-03-27 00:00 CET.

I cannot believe that such a basic functionality doesn’t work! I reported the bug a year ago!

http://bugs.micasaverde.com/view.php?id=989

2

Unfortunately, I’ve come to the final conclusion that MCV isn’t willing (or able?) to fix fundamental bugs. Once again, a scene scheduled for 2011-10-30 00:00 CEST ran at 2011-10-30 01:00 CEST …

Just to name a few fundamental flaws that simply get ignored by MCV:
[tt]http://bugs.micasaverde.com/view.php?id=989
http://bugs.micasaverde.com/view.php?id=1451
http://bugs.micasaverde.com/view.php?id=1473
http://bugs.micasaverde.com/view.php?id=1487
http://forum.micasaverde.com/index.php/topic,7477.0.html (access for beta testers only; no fix provided by MCV …)
[/tt]

3

Ap15e, we noticed the problem and fixed it some time ago, but it didn’t make it in the 1350 firmware. I attached the fix for this, which contains 2 files:

[ul][li]/www/cmh/timezone.json[/li]
[li]/www/cmh/js/ui3/cpanel_data.js[/li][/ul]

Sorry for this inconvenience.

4

Thank for the fix.

What are the firmware requirements for the fix? Is it safe to apply the fix to Vera V1 and V2?

5

This should work for any firmware made after 14 June 2011, though older firmwares are not excluded. Anyway, you should make a backup of these files, just in case.