Homeseer Time off?

[Pete]

Just noticed here that my Homeseer time is off by one hour on two machines. Both systems have the correct time. Anyone seeing this?

[Guest]

Pete Hi Pete,

I just cheked and my time is ok there .

[sparkman]

All good on my system.

[baudi]

Looks like it did the "spring forward" a few hours early.

[mitchmitchell1616]

Yep, seeing it ahead by one hour now.

[sparkman]

For those that “jumped early”, are you on linux or Windows? Mine is still good and I’m on Windows 7.

[mitchmitchell1616]

Ubuntu Bionic (18.04) server here.

[drparker151]

Yes mine jumped ahead, I'm on linux too.

[zwolfpack]

Time still correct here in PST, both Windows (7) and Linux (rpi-stretch).

For those seeing the issue, what time zone are you in, and can you tell when the jump happen? (should be able to deduce from the log).

On Linux, timezone info is stored in /usr/share/zoneinfo. Some light reading:

https://data.iana.org/time-zones/tz-link.html

[drparker151]

At 8pm Central, my logs jumped one hour. That would be 2:00 am UTC. So appears HS3 changed at UTC not local.

My timezone in Ubuntu 18.04 is set to America/Chicago. When SSH into the system the command line shows the correct time, so I believe it's not caused by the timezone setting in linux being off.

EDIT: My time zone in HS3 is set to US America/Chicago

[sparkman]

11 PM here, and all is still good. I’m guessing a specific issue related to a mono version not returning the correct daylight savings time info.

[mitchmitchell1616]

Central time here, the jump happened at 8:00pm

Current Date/Time: 3/10/2019 4:19:48 AM
HomeSeer Version: HS3 Pro Edition 3.0.0.478
Linux version: Linux grendel 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 2 Days 10 Hours 52 Minutes 41 Seconds
IP Address: 192.168.1.11
Number of Devices: 871
Number of Events: 14
Available Threads: 199
HSTouch Enabled: True
Event Threads: 0
Event Trigger Eval Queue: 0
Event Trigger Priority Eval Queue: 0
Device Exec Queue: 0
HSTouch Event Queue: 0
Email Send Queue: 0
Anti Virus Installed:

Enabled Plug-Ins
2.0.29.0: BLRing
1.3.6.0: Device History
3.0.0.56: EasyTrigger
3.0.0.31: EnvisaLinkAdemco
3.0.0.13: EVCStat
0.2.0.10: FitbitSeer
3.0.1.9: ISYInsteon
1.2.2.1: Life360
3.5.5.0: mcsMQTT
3.1.0.13: MeiHarmonyHub
1.2019.211.1740: MyQ
3.0.0.14: NetCAM
3.0.0.54: PHLocation2
0.0.0.45: Pushover 3P
1.0.0.3: RainMachine
3.0.4.6: Tasker Plugin
3.0.1.0: Vista Alarm
3.0.0.93: weatherXML

mitch@grendel:~$ mono --version
Mono JIT compiler version 5.18.0.268 (tarball Thu Feb 28 15:24:08 UTC 2019)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(600)
Suspend: preemptive
GC: sgen (concurrent by default)
mitch@grendel:~$

[Pete]

Yes here it was last night on two HS3 boxes running Ubuntu 18.04 Linux. Just the Homeseer GUI was off by one hour and the system time was fine on these two machine. Third machine running HS3 on Windows 7 was fine.

Right now this morning at 0438 all is fine.

I can see in the logs to one machine the time changed between 7 and 9 PM yesterday evening.

Mar-09 7:00:00 PM Event Event Trigger "HourlyChime songandtext"
Mar-09 7:15:00 PM Log Maintenance 9 records, selected by date/time, were removed from the log database.
Mar-09 7:15:00 PM Log Info The log database is currently 3.57MB in size.
Mar-09 9:00:00 PM Event Event Trigger "HourlyChime songandtext"
Mar-09 9:00:36 PM Event Event Trigger "HourlyChime songandtext"
Mar-09 10:15:00 PM Log Maintenance 6 records, selected by date/time, were removed from the log database.
Mar-09 10:15:00 PM Log Info The log database is currently 3.57MB in size.

[mitchmitchell1616]

Same here, only affected the HS GUI, the system itself is synced to a GPS disciplined Raspberry Pi NTP server just down the hall. Time is now correct after the local DST time jump.

What version of mono are you running?

[Pete]

Mono 5.18 on Intel (i3) based computer with a patch for ASPX working and Mono 5.20 for Arm (Pine64) based computer with no ASPX working.

The Arm PIne64 has RTC with battery. The older RPi2's all have PiFace RTC shims for time.

Yes here utilize firewall PFSense with a GPS / PPS serial connection for time. Been using an NTP server here since the late 1990's. (started with a Windows NTP server back then).

GPS antenna went from the roof top to the attic to the basement over the years. GPS was an old Trimble (from a tank) to a SureGPS.



This is though a HS3 on Linux issue (bug?)



Here is a little blog I wrote relating to PFSense in 2013 on Cocoontech.

From: Anyone using PFSense as a firewall?




xxx