Schlage Encode

(page 5 )

• Page 1
• Page 2
• Page 3
• Page 4
• Page 5
• Page 6

Joined OwnerRez a few months ago and love the advanced functionality relative to our previous platform! Mostly finished with setting up all automated messaging/triggers but just need to get the Schlage locks integrated with OwnerRez! I really don't want to set up third party software when it is supposed to be rolling out any day. OwnerRez, is there any update as to when this will be available? If it will be a few months I'll work towards getting Jervis or other software set up. If we are talking a week or two I'll wait. Thanks in advance for your reply!

Hi Kate - great to hear; thanks for the feedback! The Schlage integration is still in Testing/QA as we want to get it right, but it won't be too much longer, definitely not "a few months." Keep an eye on our changelog and/or blog for the latest.

P.S. Inquiry Triggers are coming into Testing/QA soon and that will be another nice advanced automation option!

Is there a projected release date?

Is there a projected release date?

Hi Tony,

We're unable to provide an ETA, but it shouldn't be too much longer now! Testing takes time so we can ensure that we're delivering the quality integrations that our users deserve, and we appreciate everyone's patience.

Super excited for this! I believe once you have the lock integration and a better inbox many hosts will be able to drop "other" software's being used and strengthen the OR platform overall.

Will the initial release be for Schlage and Yale or just Schlage?

Also add alarm.com to the integration for the smart lock code.  I though alarm.com had a pretty wide usage and surprised OR isn't yet connected.  Would love this feature.

We're supporting Schlage Encode locks directly. We hit some roadblocks with a direct Yale integration, and, for now, will still only be supporting them through services like Remote Lock.
 
If you are using zigbee or z-wave Yale locks, you could use the upcoming Hubitat integration to control those directly. Hubitat is a more advanced integration, and we would only recommend it for tech-savvy hosts. It is launching in a private beta , with general availability coming after we've had some more time for it to be used in the field. 

Is there another feature request that will be tracking the Yale integration since this one is now released?

Hi Scott - OwnerRez Feature requests are opened by users, so I encourage you, if you feel so moved, to start one for Yale/August Wi-Fi Locks integration. At present, unless there is significant interest we won't be doing it due to integration costs.

Love that this integration was added. I just had my first booking since signing up for the integration, and a code was generated and set by OR. Only problem is, this was a 7-digit code and so far all of my codes have been 6-digit. My understanding is that once you set the first code on the lock, that "locks in" (sorry) the code length forever more.

I don't know whether this new longer code will work (it does show up in the Schlage app Access Codes list), but there was no way to dictate to OR what the code length should be. Curious if others have had guest stays already that used this new feature, and if you ran into code length issues.

I have had the same issue. Using RemoteLock, all of our codes were assigned the last 4 digits of the guest's phone number. Now with Schlage, it is assigning 000+ the last 4 digits. In other words, if the guest's phone number is 555-9456, the Schlage integration would assign 0009456, and RemoteLock would have assigned 9456.

Note that ONE of our four Schlage Encode locks Lists the  Access Code Length field as '4' and the other 3 locks say the Access Code Length is "Undefined". I am not sure what caused the differentiation. If there were a way we could set all of the locks ot have the same Access Code Length inside OR, it may solve the problem.

A secondary disappointment is that The Schlage integration shows the Booking # instead of the Guest Name in the Name field. This requires cross-referencing the number to the name instead of just searching by name.

As a follow up to my own post, the 7-digit code worked even though up until now only 6-digit codes have been used. Maybe Schlage removed the restriction of all codes having a uniform length?

I have the exact same issue as Elite Coastal with the 000X-XXX code. One lock in my house has a four digit code, but the other one has a seven digit code that says unidentified.  I really want to force a 4 digit code across both. 
I’ve submitted a support ticket for this. Please fix!

I also would really love the Schlage lock code (in the Schlage app) to show the guest name, not the OwnerRez number, as Elite Coastal also points out. Thank you. 

-Austin

www.smokymountainslodge.com

I have had the same issue. Using RemoteLock, all of our codes were assigned the last 4 digits of the guest's phone number. Now with Schlage, it is assigning 000+ the last 4 digits. In other words, if the guest's phone number is 555-9456, the Schlage integration would assign 0009456, and RemoteLock would have assigned 9456.

Might I ask why you switched from RemoteLock? I've been using them for 6 years and find the service, software, more than fine. Plus, the price, for me at least, is lower than what OR is charging.

Might I ask why you switched from RemoteLock? I've been using them for 6 years and find the service, software, more than fine. Plus, the price, for me at least, is lower than what OR is charging.

I switched because of the delay with RemoteLock primarily, as their activity reporting can be up to an hour delayed. In the Schlage phone app, the activity reporting is nearly instantaneous, and I am optimistic that a direct integration with OR will also show faster activity reporting. I do like that the management of the locks is within the OR app, but if you want to assign a temporary code not related to a booking (say for a maintenance worker), you would have to use the Schlage app where with RL you could manage codes of all varieties within their app. RL charges me $6/mo/lock, OR's Schlage integration would cost me $4/mo/lock.

OR team,

Can you tell us if the codes generated through the integration will be automatically deleted after a guest checks out? 

Thanks!

I'm in the same boat as others. It would be perfect if you could designate the number of digits and possibly use the guest name rather than booking number. I tried manually creating codes and it still added the additional zeros to it.

Quick update here...  Keep your eye out for the weekly Product Update blog post, which will discuss this in more detail, but an update went out this morning that included some Schlage fixes:

• Delete expired codes from lock
• Make code length editable now that Schlage supports it (for locks with latest firmware)
• Use guest name for access code name instead of ORBxxx number

Hooray!! Thank you!!

Thank you!!!