Time Trouble Shooting

Posted:
Fri Oct 28, 2016 7:14 pm
by Jag4666
Hi guys,
I have been fighting to get the Webapp to show the right time.
i have gone into the rasps-config and set my settings properly. It displays the UTC time right but the local time wrong. I have set the pi for TZ=UTC so when i type date, it shows the proper time at UTC.
Unfortunately the web log, etc. still shows the time as local time.
Is there anyway to fix this?
Re: Time Trouble Shooting

Posted:
Fri Oct 28, 2016 7:48 pm
by Jag4666
So it turns out i was finally able to get the local time to show as UTC time on Pi. Funny thing is though the event log still shows a different time that it does live.
Event:
Timestamp
Type
Message
2016-10-28 5:47:16 PM arm The alarm system has been armed.
2016-10-28 5:47:08 PM disarm The alarm system has been disarmed.
2016-10-28 5:47:02 PM arm The alarm system has been armed.
2016-10-28 5:44:05 PM disarm The alarm system has been disarmed.
2016-10-28 5:43:28 PM arm The alarm system has been armed.
2016-10-28 5:43:21 PM disarm The alarm system has been disarmed.
2016-10-28 5:42:33 PM arm The alarm system has been armed.
2016-10-28 5:42:27 PM disarm The alarm system has been disarmed.
2016-10-28 5:41:49 PM arm The alarm system has been armed.
2016-10-28 5:41:44 PM disarm The alarm system has been disarmed.
Live:
Timestamp
Message
2016-10-28 22:47:16 [01000001000000003A--],008,[f700000c0008000c0c020000000000],"2 ARMED AWAY ** ALL SECURE **"
2016-10-28 22:47:11 [10010001000000003A--],008,[f70000131008001c08020000000000],"HOUSE Ready to Arm "
2016-10-28 22:47:08 [10010101000000003A--],008,[f70000131008011c08020000000000],"HOUSE Ready to Arm "
2016-10-28 22:47:06 [01000001000000003A--],008,[f700000c0008000c0c020000000000],"2 ARMED AWAY ** ALL SECURE **"
2016-10-28 22:47:06 [00110001000000000A--],041,[f70000131041008008020000000000],"1 ARMED STAY May Exit Now 41"
2016-10-28 22:47:05 [00110001000000000A--],042,[f70000131042008008020000000000],"1 ARMED STAY May Exit Now 42"
2016-10-28 22:47:04 [00110001000000000A--],043,[f70000131043008008020000000000],"1 ARMED STAY May Exit Now 43"
2016-10-28 22:47:03 [00110001000000000A--],044,[f70000131044008008020000000000],"1 ARMED STAY May Exit Now 44"
2016-10-28 22:47:02 [00110301000000000A--],045,[f70000131045038008020000000000],"1 ARMED STAY May Exit Now 45"
2016-10-28 22:47:01 [10010001000000003A--],008,[f70000131008001c08020000000000],"HOUSE Ready to Arm "
Re: Time Trouble Shooting

Posted:
Mon Oct 31, 2016 9:30 am
by kevin
Live log time is based off time on client computer (through javascript) since this is a livestream from the device itself there is no actual "timestamp" it is generated on receive by the client computer.
Event log has timestamp from event on raspberry pi, then is manipulated with javascript on client side
Re: Time Trouble Shooting

Posted:
Fri Dec 23, 2016 8:03 pm
by R305
Hey, I had this problem too. It turned out that the Pi had the correct Universal time but the wrong timezone setting, so my notifications were showing strange dates and times (correct minutes though).
TTY into the Pi (I used PuTTY) and login. Then use the timedatectl command to see what is going on and also fix it. Here is a good reference page on how to use timedatectl in linux.
https://www.cyberciti.biz/faq/howto-set ... nd-prompt/Hope this helps.
Re: Time Trouble Shooting

Posted:
Thu Dec 29, 2016 9:56 am
by kevin
Ah yep, we don't ship it with a configured timezone outside of UTC, that would do it.
Re: Time Trouble Shooting

Posted:
Sat Dec 31, 2016 6:32 am
by Jag4666
Thanks R305, that was it. So simple, I can't believe I missed it.
Re: Time Trouble Shooting

Posted:
Sat Dec 31, 2016 12:25 pm
by R305
NP Jag. It's usually the "easy" ones that get me. Although they only seem easy after you solve them!