Help with YRD240 Yale Keyfree Touchscreen Deadbolt Auto Lock Feature

[JDRoberts]

@hockeydan

@JDRoberts I guess I’m still a little confused. Are you saying your phone communicates with the beacon first and then the beacon communicates with the lock?
Making the lock have a longer time period to stay unlocked?

Sorry for the confusion! The details are in the thread I linked to above. But essentially what I use the IBeacon for is to make the area of detection smaller than it would be with other presence methods. So the lock is unlocked for the same amount of time, it’s just that the system does not detect me as being “home” until I am within about 3 m of my front door. (At the base of the wheelchair ramp there)

The phone detects the IBeacon when I am about 3 m away from it instead of the 15 m of the SmartThings arrival sensor or the even longer distance of regular phone Geopresence.

Because it detected that particular IBeacon, the phone sends a message to SmartThings. Then SmartThings unlocks the door.

A dual device approach to geopresence for smaller areas (sequential detection)

Continuing the discussion from Smart Presence Sensor randomly "leaving" and "returning": Battery life is fine on my presence fob, but I still get random drop-offs with both the fob and the phone presence. Using an idea from @DigitalM0nkey , I am changing over the way I use presence sensing for all activities. I’m now using dual devices at the geo-fence barrier, as well as a virtual presence sensor for better continuous occupancy indication. Basically I’m trying both reduce the range and improve reliability by using two devices that will be recognized in sequence rather than both at the same time. So this is how it will work at my house now: Smartthings recognizes that my phone or the fob, mainly the fob , has entered the Geo fenced area. but nothing else happens yet. I do not tri…

Estimote Ibeacons allow you to customize The signal strength of the Beacon, which in turn lets you change the detection area.

I hope that’s clearer.