Announcement

Collapse
No announcement yet.

Security Offset not working for me under HS4 - Fixed!

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

    #16
    Originally posted by andyf View Post
    randy I'd like to start playing with this. What triggers are the security offset supposed to affect? Is it "Time is:" only or can you do a "Recurring trigger After:"? Any others?
    Security offset only applies to specific time based Triggers. It should apply to sunrise and sunset, this before/after sunrise/sunset. Once it is actually working, I’ll test them. Since sunrise and sunset change daily, it will be interesting to track. It does not apply to recurring triggers.
    HS4 Pro, 4.2.18.3 Windows 10 pro, Supermicro LP Xeon

    Comment


      #17
      Security offset is looking promising under 4.2.17.0. And it will apply to sunrise, sunset and this before/after sunrise/sunset.
      HS4 Pro, 4.2.18.3 Windows 10 pro, Supermicro LP Xeon

      Comment


        #18
        Originally posted by randy View Post
        Security offset is looking promising under 4.2.17.0. And it will apply to sunrise, sunset and this before/after sunrise/sunset.
        I only have one simple event running. Which means I'll have to wait for tomorrow to see if the time changes much with this HS4 version. But I figure if it gets your blessing it must be gold.

        Comment


          #19
          It is early yet, but yesterday’s Trigger times appeared to be Random. I installed 4.2.17.0 yesterday. I also added two more offset testing Events, one for sunset and another for sunset plus an hour. If you look at the trigger times before yesterday, they weren’t random. Starting yesterday the three triggers were very random. securityOffsetTime is set for 3:00 and triggered at 3:25 yesterday, where it had been at 3:17 almost every day before. Sunset was 5:28PM yesterday the trigger was 5:44PM and 6:55PM for an hour after sunset. Here are the times set for today showing promise that the times are truly random within the +-30 minutes for security offset.

          Click image for larger version

Name:	39221D3E-C10E-4AD8-B87D-E2ACF1EDB827.jpg
Views:	53
Size:	12.7 KB
ID:	1591669
          Click image for larger version

Name:	BBD381C3-4A25-402D-97E9-14C1FF1595C5.jpg
Views:	53
Size:	12.9 KB
ID:	1591668
          Click image for larger version

Name:	7AEC1691-7D78-4241-B39E-72FBC0951555.jpg
Views:	64
Size:	14.0 KB
ID:	1591667
          The 4.2.17.0 update was installed prior to yesterday’s triggers.

          2/9/2023 6:55:20 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffsetSunset+"
          2/9/2023 5:44:20 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffsetSunset"
          2/9/2023 3:25:00 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffsetTime"
          2/8/2023 6:43:09 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffsetSunset+"
          2/8/2023 5:43:09 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffsetSunset"
          2/8/2023 3:17:00 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffsetTime"
          2/7/2023 3:17:00 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffset"
          2/6/2023 3:17:00 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffset"
          2/5/2023 3:17:00 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffset"
          2/4/2023 3:17:00 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffset"
          2/3/2023 3:28:00 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffset"
          2/2/2023 3:17:00 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffset"
          2/1/2023 3:17:00 PM HomeSeer Event Event Trigger "HomeSeer Demo securityOffset"​
          HS4 Pro, 4.2.18.3 Windows 10 pro, Supermicro LP Xeon

          Comment


            #20
            The Events fired as they should have Friday, unfortunately I do not have logging prior to the last restart since 4.2.17.2. Every time I start HomeSeer, it deletes the log. Nothing in the log about it..If there's a problem, I normally get a log error, the log has never disappeared. It is almost like running on a Pi The Events below show completely different times than any of the priors. I think it is safe to declare this bug swatted! Once I get my logging situation corrected, I’ll track them for a week.



            Click image for larger version  Name:	secure1.png Views:	0 Size:	19.7 KB ID:	1592325

            Click image for larger version  Name:	secure2.png Views:	0 Size:	20.1 KB ID:	1592326

            Click image for larger version  Name:	secure3.png Views:	0 Size:	21.3 KB ID:	1592327
            HS4 Pro, 4.2.18.3 Windows 10 pro, Supermicro LP Xeon

            Comment


              #21
              I agree, my times appear totally random also.

              Comment


                #22
                Just installed upgrade 4.2.17.0 and can confirm that security offset is working in events now.
                Thanks for resolving this bug.

                Comment

                Working...
                X