Announcement

Collapse
No announcement yet.

AutoLock Event Premature execution

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

    #16
    Originally posted by MNB View Post
    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
    The intermittent aspect is what made me suspicious of it being a timing issue. I'm curious to hear if your test resolves it.

    I don't use controlled locksets on any of my doors (yet) so I have no experience with them.
    HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

    Comment


      #17
      I've set my sidedoor to the "Exactly" and will advise if I experience any premature locking.

      I've had z-wave (Kwikset) dead bolt locks for a number of years and had great success with them (no real issues). What I like about the Kwikset is they also have the capability to key themselves to a single house key, I've yet to actual use it on any of my locks (but great backup if needed)
      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


        #18
        Originally posted by MNB View Post
        I've had z-wave (Kwikset) dead bolt locks for a number of years and had great success with them (no real issues). What I like about the Kwikset is they also have the capability to key themselves to a single house key, I've yet to actual use it on any of my locks (but great backup if needed)

        Schlage is the same way. All of the locks in my house, including interior locks, are Schlage and I keyed them to all be the same.
        Originally posted by rprade
        There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

        Comment


          #19
          Collin, its been awhile since our last postings.. When I started my z-wave journey with VERA HA, Door locks were my first devices at the time Kiwkset deadbolts was the only product that could be controlled remotely while the others were conventional deadbolts with reporting capabilities. As I mention its a nice feature but to date I haven't used them (physical keys). 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


            #20
            Regarding using keys.....

            Once my daughter came home late in the evening and I had already gone to bed. I was woken in the wee hours of the morning by a pervasive stench emanating from her bedroom. It smelled like Monsanto or DuPont were sent on a mission to create the cheapest perfume possible. In those days I had to get up early for work and sleep was a precious commodity so loosing a few hours was a big deal. The stench led me to an admittedly irrational frustration. In my poisoned and agitated state I decided to kill time before heading out by changing the batteries on the lock. I forgot to put the plastic retaining gizmo back in that keeps the batteries in place. When leaving for work, early before the luminous orb in the sky decided to grace us with it's presence, I closed the door with a little more gusto than was strictly called for. Long story short, I couldn't get in when I came home that afternoon. At least one battery had been dislodged by my emphatic door closing. I had to break out a basement window and crawl in through the mechanical room to get inside. I always keep a key to the door on my key ring these days.

            What is the moral you say? Automation is nifty and all but it's still got a long way to go before I'll trust it with things like letting me in the house when it's raining outside.

            I really should just replace that key with a bump key.
            Originally posted by rprade
            There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

            Comment


              #21
              Collin, thanxs for sharing.. I find it interesting that when one is "poisoned and agitated state" I translated as "pissed" would use zen like actions to replacing lock batteries to sooth the beast. You never said why it smelt like a perfume festival, I was waiting for skunk sprayed me retort. But your moral is aprapo yes I too keep a spare key on my ring for the "Murphy's Law" event. Mike
              Last edited by MNB; September 3, 2017, 04:37 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


                #22
                Randy, I can confirm your theory that using "Exact" vs "at Least" does make a difference I've tried multiple times (30x) to manually open all of my locks and have yet to experience an "premature locking" episode. Again thanxs for lending your expertise, I don't think I would have figured it out and would have simply lived with the problem..... nah!

                Edumacation question so how does an Trigger window have a Last Date being updated after the status? Is that due to the locks being battery devices and there might be latency? 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


                  #23
                  Originally posted by MNB View Post
                  Randy, I can confirm your theory that using "Exact" vs "at Least" does make a difference I've tried multiple times (30x) to manually open all of my locks and have yet to experience an "premature locking" episode. Again thanxs for lending your expertise, I don't think I would have figured it out and would have simply lived with the problem..... nah!

                  Edumacation question so how does an Trigger window have a Last Date being updated after the status? Is that due to the locks being battery devices and there might be latency? Mike
                  I think that is a reasonable guess. It could be something unique to your locks or it might be something that needs to be addressed programmatically. I will send Rich an email describing the situation and see if he can look into it.
                  HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

                  Comment


                    #24
                    I will have to look deeper since if "exactly" works, "at least" should also work as they both work on the last change time of the device. Maybe the status of the lock is going to unlock before the last change is updated and there is a small window there where the event gets triggered. Will report back what I find.

                    Originally posted by MNB View Post
                    Randy, I can confirm your theory that using "Exact" vs "at Least" does make a difference I've tried multiple times (30x) to manually open all of my locks and have yet to experience an "premature locking" episode. Again thanxs for lending your expertise, I don't think I would have figured it out and would have simply lived with the problem..... nah!

                    Edumacation question so how does an Trigger window have a Last Date being updated after the status? Is that due to the locks being battery devices and there might be latency? Mike
                    💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                    Comment


                      #25
                      I did find a possible race condition where the status of a device was being updated before the last change time. Its a small window but it could be what is causing this. I put in a fix for that.

                      While looking at that I noticed another oddity. For the case of the locks if you use the "at least" trigger, the event actually triggers multiple times. This is because events are checked every second and the lock could take a few seconds before its actually locked. So if it takes 3 seconds to lock, the event will trigger 3 times since the trigger is still true until the lock actually changes. This causes extra Z-Wave activity and load on the battery.

                      The fix is to use the "cannot re-trigger" option on the event and set that to say, 5 seconds. I cannot see an automated way to fix this issue as Z-Wave commands are queued so HS does not have a reliable way to know that the command was completed. Ideally there needs to be a way for HS to know when a command has completed and during that time ignore triggers on the event in progress.

                      Originally posted by rprade View Post
                      I think that is a reasonable guess. It could be something unique to your locks or it might be something that needs to be addressed programmatically. I will send Rich an email describing the situation and see if he can look into it.
                      💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                      Comment


                        #26
                        Many thanxs Rich for looking into this, I guess I wasn't imaging it.. Your suggestion to use "Cannot re-trigger" Option, I had been using it originally when I had my trigger set to "at least" set for 4 minutes (hoping the problem would go away which it did not) after wards I've since adjusted it my current 1 minute value. The point is that it did not have any effect in avoiding said race condition. I still think that since the locks are battery devices that there is a latency of reporting/receiving status hence the small window of opportunity to trigger prematurely (my two cents) I'm happy with using the "exact" trigger solution as it seems to do what I wanted with out premature locking during manual operations. 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


                          #27
                          The "cannot retrigger" suggestion was only for keeping the event from triggering multiple times when it did trigger, which is something you would not see unless you looked at the log. It would not fix the problem with the event triggering too early. I hopefully put in a fix for that.

                          Originally posted by MNB View Post
                          Many thanxs Rich for looking into this, I guess I wasn't imaging it.. Your suggestion to use "Cannot re-trigger" Option, I had been using it originally when I had my trigger set to "at least" set for 4 minutes (hoping the problem would go away which it did not) after wards I've since adjusted it my current 1 minute value. The point is that it did not have any effect in avoiding said race condition. I still think that since the locks are battery devices that there is a latency of reporting/receiving status hence the small window of opportunity to trigger prematurely (my two cents) I'm happy with using the "exact" trigger solution as it seems to do what I wanted with out premature locking during manual operations. Mike
                          💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                          Comment

                          Working...
                          X