Homeseer Time off?

[Guest]

So, if there is any event in the 1hours , hs3 is ‘’skipping’’ they wont run?


same question for November, are the events going to fire two times?

[mitchmitchell1616]

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?)

Pete -- what timezone are you in? I was thinking at first that Mono may have told .net to switch times based on UTC rather than CST in my case but if you are in a different timezone and see it change at the same localtime that theory doesn't work.

[mitchmitchell1616]

So, if there is any event in the 1hours , hs3 is ‘’skipping’’ they wont run?


same question for November, are the events going to fire two times?

Matt -- no idea yet. Not sure whether events will be looking at the real system time or seeing the HS3 'GUI time'.

[Pete]

Mitch,

I am near Chicago so I think we are in the same time zone.

I do not think it is a mono glitch in HS3 for Linux....just a guess though.

Homeseer 3 does it own time thing relative to the system time.

Here my 15 Homeseer 3 touchscreens get their system time from the PFSense NTP server.

They are all controlled by HS3 and eventwise they follow the HS3 mothership time rather than the system time.

The touchscreen displays are off though after 10 PM and do not go back on until around 8 AM such that I do not see anything anyhow using Jon00 remote control.

Ahh...just noticed that my Tasmota devices did not change time...

5:09:47 MQT: /GarageDoor1/SENSOR = {"Time":"2019-03-10T05:09:47", "Switch1":"Off", "Switch2":"On", "DS18x20":{"DS1":{"Type":"DS18S20", "Address":"10A04713000800D9", "Temperature":46.5}}, "TempUnit":"F"}
05:11:26 HTP: Main Menu
05:11:30 HTP: Console

ICS-IBMNBK0:~$ date
Sun Mar 10 06:12:55 CDT 2019

Checking on my Espurna devices and while syncing to the NTP server they did not change time.

MQTT Status: CONNECTED
NTP Status: SYNC'D
Current time: 2019-03-10 05:16:20

Rebooted both devices.

Tasmota devices remained one hour off and Espurna devices devices also remained one hour off.

There is a built in firmware time change but it must not be set at this time.

A manual change to DST worked on Espurna.

Thinking for Tasmota need to send a command to change time zone as I never did configure the time zone.

[sparkman]

Here's a quick script to check whether the system thinks daylight savings time starts at the time your systems rolled over.

Sub Main(ByVal Parms As String)
    Dim Debug As Boolean = True
    Dim logName As String = "DST"

    Try
        Dim localZone As TimeZoneInfo = TimeZoneInfo.Local
        Dim DST As Boolean = False
        Dim localTime As Date = Now
        If Debug Then hs.writelog(logName,localZone.ToString)

        DST = localZone.IsDaylightSavingTime(localTime)
        If Debug Then hs.writelog(logName,CStr(localTime) & " : " & CStr(DST))

        localTime = #3/9/2019 7:14 PM#  
        DST = localZone.IsDaylightSavingTime(localTime)
        If Debug Then hs.writelog(logName,CStr(localTime) & " : " & CStr(DST))

        localTime = #3/9/2019 8:14 PM#  
        DST = localZone.IsDaylightSavingTime(localTime)
        If Debug Then hs.writelog(logName,CStr(localTime) & " : " & CStr(DST))

        localTime = #3/10/2019 1:59 AM#  
        DST = localZone.IsDaylightSavingTime(localTime)
        If Debug Then hs.writelog(logName,CStr(localTime) & " : " & CStr(DST))

        localTime = #3/10/2019 3:01 AM#  
        DST = localZone.IsDaylightSavingTime(localTime)
        If Debug Then hs.writelog(logName,CStr(localTime) & " : " & CStr(DST))
    Catch ex As Exception
        hs.WriteLog(logname, "Exception " & ex.ToString)
    End Try
End Sub

For me it displays the following in the log which is correct:

Mar-10 11:13:58 AM DST 3/10/2019 3:01:00 AM : True
Mar-10 11:13:58 AM DST 3/10/2019 1:59:00 AM : False
Mar-10 11:13:58 AM DST 3/9/2019 8:14:00 PM : False
Mar-10 11:13:58 AM DST 3/9/2019 7:14:00 PM : False
Mar-10 11:13:58 AM DST 3/10/2019 11:13:58 AM : True

For those where it rolled over to DST too early, what do you see?

[Pete]

Thank you Sparkman

Running it on HS3 on Ubuntu 18.04 see this:

Mar-10 4:26:13 PM Event Event Test Timecheck TimeCheck triggered by the event page 'Run' button.
Mar-10 4:26:13 PM Event Event Trigger "Test Timecheck TimeCheck"
Mar-10 4:26:13 PM Event Running script in background: /opt/HomeSeer/scripts/timecheck.vb
Mar-10 4:26:18 PM DST 3/10/2019 4:26:18 PM : True
Mar-10 4:26:18 PM DST 3/9/2019 7:14:00 PM : False
Mar-10 4:26:18 PM DST 3/9/2019 8:14:00 PM : True
Mar-10 4:26:18 PM DST 3/10/2019 1:59:00 AM : True
Mar-10 4:26:18 PM DST 3/10/2019 3:01:00 AM : True

Running it on HS3 on Windows 7 Pro 32 bit see this:

Mar-10 4:36:31 PM Event Event Tests Test Time Check triggered by the event page 'Run' button.
Mar-10 4:36:31 PM Event Event Trigger "Tests Test Time Check"
Mar-10 4:36:31 PM Event Running script in background: C:/Program Files/HomeSeer HS3/scripts/timecheck.vb
Mar-10 4:36:31 PM DST 3/10/2019 4:36:31 PM : True
Mar-10 4:36:31 PM DST 3/9/2019 7:14:00 PM : False
Mar-10 4:36:31 PM DST 3/9/2019 8:14:00 PM : False
Mar-10 4:36:31 PM DST 3/10/2019 1:59:00 AM : False
Mar-10 4:36:31 PM DST 3/10/2019 3:01:00 AM : True

[sparkman]

Thank you Sparkman

Running it on HS3 on Ubuntu 18.04 see this:

Mar-10 4:26:18 PM DST 3/9/2019 8:14:00 PM : True

Hi Pete, that leads me to believe it’s a mono issue and not a HS issue as the call to return that is a straight .NET/mono call. Would be interesting to see if other versions of mono show similar behavior. I’ll make an update to the script that also displays the time zone mono thinks it is in.

Cheers
Al

[Pete]

Thank you Al.

Yes on the testing HS3 computer I am running Mono 5.20.0.244

It is an Arm based 2Gb RAM Pine64.

Here is the same test using an Intel i3 running Ubuntu 18.04, HS3 V500, Mono 5.18.0.268

Mar-10 5:40:52 PM Event Running script in background: /opt/HomeSeer/scripts/timecheck.vb
Mar-10 5:40:52 PM DST 3/10/2019 5:40:52 PM : True
Mar-10 5:40:52 PM DST 3/9/2019 7:14:00 PM : False
Mar-10 5:40:52 PM DST 3/9/2019 8:14:00 PM : True
Mar-10 5:40:52 PM DST 3/10/2019 1:59:00 AM : True
Mar-10 5:40:52 PM DST 3/10/2019 3:01:00 AM : True

[sparkman]

Pete I've updated the script above to also write the time zone to the log. Does it show the proper time zone, or does it show UTC?

[Pete]

Thank you Al. It shows the proper timezone.

Mar-10 8:32:42 PM Event Event Test Timecheck TimeCheck triggered by the event page 'Run' button.
Mar-10 8:32:42 PM Event Event Trigger "Test Timecheck TimeCheck"
Mar-10 8:32:42 PM Event Running script in background: /opt/HomeSeer/scripts/timecheck.vb
Mar-10 8:32:46 PM DST America/Chicago
Mar-10 8:32:46 PM DST 3/10/2019 8:32:46 PM : True
Mar-10 8:32:46 PM DST 3/9/2019 7:14:00 PM : False
Mar-10 8:32:46 PM DST 3/9/2019 8:14:00 PM : True
Mar-10 8:32:46 PM DST 3/10/2019 1:59:00 AM : True
Mar-10 8:32:46 PM DST 3/10/2019 3:01:00 AM : True

[Guest]

I needed to track DST (on/off) via a virtual device.
if this can be useful to someone else, here's a small script to do so (based on sparkman test script above)

Sub Main(ByVal Parms As String)

Dim DST As Boolean
Dim localZone As TimeZoneInfo = TimeZoneInfo.Local
Dim localTime As Date = Now

DST = localZone.IsDaylightSavingTime(localTime)

If DST = True Then hs.SetDeviceValueByRef(7910, 100, True)
If DST = True Then hs.writelog("Daylight saving time (DST)","ON")

If DST = False Then hs.SetDeviceValueByRef(7910, 0, True)
If DST = False Then hs.writelog("Daylight saving time (DST)","OFF")

End Sub