Vera Light London not changing to British Summer Time

Community Playground General Discussions
1

Clocks went forward 1 hour in the UK today, but my Vera Light still shows GMT.
I have tried switching to another location and then back again, but it’s stayed the same.

Anyone else got the same problem?

EDIT: Just to add, if I go in through cp.mios.com, as the page loads, the time initially sets correctly, but once it finishes, it sets to GMT. Odd.

2

My time seemed to have changed when I checked this morning, but now it’s definitely 1 hour behind. >:(

3

Same problem for me in France. Still with the wrong hour. :cry:

4

+1
Same problem with Vera 3 in France.

5

Same here in the Netherlands. If I connect to Vera locally, the clock initially shows the right time but then loses an hour as the page finishes loading.

The internal clock is off as well: I’ve a scene that runs a fan in the basement at 11:00am, today it kicked in at 12:00am. Vera’s console shows the time as being one hour behind.

6

Thanks for you replies.

I’ve raised a ticket so we’ll see what the tech boys can sort out.

7

All the descriptions are consistent with Vera having the right time but the wrong timezone. That is, it correctly knows what time it is in UTC, but it applies the wrong offset to get your local time.

Things you can do to help MCV to identify this bug:

  • Clear your browser cache and see if it behaves any differently. Some versions of the firmware use your browser’s JavaScript timezone function.

  • SSH to your Vera and copy the output from:

cat /etc/TZ

uci show ‘system.@system[0].timezone’

8

same problem is docmented here:
http://forum.micasaverde.com/index.php/topic,10031.0.html

9

VeraLite@1.5.346:

CET-1CEST,M3.5.0,M10.5.0/3
Sun Mar 25 14:41:22 CET 2012

Wrong time.

Vera V1@1.1.1338

CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
Sun Mar 25 14:40:03 CET 2012

Wrong time.

Vera V2@1.5.346

CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
Sun Mar 25 14:44:30 CET 2012

Wrong time.

10

Same Problem of Vera 2 stuck at GMT on UI4. Upgraded to UI5, just in case it was fixed. Well it was not.

Edited /etc/TZ from GMT0BST,M3.5.0/1,M10.5.0 to GMT0BST,M3.4.0/1,M10.4.0

Changed the 5 to a 4 as I think there are only 4 Sundays in March and October.

Guessing 5 denotes number of Sundays in a month.

Well it works.

11

[tt]http://minix1.woodhull.com/manpages/man5/TZ.5.html[/tt]:

Mm.n.d
               This indicates month m, the n-th occurrence of day d (1 <= m <=
               12,  1  <= n <= 5, 0 <= d <= 6, 0=Sunday).  The 5-th occurrence
               means the last occurrence of that day in a month.  So M4.1.0 is
               the  first  Sunday  in  April,  M9.5.0  is  the  last Sunday in
               September.

Too difficult for MCV to handle? Or an OpenWRT bug?

12

Same problem in my VeraLite in Denmark. How do I “SSH my Vera”?

13

Ah, just posted in another thread, good find!

14

Thanks mano - that worked a treat!

15

Just a note: The above behavior is somewhat normal. When the dashboard first starts to load, it uses the local time as set on the computer that you are using. I would assume that your computer did change the time. Once your Vera is contacted and it sends its local time, the clock updates. This is another observation that points to Vera as not changing the time ahead on the correct day.

16

OpenWrt bug. Actually, a uClibc bug. See:
https://forum.openwrt.org/viewtopic.php?pid=162101
http://tomatousb.org/forum/t-456075
http://lists.busybox.net/pipermail/buildroot/2011-October/046667.html

Looks like a leap year bug. Having once written a timezone library myself (in Forth, for the language geeks), I can affirm that it’s easy to get this wrong.

Upshot:

  • MCV is a victim as much as the users.
  • MCV will need it to be fixed upstream, which will take more than a week.
  • It will fix itself in April.
  • Until then, use mano’s workaround (but revert it in April or you may hit the opposite problem in 2013).
17

uClibc 0.9.33 has the fix I was talking about. It was incorporated into OpenWrt at changeset 30374, seven weeks ago. In case MCV wants to update its base OpenWrt image. Or in case any Vera homebrewers want to build their own firmware image*.

  • Sentence may contain irony.
18

Same in Switzerland on Vera3 1.5.346, time not correct…

How would I change the time? Just choose another location for a temporary fix?

19

So it might be a week before this is fixed? Why is there no manual override? Now I need to go change my scripts for the wrong time and in a few days the scenes will run at the wrong time again and I need to fix it again. This is annoying.

20

Or you just set the wrong timezone so that your time is correct again instead of changing every single schedule in every single scene.

I can also confirm that mano’s fix is working. But I don’t really understand why…

root@MiOS_30101168:~# date
Mon Mar 26 09:29:31 CEST 2012