Schlage was released on 10/25/23. Igloohome will likely be next and then Hubitat will be released sometime after (or they could be released together - TBD). The initial development is done and currently undergoing QA.

Hubitat is in private beta testing. Escalate inquiries to T2. See https://help.ownerrez.com/a/tickets/218912

Pricing is $4/lock per month.

Schlage

The Schlage (pronounced SHLAYG) integration supports all Schlage Encode Wifi / Encode Plus Wifi locks. Users will need to create a free Schlage account download and use the Schlage phone app to set up the lock. They then can go into OwnerRez pair their Schlage account and set up the lock integration.

Supported Locks

Encode (Wifi)
Encode Plus (Wifi)

Features

Custom Codes
Last X digits of guest phone number
Random Codes (as generated by OwnerRez)
Lock / Unlock commands
Lock status
Battery level
View lock events
View access logs

Limitations

4 to 8-digit lock codes
All codes on the lock must be the same length (NOTE: the user can have locks mapped that are each configured with different length codes)
The first code entered into the lock will determine the code length
All lock codes must be deleted to change the code length

Igloohome

Igloohome products are designed to work offline, using their "algoPINs" (short for algorithmic PIN). Users need to create a free Igloohome account, download and use the Igloohome phone app to set up the locks over a local/short-range Bluetooth connect. The setup process exchanges an encryption key that is stored on Igloohome's servers. With this setup, users can generate an algoPIN valid for a certain time period without needing to communicate directly with the lock.

Because they can work offline, Igloohome locks are ideal for remote locations with non-existent or poor internet access.

To the best of our knowledge, these are the current Igloo products supported.

Without Wifi Bridge

Features

Igloo generated codes

Limitations

Users cannot specify the code, nor use the guest's phone number
Different locks at the same location will have different codes
Code length is preset as 7-9 digits (exact length varies on the length of stay)
The code must be used within 24 hours of its start time or it becomes inactive
Stays < 29 days, the start and end time must be a whole hour (i.e. 2 p.m., not 3 p.m.)
- OwnerRez automatically rounds the start time to the top of the configured hour, and the end time to the next configured hour
Stays > 29 days, the start time must be a whole hour, and the end time must be the same hour
- OwnerRez automatically rounds the start time to the top of the configured hour, and the end time to the same hour, or next day if check in < check out time
No lock information (battery, logs, etc)
No remote lock / unlock

Wifi Bridge

Igloohome's Wifi Bridge device can be used to provide greater control over the locks by bridging the Wifi/cloud connection to the locks over Bluetooth. Users would purchase the bridge and configure it with the phone app allowing them to remotely manage the lock.

Features

Igloo generated codes
Custom Codes
Last X digits of guest phone number
Random Codes (as generated by OwnerRez)

Limitations

4 to 6-digit lock codes
Bridge device must be online and within Bluetooth range of the lock
Same first use time limit, top of hour / matching hour logic applies regardless of bridge device

Possible future features for a version 2

These are available via the API when users have a Bridge, and we even have some basic functionality built out, but it's hidden from end users currently.

Lock / Unlock
View access logs
View battery level

Hubitat

The Hubitat integration is unique because it is not a lock brand, but rather a home automation hub for people with Zigbee or Z-wave devices (low-energy wireless communication protocol). It is ideal for people who don't like the idea of all of their devices reaching out to the internet as it keeps the management all local. It is a more advanced option, and arguably shouldn't be recommended to users who don't already use it.

Users do need to purchase the $3/month ($30/year) "Remote Admin" subscription from Hubitat to use the integration.

In addition to purchasing the remote admin subscription, users will need to download and install our "OwnerRez" app on their Hubitat hub (via a ZIP file) and already have their locks configured, then "pair" them with the OwnerRez app, then pair the OwnerRez app with their OwnerRez account.

Device support gets murky as the system works by defining "capabilities" that each device has by exposing a set of APIs based on each capability. At a minimum, we need the "Lock Code" capability to work with the OwnerRez integration. Testing is being done with a Kwikset and Yale locks. Here is the supported locks list and users can filter by Device Type = Lock.

Features

Custom Codes
Last X digits of guest phone number
Random Codes (as generated by OwnerRez)

Limitations

Lock code length can vary by lock
- OwnerRez automatically limits / pads the code length as needed on a lock-by-lock basis
The Hubitat Hub must be online and able to communicate with the lock at check-in time to configure the code
- We have a number of safeguards in place to protect against codes not getting configured on the lock, but a prolonged power outage, misconfigured clocks/timezones, software crash, etc could cause failures.
- The Hub does not need to communicate with OwerRez or the internet to configure the locks provided it was online at some point after the booking is created
Hubitat is not user-friendly when compared to the larger brands

Possible future features for a version 2

These are available via the API and we even have some basic functionality built out, but it's hidden from end users currently.

Lock / Unlock
View battery level
View access logs (this is conceptually possible, and framework was put in to capture the data, but it is less fully implemented than other integrations.)