Announcement

Collapse
No announcement yet.

AutoLock Event Premature execution

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

    AutoLock Event Premature execution

    I'm experiencing a premature locking of my lock(s) when I manually unlock my door deadbolt (Kwikset), and the weird thing is that it doesn't happen always only randomly sometimes, even though my "AutoLock" Event is set to only lock after being open for 5 minutes. I've included a copy of the event for review can someone advise as to how one resolves "Premature locking"? Before someone asks, yes I have disable the locks autolock capability and is only controlled via manual or HS3 commands. Mike
    Attached Files
    Computer: CUK Intel NUC7i7BNH
    Op System: Windows10 Pro - Work Station
    HS Version: HS4 Pro Edition 4.2.19.0

    Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

    #2
    I was hopeful someone might jump in here using what many do, delayed events.

    I don't use delayed events. Rather, I took the timer approach where if something happens that I want to happen, then the timer is reset to zero. If the timer reaches 5 minutes, then I lock the front door.

    Here are two events:
    Attached Files
    Michael

    Comment


      #3
      Michael, thanxs for the comeback. As part of my edumcation/curiosity why are you using a timer vs the direct method "Lock has been Unlocked for at least 5m, 0s" as I used, can you explain the pro's/con's. You also make mention of delayed events, obviously I must be missing something in regards to HS3 logic-wise. Mike
      Computer: CUK Intel NUC7i7BNH
      Op System: Windows10 Pro - Work Station
      HS Version: HS4 Pro Edition 4.2.19.0

      Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

      Comment


        #4
        I like timers because I can look at the timer device and see how many minutes have elapsed as opposed to calculating when the delayed event is supposed to fire.

        Not that one or the other is better or worse, just that my brain understands the former over the latter.

        All of my "occupancy" events, including the Front Door event, are based on timers.

        One of the advantages of using timers, for me, is that when all Room occupancy timers have elapsed, meaning that they have reset to zero and are stopped, then I can do various things, including putting the house to sleep.

        In my HS2 days, this was not possible to have the house put to sleep, autonomously: we had to push a button on a keypad to initiate the sleep sequence.

        With timers, I don't have to physically engage to initiate the sleep events - but I can if I want, either using a minimote, a HS-WD100 scene or Alexa.

        As I said, others use delayed events. Perhaps my OCD doesn't allow me to use this approach, but that is why HS3 is so powerful. If you can imagine it then it is probably possible.

        Perhaps others may chime in explaining other approaches including delayed events.

        Enjoy the journey and the successes!
        Michael

        Comment


          #5
          Here is my garage Start Timer Event:
          Attached Files
          Michael

          Comment


            #6
            In my garage occupancy event, any of the triggers will reset the timer to zero and let it start counting up again.

            This way, if we are in the garage, or using any of the doors, we keep setting the timer back to zero until such time that none of the triggers "trigger" such that when an elapsed timer reaches a specific time, I can start to shut things down in the garage.
            Michael

            Comment


              #7
              Michael, thanxs for the explanation and pictures (worth a thousand words!). What does the "&hs.SetdeviceValueByRef and String doing? I see that there are two devices 542 and 527 I assume that device 527 is a virtual device and it inserting "Garage" as device status msg? Mike
              Computer: CUK Intel NUC7i7BNH
              Op System: Windows10 Pro - Work Station
              HS Version: HS4 Pro Edition 4.2.19.0

              Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

              Comment


                #8
                Please disregard the immediate script commands. I evaluated a plug in and when I decided that it didn't meet my needs and removed it, it unfortunately messed with my device strings so I had to figure out how to put them back where they should be.

                I do like the writelog script command as it reduces the clutter in my log with the group options. All I get is if the timer started, in this event, or if it elapsed, based on another event.

                Another example of having HS3 do what you want!
                Attached Files
                Last edited by Rvtravlr; September 1, 2017, 11:17 PM.
                Michael

                Comment


                  #9
                  Thanxs for taking the time and explaining. I think I will adopt your timer approach unless someone else can explain delayed events approach and their merits. Mike
                  Computer: CUK Intel NUC7i7BNH
                  Op System: Windows10 Pro - Work Station
                  HS Version: HS4 Pro Edition 4.2.19.0

                  Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

                  Comment


                    #10
                    Perhaps Randy will chime in - he is the guru in event explanation, including delayed events. Others, too, have great advice. Uncle Michael, Sparkman, Rupp and many others.
                    Last edited by Rvtravlr; September 1, 2017, 11:56 PM.
                    Michael

                    Comment


                      #11
                      Michael, quick clarification when I look at your "Lock Front Door" Event the first IF "Front Door's Value is more than 5m, 0s" I'm assuming your using the "Timer Front Door" timed value set in "Front Door - Start Timer" event?
                      Computer: CUK Intel NUC7i7BNH
                      Op System: Windows10 Pro - Work Station
                      HS Version: HS4 Pro Edition 4.2.19.0

                      Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

                      Comment


                        #12
                        Yes, in this event the timer, Front Door, is what I am triggering on (actually the minutes elapsed of the Front Door timer).
                        Michael

                        Comment


                          #13
                          Michael, many thanxs for sharing your door lock and occupancy events. I've incorporated the timer schema and it so far it seems to be working without any premature execution when I manually open the inside bolt. I made a few minor modifications; changed "Unlocked for inside handle" to "Unlocked" in the event that someone opens the door via other means (keypad) or zwave command that after 5 minutes open, it would lock the door and I also changed "timer value becomes" instead of "timer value is more than", based on Randy's Event gotcha's. Mike
                          Last edited by MNB; September 3, 2017, 12:24 PM.
                          Computer: CUK Intel NUC7i7BNH
                          Op System: Windows10 Pro - Work Station
                          HS Version: HS4 Pro Edition 4.2.19.0

                          Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

                          Comment


                            #14
                            Originally posted by MNB View Post
                            Michael, many thanxs for sharing your door lock and occupancy events. I've incorporated the timer schema and it so far it seems to be working without any premature execution when I manually open the inside bolt. I made a few minor modifications; changed "Unlocked for inside handle" to "Unlocked" in the event that someone opens the door via other means (keypad) or zwave command that after 5 minutes open, it would lock the door and I also changed "timer value becomes" instead of "timer value is more than", based on Randy's Event gotcha's. Mike
                            I have one observation. "timer value is more than" is not a gotcha, since the event resets and stops the timer. It actually is a better choice because it avoids another gotcha in his event - using "exactly" if someone happens to trip the motion detector right at the 5 minute mark, the event would never run. Using "more than" will cause the door to lock as soon as ther is no motion more than 5 minutes after the timer is started. Since the event stops the timer and resets it, the event will not trigger again until more than 5 minutes after the timer is restarted.

                            For the record I am at a loss as to why your event in the first post didn't work. My only guess is that it might be a critical timing issue where there is a slight delay in setting the Last Date after the status of the lock is updated. You could test the theory by using "exactly" instead of "at least" as the Trigger. This change would make the Trigger window very narrow, virtually eliminating the likelihood that the event could trigger due to the Last Date being updated after the status.
                            HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

                            Comment


                              #15
                              Thanxs Randy as always your guidance is valued. Understand your point in regards to the Trigger and will make the necessary change.

                              As I made mention at the start of this thread, I wasn't see the instantaneous locking occurring after opening the door manually via deadbolt every time but it occurred just enough instances to make it a nuisance. I agree with you that it seems like a critical timing issue. I will set one of my locks to "exactly" to test your theory. Mike
                              Computer: CUK Intel NUC7i7BNH
                              Op System: Windows10 Pro - Work Station
                              HS Version: HS4 Pro Edition 4.2.19.0

                              Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

                              Comment

                              Working...
                              X