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.

102 Comments (add yours)

Bri
Oct 4, 2024 11:09 AM
OR Team Member Joined Mar, 2022 99 posts

Is there another integration that would work better? This still hasn't been solved and is a back and forth between Schlage and Ownerrez that I am a bit frustrated by, both blaming the other for being the issue (and I am guessing Schlage is at fault but it's still frustrating to be in the middle of this and feeling helpless since I'm JUST a user with no power in this situation).  I would like to change to another integration if it works better and allows me to have the default toggle to code usage notification as on.  

by Susan – Oct 4, 2024 2:01 AM (UTC)

Hi Susan,

We have updated our support content so that our users are aware of this limitation.

https://www.ownerrez.com/support/articles/integration-schlage-door-locks#notification

Susan
Oct 4, 2024 11:13 AM
Joined Sep, 2021 8 posts

Is there another integration that would work better? This still hasn't been solved and is a back and forth between Schlage and Ownerrez that I am a bit frustrated by, both blaming the other for being the issue (and I am guessing Schlage is at fault but it's still frustrating to be in the middle of this and feeling helpless since I'm JUST a user with no power in this situation).  I would like to change to another integration if it works better and allows me to have the default toggle to code usage notification as on.  

by Susan – Oct 4, 2024 2:01 AM (UTC)

Hi Susan,

We have updated our support content so that our users are aware of this limitation.

https://www.ownerrez.com/support/articles/integration-schlage-door-locks#notification

by Bri – Oct 4, 2024 3:09 PM (UTC)

Thank you for the update!