Thanks for the response Chris...our point on most of these requests is that OwnerRez is our system of record and is the system that we use to communicate with guests and where we go if we need to find information about a property or booking or guests or whatever...
If we look at them one at a time...
1. Notification on Battery Level. We too have setup Hubitat to do this and it tells us when we are at the percentage that we set one time per day until we fix it. Since OR has this information on the door lock in OR already it would be nice to have OR notify instead of relying on the hub and the twilio service I have installed to send us a notification.
2. Logs. I do not want an email for every lock open and close. We are 42 properties and what would be hundreds of emails each day. I believe for nearly every integration that is done there are detailed logs kept on OR. Hubitat is limited on what it stores and what can be filtered, etc... and having to search through thousands of emails to find a specific event would be problematic as well. If the logs lived in a database somewhere that could be filtered by property, lock, date, time, type of event, etc.... then we could narrow down particular things. This for us is more of a security thing so we can track when staff/contractors enter the property and for guest issues and claims. We do this with our camera system as well. Lets just say we have had instances where guests make claims that ultimately turn out to be unfounded but finding the details is a time consuming process. We also use it to confirm no shows.
3. Notification when not booked... this is also a security thing... we have had situations where someone would "bump" the lock to gain access to the property. The event of the door opening was logged, no booking or block. It really a notification specific to an event that has occurred in the logs that have been collected.
4. Notification of first use... we had this with other lock providers. Not sure how they accomplished it... again probably back to collecting log information and then processing it. We would like this in OR so that we can then trigger a communication to the guest... in particular a welcome to the property, give it a quick look is there something not right? Thing first impression survey. We would also like to have a status on the property set so that we can visually see it on the ribbon view that the property is occupied. When in the busy season it is sometimes necessary to do last minute things that while they could wait until the next guest... if the current guest has not checked in yet let me quickly drop off a throw that needed laundering, refill the laundry soap or dishwasher pods, etc... things that if we knew the guest wasnt there yet we could just do without having to call the guest to ask if we can drop something off, etc...
5. Staff Codes - These would be no different than any other code except they do not have a start and end time. OR now has a staff component for access to OR and in the case of the staff we would just want to have it generate a code that lives in the lock all the time. We do this now manually using the lock code manager. We deliberately set our staff codes to be 5 digits with a starting digit different for each geographic area and our owner codes are also 5 digits starting with a 9. This keeps them from conflicting with guest codes which are 4 digits and being added by OR. The ability to add codes OR already has. The Team Access section they already have. We would just like to have a property select list so we can determine which properties to add the staff person to and a field for the code they have been assigned. OR would then just put that code onto each of the property hubs.
6. Owner Blocks - we also use these for contractors. Generally speaking we notify them of when they can get into the property but for some reason a block seems to also follow the standard checkin and checkout times of the property even though a block has no time fields associated with it. On a booking we can adjust the times to reflect property defaults or change them to whatever we want. In a block this is not possible so we usually have to manually go into the lock code manager to give the contractors a time that is outside of the typical property times. We would really like blocks to be like bookings where we can set the time for them to be active.
While Hubitat can likely do much of this, as I said I like to try to have one source of truth. Most of these things we have addressed with manual solutions or with an integration we created with Twilio and I know we could go further with Twilio -> Zapier -> OR but ultimately we would like to see this stuff in OR so we didn't have to develop that type of solution.
