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

  • Posted on
  • By

One, two, Freddy’s coming for your STR. Three, four, better lock your door!

Get ready to be thrilled! As Halloween approaches, check out this week's chilling product update that's all about our October 25th release with 14 updates, including our hair-raising new Schlage Lock Integration Powered by OwnerRez, along with a number of creepy crawly bugs.

New Features

Schlage Door Locks Powered by OwnerRez

OwnerRez is proud to present our first direct lock integration, the long-awaited Schlage locks integration!

Not familiar with Smart Locks? A great place to start is by reviewing the Smart Lock Overview vacation rental guide.

Schlage Door Lock Logo

Priced at $4/lock per month, the OwnerRez Schlage integration supports the following lock series:

  • Encode (Wifi)
  • Encode Plus (Wifi)

For an initial release, we've made it quite feature-rich. After mapping a lock to a property, you can lock and unlock, and view lock info and events. You can also see at a glance the battery level and whether the lock is locked or unlocked.

Users can download the free Schlage Home app to get started. Then, pair their Schlage account and configure the lock integration directly in OwnerRez.

Here are the quick and dirty steps to take inside OwnerRez to get started:

1. Go to Settings > Door Locks (under Workflow & Devices)

2. Click the "Connect Schlage Home" button

3. Acknowledge the monthly fee per lock that will be added to your monthly charges if you have a Schlage lock or locks mapped. Click "Ok, I understand" to continue.

4. At that point, you will be sent to Schlage's website with a page that asks you to confirm a few things. These three things are paramount to establishing a successful connection to your Schlage lock(s) using OwnerRez. Do not proceed until you have completed all three.

5. Once you confirm all 3 have been completed, click each checkbox and then click "Let's go" to continue.

6. Then, enter your email address and password to sign in to your Schlage account. Click "Sign In" to continue.

7. Once logged in, Schlage will redirect you back to your locks page in OwnerRez. You can then click "Change" to tweak your Schlage integration settings.

8. Once you have completed step 7, you can proceed to mapping your lock(s) to your properties. We recommend you start with one to see how things are looking and working.

Check out the Schlage support article for more information.

Coming Soon - Igloohome and Hubitat

Be on the lookout for our upcoming Igloohome and Hubitat lock integrations powered by OwnerRez!

Bug Fixes

Don't Send Changed System Messages or Alerts When Only Cleaning Date is Changed. Guests and OR users sometimes received system emails or alerts that their booking had been changed. It was determined that the system emails or alerts were sent when an OAuth app such as Turno changed the cleaning date. We corrected this bug so guests and OR users will no longer receive booking changed alerts when apps change the cleaning date.

Ensure Payment Information is Required for Team Accounts Upgraded to Full Accounts. When a Team Access Staff Member user was upgraded to be a full user (i.e., billing will commence) they were not always asked to add a credit card. This has been fixed to require a card to be put on file to change the account from Staff to a Full account (billed) user.

Fix Cancellation Policy Preview Displays Incorrectly. When users created or edited a cancellation policy and selected the "Yes, but it's complicated" option, the available options included cancellation policies that the user had never used. This bug has been fixed to display only any previously used cancellation policies in the preview for any "Yes, but it's complicated" options.

Fix First Webhook Attempt Should Treat Any 2xx Code as Successful, Not Just 200. We were not treating 204 codes as success in our node version of the webhook sender. We corrected this error and will now treat any 200-299 code as successful.

Fix Rare Edge Case Error on Viewing Booking Transactions. An OR user encountered an error while attempting to view a booking transaction. We resolved this bug, and the user can now correctly view booking transactions.

Handle Very Long Names on Inquiries. The Inquiry widget's name field is limited to 32 characters, which can cause errors for long names. We have fixed this glitch to better handle long names by adding specific space-splitting logic to the spaces in long names.

Hide Registration Number Heading From Hosted Websites When Registration Number is Not Configured. Users that did not have their property registration number configured in the {PDESREGNUM} field and then created a Property Description Override for their Hosted Website noticed that the empty Registration Number heading was displayed live on their Hosted Website. We resolved this bug by not showing the Registration Number header if both the registration number and date fields are empty.

Improve Airbnb Publish Check Upon Connection. If an OR user created an unpublished Airbnb listing with one address, disconnected that listing from Airbnb, then created another OR property with a different address and attempted to connect that new property to the initial Airbnb listing, the listing would be unable to correctly sync. We have fixed this glitch to consider published Airbnb listings in the past only if it is published now and has an address, and if the listing was published previously when we try to push, that push will set the Airbnb listing to published.

Increase System Email Subject Maximum Length to 256 Characters. The email subject limit of 128 characters caused errors for users with long property names. We have increased the email subject limit to 256 characters. This will prevent errors for users with long property names.

Remove BridgePay as Payment Processor Option. BridgePay is a deprecated payment processor product only available in the United States. Due to underwriting limitations, new BridgePay account applications can no longer be submitted, and this payment processor has been removed as an option for OR payments.

Remove Disabled Integrations From Property Field Differences Article. Disabled API-integrated channels were visible in the  Property Field Differences support article when users clicked on the far right HomeToGo, Houfy +14 others dropdown menu. We've resolved this by not having those show any longer.

99 Comments (add yours)

Chris A
Nov 1, 2023 7:40 AM
Joined May, 2019 17 posts

Another Suggestion: Only send the door codes a few days before the guest arrival. Do not send all the codes immediately to the lock. The lock does have a 100 code limit, and when you are searching for a specific code to make an edit, it makes it extremely difficult to find a specific booking when there are so many in there. We have bookings showing up in ours that are a year away. I think if you guys can change the booking number to the guest name as well, both of these enhancements will make the feature easier to use.

Donaven B
Nov 1, 2023 8:56 AM
Joined Aug, 2022 34 posts

totally agree... in no case do I or would I use the OR booking number.

SHORE THING VACA
Nov 1, 2023 9:07 AM
Joined Mar, 2022 1 post

I use First Initial and full last name when setting up the Access Code Name in the Schlage App. Instead of the using the Booking number, could you program it to use first initial and full last name?

Obviously, the 4 digit request is a big deal. It looks like you guys are working on it. Additionally, I noticed when the code was generated by OR, the "Notify me when Code is Used" flag is off when I look at my app. Can this be changed to automatically be on?

Chris A
Nov 1, 2023 11:16 AM
Joined May, 2019 17 posts

Maybe there could be an option in the OR settings to use either name or booking number? It seems most people commenting use the name, as I do.

Paul W
Nov 1, 2023 11:34 AM
OR Team Member Joined Jun, 2009 833 posts

I've seen a bunch of questions about why OwnerRez is sending all the door codes to the Schlage lock up front, like at the time of booking, instead of waiting a few days before arrival.  For some people with a lot of future bookings, that means you have dozens of codes showing in your Schlage app.

This is a standard setting that can be configured for any lock integration, Schlage or otherwise.  Look at the "Generate When" option.

By default, it is set to "at booking time" which means the code is assigned and sent to the lock as soon as the booking occurs, even if the booking is 6 months in the future:

Just switch that over to "number of days before arrival" and fill in the number of days you want, and bob's your uncle:

 

Paul W
Nov 1, 2023 11:35 AM
OR Team Member Joined Jun, 2009 833 posts

Maybe there could be an option in the OR settings to use either name or booking number? It seems most people commenting use the name, as I do.

by Chris A – Nov 1, 2023 3:16 PM (UTC)

We are changing it to use the name.  The feedback on that has been overwhelming and the use case is pretty obvious.  The OwnerRez engineer working on lock stuff is already actively working on putting that in place.

Kelly M
Nov 1, 2023 4:49 PM
Joined Apr, 2021 26 posts

Quick follow up. Maybe I missed it but a Low Battery Alert would be nice. I change my batteries at 50% so having the option to set when the notice goes out would be an added bonus. 

by Nathan W – Oct 31, 2023 10:04 PM (UTC)

We do show the battery level, as you probably know, but you're right - an actual alert would be great since you won't see that battery level unless you go looking.  Same with an alert when the guest uses the lock, telling you that they entered.  There is a lot that can be done, but the first release was about getting a low-cost bare-metal integration out there for everyone to start pounding on.

Thanks to you as well, Nathan!

by Paul W – Oct 31, 2023 10:07 PM (UTC)

 

Another vote for this! Would be helpful to receive a low battery notification that we can set.

Kelly M
Nov 1, 2023 4:54 PM
Joined Apr, 2021 26 posts

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.

by Paul W – Oct 31, 2023 12:04 AM (UTC)

I just ran into this issue yesterday after regrettably updating my lock firmware... SO happy to hear that you are actively working on fixing this to allow us to set the code length manually as this has been a real bummer - thank you thank you! And thanks for all the hard work on the Schlage integration, so excited to finally be able to utilize this! :)

Kelley S
Nov 1, 2023 9:49 PM
Joined Aug, 2021 2 posts

I currently use Remote Lock and if a code is unable to be generated for any reason, they send me an email. Does OR do this as well? Do you continue to push to the lock if it isn't successful the first try? I don't see any documentation saying how your integration handles this. I manage homes in the mountains and wifi does go out from time to time. 

Kirthi K
Nov 2, 2023 8:24 AM
Joined Oct, 2021 2 posts

Hello,

Thank you for getting the Schlage lock integration! As others have pointed out, I would like to chime in as well.

1. Name of guest and not ORB booking number as the code name.

2. Delete obsolete codes: I understand that the code will not work, but schlage allows for 100 codes to be in the lock, and this will make the code list unwieldy to say the least if we are not actively deleting expired codes in a timely manner. I am having to do this manually to keep the code list from spiraling out of control.

3. My locks have been historically set to code for only 4 digits.  I noticed last night that one of my locks has now a 7 digit code set: 000xxxx, with xxxx as last 4 of the guest phone number. Prior to this, only the last 4 digits have been set.

Teresa J
Nov 2, 2023 1:37 PM
Joined Jan, 2023 6 posts

Any ETA on the 4-digit code length hot fix?  I ran into this same problem this morning when I activated 3 more locks that I wanted to get up and running.

Wanderlustpines
Nov 2, 2023 9:25 PM
Joined Feb, 2022 1 post

Hi, can you tell me if e will be able to adjust the check in and check out times for each individual guest? I am able to do that in RemoteLock if I want to allow someone to check in a few hours early or check out a few hours late I am able to adjust just that one guests time within their booking.

Kelley S
Nov 2, 2023 9:50 PM
Joined Aug, 2021 2 posts

You can adjust the checkin/checkout times of the reservation. I imagine this will update the codes if already created. Or, you can do it in the schlage app for sure. 

Asha P
Nov 3, 2023 12:28 PM
Joined Apr, 2022 2 posts

Just connected my Schlage lock. A few questions:
When does the guest receive the code?
Where do I see the code in case I need to resend to the guest? Can I set an email notification template to go out on booking and day of arrival with the code?

 

Thanks for setting this integration up!

Florian L
Nov 4, 2023 10:58 AM
Joined May, 2023 1 post

Is there any way to limit the number of digits for the automated Schlage codes? The default appears to be 8 digits.. I only want my codes to be 4 total digits, but Schlage is generating 7-8 digit codes. 

Paul W
Nov 5, 2023 11:05 AM
OR Team Member Joined Jun, 2009 833 posts

Hi, can you tell me if we will be able to adjust the check in and check out times for each individual guest?

Yes, this flows from the booking itself.  Every booking has a default check-in and check-out time, which comes from the default property rules.  If you don't manually adjust this on the booking, it uses the default.  If you change the check-in/out times on the booking, the code will follow that new time.

Kelley nailed it:

You can adjust the checkin/checkout times of the reservation. I imagine this will update the codes if already created. Or, you can do it in the schlage app for sure. 

by Kelley S – Nov 3, 2023 1:50 AM (UTC)

Also, keep in mind the "grace period" settings.  Grace period is always added onto the new time.  So if you give a specific guest early check-in at 1 pm, and your grace period is 2 hours, the code will start working at 11 am.

Paul W
Nov 5, 2023 11:32 AM
OR Team Member Joined Jun, 2009 833 posts

When does the guest receive the code?
by Asha P – Nov 3, 2023 4:28 PM (UTC)

The short answer is: whenever you decide to send it to them.  The code itself is generated at the "generate when" time setting on the integration page.  There are options for generating it at the time of booking (the default option), or certain number of days before arrival, or manually (ie. you set it yourself).

Assuming the code is generated at the time of booking, you can then configure templates/triggers to send it to the guest from that point forward.

Typically, the normal pattern is to send a message [x] days before arrival if certain conditions are met (booking is paid in full, renter agreement signed, etc).  You would customize the template to include the door code and possibly other information.

So it's kind of up to you.

Where do I see the code in case I need to resend to the guest?

Right on the booking overview page.  Once your lock integration is in place, all bookings that are at that property (ie. the property configured in the lock integration) will begin show a "Door Code" field on the booking.  It will show the code value right next to it if a code was generated.  There are other options there for Generate, Sync, etc so that you can change the code or resync to the lock.

Can I set an email notification template to go out on booking and day of arrival with the code?

Yes!  See above, or look at our documentation on automated messaging and field codes.

Dror E
Nov 5, 2023 1:45 PM
Joined Jul, 2022 5 posts

Paul,

If you are asking about examples why the integration is inferior to other options (RemoteLock, Jarvis) then the two examples in the comments - battery low alert and webhooks for first door entry etc are great examples. I am ok to pay "more" for having those features now before I move to OwnerRez integration. The way I look at it - If a guest can not enter since the batteries died and I did not get an alert, it does not worth the $1/saving a month for me. Love to see the v2 in the next few weeks and make the switch.

Asha P
Nov 5, 2023 4:50 PM
Joined Apr, 2022 2 posts

Thanks! 

Chris O
Nov 6, 2023 1:19 PM
Joined Mar, 2023 7 posts

Eric - Can I be a part of the Hubitat beta?