Jarvis systems

I used Jervis before I was a Hospitable client. Hospitable’s Devices section made Jervis obsolete for me. Is there a reason you still prefer Jervis over Hospitable Devices?

I’d generally agree with Tom here — unless you have a very specific need, staying within Hospitable’s native setup is usually the safer option.

Hospitable’s Devices feature is built on top of seam.co, which is widely used across the industry, so you’re not really missing much in terms of core capabilities. Most major lock brands supported by Jarvis are also supported there.

The main advantage of staying native is the tight integration with reservations:

• codes are automatically created and updated based on check-in/check-out times
• any change to the booking (dates, times) can update access without manual intervention
• fewer sync issues compared to third-party bridges

That’s something you don’t always get reliably when you go through an external system like Jarvis.

Where Jarvis could still make sense:

• if you need advanced building logic (shared doors, complex access groups, etc.)
• or if your lock brand / setup isn’t supported in Hospitable

But if your setup is fairly standard STR, adding another layer often just adds complexity and potential failure points without much upside.

I do use Remotelocks advanced logic but I can mostly do that with hospitables native solution. 

The problem I have is the type of locks hospitiable offers won’t work with some of my community doors. Either the type of locks don’t hold enough codes or the type of door (slam door) needs a special lock that I get from Key In Code which isn’t supported by hospitable. 

I use Jervis only for automation of my garage door.  I wasn’t aware of this type of capability within Hospitable. For my my garage access it’s been great.

Same here, ​@Tom Beerley. I wouldn't recommend paying 10 dollars per lock or so to Jarvis or RemoteLock. Not worth it