Announcement

Collapse
No announcement yet.

Homeseer Time off?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Homeseer Time off?

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

    Click image for larger version

Name:	time2.jpg
Views:	37
Size:	22.9 KB
ID:	1291326
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
    Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

  • #2
    Pete Hi Pete,

    I just cheked and my time is ok there .
    Attached Files

    Comment


    • #3
      All good on my system.
      HS 3.0.0.548: 1976 Devices 1156 Events
      Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

      Comment


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

        Comment


        • #5
          Yep, seeing it ahead by one hour now.

          Comment


          • #6
            For those that “jumped early”, are you on linux or Windows? Mine is still good and I’m on Windows 7.
            HS 3.0.0.548: 1976 Devices 1156 Events
            Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

            Comment


            • #7
              Ubuntu Bionic (18.04) server here.

              Comment


              • #8
                Yes mine jumped ahead, I'm on linux too.
                HS3 SEL running Pro Edition 3.0.0.531 on Ubuntu 18.04, mono 5.20, 656 devices, 209 events.
                Plug-Ins: Chromecast, Device History, EasyTrigger, Ecobee, JowiHue, LutronCaseta, MeiUnifi, PHLocation2, Pushover 3P, SDJ-Health, Sonos, WeatherFlow, weatherXML
                Scripts: SparkMan's Lock Event, 5 of Jon00 scripts.

                Comment


                • #9
                  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

                  Comment


                  • #10
                    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
                    HS3 SEL running Pro Edition 3.0.0.531 on Ubuntu 18.04, mono 5.20, 656 devices, 209 events.
                    Plug-Ins: Chromecast, Device History, EasyTrigger, Ecobee, JowiHue, LutronCaseta, MeiUnifi, PHLocation2, Pushover 3P, SDJ-Health, Sonos, WeatherFlow, weatherXML
                    Scripts: SparkMan's Lock Event, 5 of Jon00 scripts.

                    Comment


                    • #11
                      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.
                      HS 3.0.0.548: 1976 Devices 1156 Events
                      Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

                      Comment


                      • #12
                        Central time here, the jump happened at 8:00pm Click image for larger version

Name:	
Views:	0
Size:	25.8 KB
ID:	1291368

                        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:~$
                        Attached Files

                        Comment


                        • #13
                          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.
                          - Pete

                          Auto mator
                          Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                          Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                          X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                          Comment


                          • #14
                            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?

                            Comment


                            • #15
                              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.

                              Click image for larger version  Name:	image_77515.gif Views:	1 Size:	105.0 KB ID:	1291379

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


                              Click image for larger version  Name:	GPS.jpg Views:	1 Size:	64.1 KB ID:	1291376
                              Here is a little blog I wrote relating to PFSense in 2013 on Cocoontech.

                              From: Anyone using PFSense as a firewall?




                              xxx
                              - Pete

                              Auto mator
                              Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                              Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                              X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                              Comment

                              Working...
                              X