Announcement

Collapse
No announcement yet.

Log time is incorrect

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

    Log time is incorrect

    It really feels like I'm missing something simple. In my log output, each line has a time associated with it. Right now the log says about 11/17/2020 1:58:02 PM. However, my computer clock is reading 2:29PM (about 30 min difference). Where does the log time come from if not from the computer clock?

    clues are appreciated

    #2
    Is your Homeseer server the same computer as what you are observing the log from? If it is a different computer, then that computer's time might disagree with your computer.

    Comment


      #3
      Assuming you are running windows 10?? Here is a how-to on setting your computer time to NTP (Atomic clock time from Nist) I think Homeseer goes to the NIST website for the area so it has the proper time for sunrise and sunset to control conditions.

      https://www.groovypost.com/howto/syn...t-atomic-time/ This is for windows 10.

      If running Linux you can go here: https://linoxide.com/linux-command/s...-ubuntu-linux/

      For the lat long you have set in your computer, you can go here ( https://www.calculatorsoup.com/calcu...ise_sunset.php ) and see if the times match Mountain Standard time is UTC-7:00.

      Comment


        #4
        I appreciate the help from both of you guys. I did make sure all the PC are running the same time, and I used the method proposed by AllJailJ. Neigher seems to have affected anything. My log says 7:47:47 AM and the clock say 8:24 AM, so a difference of 37 min? Doesn't make senses - where else could this offset be coming from?

        Comment


          #5
          Just stumbled on a fix, although I don't have a clue why it fixes it. On the log screen, where it says "clear", "reset", "search", there's another button for "type filter". I opened it, and closed it (that's all), and the time jumped 37 min in the log. I don't think I've ever used that type filter, but there it is.

          Comment


            #6
            Totally strange. Glad you got it fixed.

            Comment


              #7
              Are you sure this is not simply a browser refresh issue?

              Comment

              Working...
              X