intriguing.
might also be relevant that it wasn’t in this case resetting to the default check-in time but seemed to be resetting back to an arbitrary time that I think I must have added during my last round of testing.
happening again.
but I found a workaround is to refresh user codes in Z-wave JS and try again - immediate and subsequent changes to check-in time are then sticking.
@fitz247 this should be fixed. Happened with a bunch of other cleanup work I was doing.
For folks that may, or may not, have been paying attention, there have been a bunch of releases recently. As of this writing, we’re v2.3.4 is out.
Here’s a run down of all the changes that have occurred recently:
- Tests are now in place for > 90% of the integration. This makes it easier to move forward with confidence as I make other changes. It also means that as I find specific bugs, we’re now getting regression tests so that other changes shouldn’t re-break something.
- The internal components have been overhauled to use Home Assistant best practices
- Calendar and sensors are now kept in sync. Previously I was using some custom logic on when the various entities updated. They now all follow the internal coordinator. This has had the added benefit of changes, particularly overriding start / stop times, are much more responsive
- The calendar and sensors will now only be in an unavailable state if the upstream calendar is not available during startup. Ideally, you should not see them as unavailable at all
- We’re much more resilient to platform outages and we’ll ride cached data where appropriate
I do have more changes that I will be making in the future to improve the integration more.
1 Like
This integration continues to be a life-saver, thankyou.
However FYI I am still seeing time changes will not stick before the actual day.
1 Like
Are you on the latest version? Doing an override should definitely be sticking now, I haven’t had it not at all with the latest version.
v2.5.1 is now released. If you picked up any of the releases v2.4.0 - v2.5.0 and you integrate with Keymaster you’re going to need to upgrade to this release as it fixes a regression that was found to be introduced with v2.4.0 where new events would not get put into Keymaster slots.
I’m using this integration to manage locks on my STR that we have listed on AirBNB and VRBO. Everything works great on Airbnb but not on VRBO. The code is never the last 4 of the guest phone number with VRBO. Did some digging and it looks like the phone number is not coming across with the ical link. Is there a way to make this work?
I no longer have a working iCal link for VRBO so I can’t check to see if things have changed, but when I first added VRBO as a platform the iCal I had access to showed me that VRBO and Booking.com both do not provide any DESCRIPTION element in their calendar events. This means that the only information that Rental Control can get is the reservation name / ID from those platforms.
If you’re listing on multiple platforms I would suggest that you consider investing in a Platform Management Service (PMS) as they can usually get all the needed info for you. I’m currently engaged with a gig that is setting up on Guesty. I’ve got a few more integrations and an App (aka Add-On) in support of Guesty that I will be releasing in the next few weeks.
Guesty killed Guesty for Hosts, I’m considering Guesty Pro or Lodify. Can you speak about the integrations? That will make my decision easier.
Well, I don’t have an example calendar to work from for Lodgify so I don’t know how well it works with RC. What I can say is that I’ve been working with someone getting setup on Guesty Pro. The calendar that they output sucks mightily but I recently built a calendar bridge app that can handle getting better data out of Guesty Pro. I also just built out another integration that allows you to get even more data out as well as push up data for custom fields.
Both are very early releases. I’m not certain how many bugs are still in there, but it’s at an operational point for them.
I haven’t made any announcement threads yet for either of them but you can get the app by adding GitHub - tykeal/homeassistant-addons: Home Assistant Apps from tykeal · GitHub to your add-on store and then installing RentalSync Bridge.
The Guesty integration can be found here
I have a basic door code sync blueprint available here that will allow you to shove your door code back into a custom field on a reservation for use in messaging.
Also, if you’re curious about the Captive Portal that is in that addon store, that was also built out recently and supports TP-Omada network controllers (I’ll probably add Ubiquity as well in the future) and ties back into RC to do captive portaling using the door code as a device access PIN for the duration of their stay.
All of this has been built out because I got hired on to do some gig work to help setup a multi-unit building with HA and RC.
That’s awesome! I am leaning toward Guesty Pro instead of Lodify. I will probable do it this weekend. I have some existing reservations and the migration process with my message automation will probably need a full weekend of work.
But congrats on the gig!
Just an FYI I found out about another PMS just yesterday: Hospitable (note I’ve added a referral link on that since they give me one). I’m probably going to do their free trial here in a bit as Guesty is still just way to expensive for me to stomach. I’m hoping that this one will work out for me!
@Rodrick just an FYI I did sign up to Hospitable and so far I’m enjoying it as a PMS. I haven’t done any switching of RC to it but I can say that the calendars that it outputs are very good so it will be an easy replacement from that point of view.
Guesty is very expensive! I demoed Hospitable April 2025. I will give it another look.
I agree that Guesty is very expensive. That’s why I was rather happy to find out about Hospitable! Very affordable and I just finished pulling in all my AirBnBs to the platform. I’m going to hold off on switching calendars until I’m between guests 
I just had a guest locked out, and traced the root cause to Airbnb changing the calendar url for my listing. Result was all rental control codes were wiped (I’m a bit curious the existing entries weren’t just cached?). Updating the calendar URL immediately fixed it of course.
I’ve never seen this before but makes me nervous! I’m wondering what best practice would be to generate an alert when calendar syncing fails (of course there is stuff in the logs but i’m not routinely watching those)?
I’ve never had Airbnb change the calendar URL before. That seems very sketch. Those are supposed to be pretty much never changing as a change in the URL would break sync with other platforms!
To answer your question about caching. We cache… but only for a bit. If you only have one event in your calendar, then if the calendar moves or goes away but you’re still getting a valid calendar it will eventually clear. If you have more than one event in the calendar and it just up and disappears, then it will remain until the next reload as we detect that as an error and keep using the current calendar.
I know, right! But no doubt it changed, i was careful to note both versions!