Latest Activity...
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.
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 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 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.
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.
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
How do expired codes get deleted?
Kirthi, you can determine when codes are deleted during the Door Lock Configuration and Grace Period.
Is there a buffer time so that the code can be active a few hours before official checkin time?
You can configure buffer times or Grace Period while setting your Door Lock configuration and Grace Period.
Yes, Yale please!!
OR is currently testing some Yale locks as part of the upcoming Hubitat Door Locks Powered by OwnerRez.
This is really great! Any chance Yale locks will be coming anytime soon?
Thanks Julie! OR is currently testing some Kwikset and Yale locks as part of the upcoming Hubitat Door Locks Powered by OwnerRez.
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?
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?
Agreed! Would love to see the same support for Yale/August locks!
How do expired codes get deleted?
Is there a buffer time so that the code can be active a few hours before official checkin time?
Yes, Yale please!!
Thank you so much for bringing this integration to OR users and much appreciated. Been waiting for this over wanting to use Remote lock for some time as all my properties use Schlage Encode.
With that being said are you able to use nested if then logic such as the below so codes don’t go out without requirements ? Currently I manually verify before sending to guest and would like to remove that step and then sending of checkin details.
example as below:
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?
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?
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.
Hey thanks, Paul - all those are the kinds of things I thought would be included in the integration, not just the few things that can be done in the Schlage app.
This is really great! Any chance Yale locks will be coming anytime soon?
As Shawn stated, those are just extras we added into OwnerRez so you can see them while you are there.
The integration, at large, is about being able to automatically set door codes for your bookings, and everything that goes with it:
All of the above should be obvious - this is what all of our door lock integrations do - but hopefully this helps clarify.
I see, thanks for that clarification.
Scott - what we mean by that is that you can now do those things inside OwnerRez. It's not meant to replace the need for the Schlage Home app but to have access to such info inside OwnerRez.
"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."
- These are things I can already do with the Schlage app. Are these the only features offered with this integration?
Looks like a lot of fun and great connections!
Wow, looks like it was a lot of fun! Yay OwnerRez! Sorry I had to miss it.
We had a fantastic time showcasing at the 2023 VRMA International Conference and had the pleasure of connecting with numerous OwnerRez users, property managers, and industry partners.
This year, we had 10 team members fly/drive to Orlando, FL, to ensure we could converse with everyone. If you didn't get a chance to speak with us, please sign up for one of our weekly demo webinars. We will exhibit at more industry events in the upcoming months, and you can find the full list of events here.
Here are some photos we took at the conference:
(Rex and Steve setting up the booth.)
(Jen getting the bright green booth fabric set.)
(Steve and Rex putting the final touches on the booth fabric.)
(The full OwnerRez booth set up and ready for meet and greet.)
(Welcome reception with everyone who just arrived at Disney Coronado Springs Resort.)
(Coronado Springs Resort is beautiful at night.)
(The owners of OwnerRez all dressed up and ready for our Hangout event.)
(The Hangout check-in team. We checked in 250 people!)
(Bird's eye view of the OwnerRez 2023 Hangout. Luckily, we had perfect weather!)
(Suzee, Bri, and Benton from our support team came to hang out with everyone at our event.)
(It's always great catching up with our good friends from Big Fish Rentals, Chad and Julie.)
(Chris and Devin with RentalGuardian having a great time at the party.)
(Ken and the team from Nofie enjoying the party thoroughly.)
(Paul with the team from The Global Improvement Group.)
(Selfie with Rex, Bri, Shawn, and Benton.)
(Packed Hangout with everyone having a great time.)
(Post Hangout event, catch up with the team.)
(Selfie with Steve, Lisa, Rex, Bri, and Jen.)
(Last day photo with the team at Touch Stay.)
(The team breaking down the booth set up.)
(Final team dinner before heading back to our daily routines.)
Thanks to VRMA for hosting a fantastic conference. We are excited to exhibit at future VRMA events in 2024!
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.
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.
Priced at $4/lock per month, the OwnerRez Schlage integration supports the following lock series:
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.
Be on the lookout for our upcoming Igloohome and Hubitat lock integrations powered by OwnerRez!
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.
