Unveiling Schlage Door Locks Powered by OwnerRez, Accompanied by Some Creepy Crawly Fixes!

Is this compatible with the Yale/August setup?  I am not familiar with Hubitat, but from my quick review it looks like they are not using the August platform.  Looks like they use zigbee and zwave, rather than the yale august app.  Any insight is appreciated.  I 

So Owner Rez generates a random new code for each guest and that can get added to guest messaging then deprogrammed after checkout? Is it possible to use the last four digits of their phone number which is easy for guests to remember?

Erin, you can configure door codes to be the last four digits of the guest phone number while setting your Door Lock configuration and send to guests prior to check-in.

I am currently using Remote Lock at a cost of $6 per lock per month. Would I be correct in stating that the OR link to Schlage will pretty much do the same thing as RL with the exception of adding additional lock codes for property gates or other secured entrances? I am using Schlage Encode Locks.

If you are using the Schlage Encode/Enclode Plus series of lock, the new OwnerRez integration can work directly with the Schlage API without requiring a third-party to synchronize codes. If you need to set additional codes on the lock, you would just use the Schlage app on your phone.

If you are using RemoteLock to setup additional codes to other devices OwnerRez does not directly support yet (basically anything else until the Igloohome and Hubitat integrations launch), you would still need to use RemoteLock to manage those. I would need to hear more about what features of RemoteLock you are using, and for which devices, to say for certain, but if you are using features in RL to synchronize codes between devices of difference brands, you may need to leave all your locks in their system for everything to work together.

I would recommend opening a support ticket with the specifics of your setup so we can get the full pictures, and do research as needed on your best path forward. 

Thank you so much for all the hard work.

I enabled this integration a couple of minutes ago, and I'm trying to figure out how it works. I thought there's a finite number of codes one can generate, at least, that's how it is in the Schlage iOS app.

Assuming is the same here, if for example, a code is generated when a booking is created, I'm assuming that code is held by OR and sent to Schlage to be used when that booking checks in (or whatever is set for the arrival grace period).

Is what I just said true?

Assuming this is true: does it mean if there is an overlap between the current booking and previous booking (the previous booking did not check-out yet) the previous booking code is overwritten? or are both codes valid and they expire based on Departure Grace Period? again, trying to understand how all this works.

 

One more question: at least in the Schlage iOS app, codes have names. I have one code for the Housekeeper and one for the Guest. help me to see when the guest used the lock, or when the housekeeper used the lock. what is the name of the code when I use this integration? the guest's name?

Alin

The code limit is set by the lock hardware. Generally it is 100 codes, but could vary by model.

You configure when the code is sent to the lock. By default it is sent to the lock at booking with an access schedule of the check-in and check-out times (plus or minus any grace period, which defaults to 1 hour before/1 hour after). The other option is to send the code X number of days before the arrival. This means you will see the booking in your Schlage Home App as soon as it is booked. It will be named after the OwnerRez Booking ID (ORB########). There is a 12 character limit to access code names, so we couldn't fit the guest name in there as well and keep it unique so there are no naming conflicts.

We had some internal discussions about whether we should do something different, but the product team decided that even the hottest properties generally never get dangerously close to the code limit. And if yours does, the "Generate When: A number of days before arrival" setting will help you deal with it.

For Schlage, you can have codes with overlapping access schedules. You just cannot have two entries with the name code, or the same name. 

I have three units behind a gate and need for the guests per each unit to have the same lock code for the gate's Schlage lock as they have for their respective unit. Can this be configured?

Thank you for doing this.  I know this has been something people have been asking for for quite some time.

 

Currently, I use Lynx for my lock management with Schlage and Yale Z-Wave locks managed through a Samsun Smart Things hub and Lynx has OR integration for the booking info.  Currently Lynx creates a code based on the phone number and has a specific window of time that it's active from check-in to check-out.  I also have property groupings and can assign permanent codes for the maid, the handyman, the owners, myself, and more.

Will OR support having codes for support staff and groupings so if I want someone to only have access to certain homes I can assign them to that specific group?  Also, are z-wave locks on the roadmap?

Additional code management for cleaning / other staff isn't part of this update and you would still manage any non-booking codes directly with your specific lock management solution. I am sure our product team aware of this potential feature, but I am unsure if it is on the roadmap.

Z-wave and Zigbee locks will be part of our Hubitat integration, which is in a closed beta at the moment as we are working through the QA and bugfixes still. If you are using other hubs, we will definitely collect feedback and work through the integration priority based on community demand.

 

Is there a buffer time so that the code can be active a few hours before official checkin time?

You configure this in OwnerRez. We will take the check-in / check-out time and subtract / add the grace periods your configure on the lock integration (right at the top "Arrival / Departure Grace Period"). The default is 1 hour.

Joseph,

The codes are stored locally in the encode and will work even if wifi goes down. It may be advantageous to generate several back-up codes in the event of wifi failure and last minute bookings.

Trevor

Does the Schlage Encode lock require the Wi-Fi to be working at the time the guest is checking in or will the lock save the data at the time the booking is created and schedule the code in advanced without the need for Wi-Fi at the time the guest checks in?

The codes are sent directly to the lock and saved locally. You will actually get an error message if the lock is offline or the code failed to generate for any reason (either in a popup or email, depending on how the booking was created in OwnerRez).

Is this compatible with the Yale/August setup?  I am not familiar with Hubitat, but from my quick review it looks like they are not using the August platform.  Looks like they use zigbee and zwave, rather than the yale august app.  Any insight is appreciated.  I 

This release only includes the general availability of our Schlage integration, which supports the Schlage Encode / Encode Plus line of smart locks. Igloohome and Hubitat are in closed beta.

Hubitat is intended to be used as an alternative to always-online "cloud" home automation, thus its focus on the Zigbee and Z-Wave connectivity. It can support some Wi-Fi devices, if the devices can receive commands over the local network and not require a cloud integration. I've tested this with my Kasa smart switches, but am unaware of any Wi-Fi smart locks that are supported. Being a piece of physical security, I would guess most manufactures would worried about network security. The Z-Wave and Zigbee protocols are short-range, and require a secure handshake to pair with your controller hardware.

Hubitat requires more setup than other out-of-the-box solutions, so I would not say just anybody should run out and buy one in anticipation of the upcoming support. Definitely read up on it and decide if you'd prefer a more turn-key solution (lock pun!).

So it sounds like from what I’ve been reading, there is no current “planned” support for our August integrated locks.  I had switched to yale/august locks thinking they were a pretty common standard in STR but if we have to we will switch over to schlage as I prefer OR integration over 3rd party.  

So it sounds like from what I’ve been reading, there is no current “planned” support for our August integrated locks.  I had switched to yale/august locks thinking they were a pretty common standard i

Curious. What August lock (model number) are you using?  Is it Wifi or smart/z-wave?

I have three units behind a gate and need for the guests per each unit to have the same lock code for the gate's Schlage lock as they have for their respective unit. Can this be configured?

If you map the single gate lock to each property in question, then use either the "Use Guest Phone Number" or "I will manually set the code" option, then each lock will get the same code as long as each lock is using the same code length.

If you use the "Generate Random Code" setting, I would not guarantee each lock would get the same random code, particularly if the code failed to set on one of the locks and the system has to retry setting the code it may regenerate a new random code.

Hey Paul.  We use the Yale Assure locks models YRL 216/236 and YR C/D 226/246/256.  Both are Wifi and we use the August app and remotelock to control today.  

I don't know what to make of this. My configuration is not the same as the sample configuration from Door Locks - Overview

My configuration is on the left, and the screenshot from the doc is on the right with those arrows showing the differences. To be clear, by differences, I mean configs that don't show up in my settings, not different choices of values.

What I'm honestly more "concerned" about is not having the ability to set the code length. As far as I can tell, right now, the system wants to generate a 8-digit code and I can't change that. In Schlage iOS app, my existing codes are all 4 digit codes

Have I done something wrong here?

I don't know what to make of this. My configuration is not the same as the sample configuration from Door Locks - Overview

 

My configuration is on the left, and the screenshot from the doc is on the right with those arrows showing the differences. To be clear, by differences, I mean configs that don't show up in my settings, not different choices of values.

What I'm honestly more "concerned" about is not having the ability to set the code length. As far as I can tell, right now, the system wants to generate a 6-digit code and I can't change that. In Schlage iOS app, my existing codes are all 4 digit codes

Have I done something wrong here?

Alin, the support doc screenshot has been updated but it is not a Schlage specific screenshot. See the Schlage support doc for more specific details.

Thank you Anne.

Is there any way to change the code length? I don't see a way in OR and also I don't see any configuration about code length in the Schlage iOS app (where I can set 4 digit codes). when I try to set a 4 digit code in OR the set code popup errors with "Code must be 8 numeric digits" 

Thank you Anne.

Is there any way to change the code length? I don't see a way in OR and also I don't see any configuration about code length in the Schlage iOS app (where I can set 4 digit codes). when I try to set a 4 digit code in OR the set code popup errors with "Code must be 8 numeric digits" 

Alin, did you review the Schlage Limitations? That may be affecting your configuration. Feel free to reach out to our Helpdesk Team for further questions.

I don't see a way in OR and also I don't see any configuration about code length in the Schlage iOS app (where I can set 4 digit codes). when I try to set a 4 digit code in OR the set code popup errors with "Code must be 8 numeric digits"

We actually ran across this earlier this morning and are preparing a hotfix to correct it.

There was also a Schlage update to the API in the past few days that fixed a similar problem for integrated partners (like OwnerRez).

Very soon, this will be fixed so that you can set a code 4-8 digits in length.