Yes calendar.rental_control_x is the calendar that RC is actually tracking for things. If you pull up the calendar sidebar in Home Assistant you’ll see the calendar there. All guest bookings from the platform (Airbnb in your case) will show up there. Please note, Airbnb removes finished bookings from the exported calendar so the only way to see past booking dates is on Airbnb itself.
1 Like
Please note that v1.2.3 has been released. This should handle the problems that myself, and others, have been seeing with Airbnb over the last several months were you’ll get a calendar update that is empty even when you are in the middle of hosting a guest.
Things to note about the method of caching that has been implemented here.
- It only works after the calendar has been loaded fully and has more than 1 event in it
- The integration now ignores a calendar refresh if the number of events drops to 0 when the last stored calendar has more than 1 event in it. The refresh will continue to be ignored until the incoming calendar has at least 1 event in it or the events in the current calendar age down to 1
- If you expect the calendar to drop to 0 for some reason, the only way to have it pick this up if your current calendar has more than 1 event in it is to reload the integration as that throws away all current data from the calendar platform.
Will this work with Schlage Encode WiFi locks?
Rental Control doesn’t directly manage the locks themselves. It only works on top of Keymaster. Unfortunately, Keymaster only supports Z-Wave based locks as such, no this will not work with a Schlage Encode WiFi lock.
Encode locks have poorer battery life than their Zwave counterparts, so they’re probably not ideal to use for rental properties. That being said, it probably wouldn’t be that difficult to add encode locks to KM. But not having the hardware makes that a barrier.
WARNING: Problems with Keymaster 0.0.99 (current “stable” release as of time of this warning) and HA 2025.8.0 please note that something in how HA 2025.8.0 is working with ZWave is breaking Keymaster’s ability to properly detect that Zwave is up and working. Until Keymaster can be updated to fix this I strongly recommend that if you’re using Rental Control that you not upgrade to HA 2025.8.0!
1 Like
@firstof9 mentions that the Keymaster beta resolve this issue. RC does not currently support the beta as entities got moved all around and logic of the advanced options (needed for RC to operate) is dramatically different.
Mainline of the git repo has a pre-release beta of RC that works with the beta branch of Keymaster. It has a couple of bugs that I have not been able to fully squash yet (which is why I haven’t released an actual beta or full release yet).
Known issues with it:
- Timeboxed events (that is events with their own times) do seem to work, but they may potentially throw some errors in the log and I haven’t figured out why
- Events that have their start or end date change do some really screwy things to the checkin and checkout times for some reason. I have yet to figure out why but I suspect it has to do with the entities now in use by Keymaster having a timezone attached to them when the old ones (created via templates) were timezone naive IIRC.
A note on upgrading to Keymaster v0.1.0-b1 if you have only one lock at play, then do the upgrade, reboot and when the system finishes startup, reboot one more time and you should be good.
If you have more than one lock you will probably want to completely remove your Keymaster configurations and rebuild them as the migration can choke enough on multiple locks that it never completes cleanly.
Rental Control v2.0.0 has been released. This version now requires Keymaster >= v0.1.0-b0 to be installed if you are using RC to drive lock management with Keymaster.
Keymaster v0.1.0-b0 (or greater) is required if upgrading to Home Assistant 2025.8.x due to changes in ZWave configuration.
Hello, can I combine the apartments? I have four, each with EVENT-0 to EVENT-4.
For each apartment, I need to see individually when the next guest is arriving.
However, I would like to see an order, regardless of which apartment the guest is moving into.
Max M - 1 October 2025 - 5 October 2025 - Apartment 1
Eva P. - 3 October 2025 - 12 October 2025 - Apartment 2
Claus X. - 7 October 2025 - 15 October 2025 - Apartment 1
Chris T. - 13 October 2025 - 16 October 2025 - Apartment 3
To manage multiple units you need to have the following:
- An iCal for that unit (not shared with other units)
- Configure a Rental Control using that iCal
Seeing the schedules is more a matter of what you do with your cards. Personally, I use Atomic Calendar Revive for this in schedule view.
Here’s a quick configuration that would get you all of your RC calendars into this view:
type: custom:atomic-calendar-revive
name: Rental Control Calendar
enableModeChange: true
entities:
- entity: calendar.rental_control_*
icon: mdi:home
firstDayOfWeek: 0
maxDaysToShow: 360
refreshInterval: 60
sortByStartTime: false
showCurrentEventLine: false
showMonth: true
showWeekDay: true
showFullDayProgress: true
showEventIcon: true
showNoEventsForToday: true
disableCalLink: true
disableCalEventLink: true
disableLocationLink: true
disableEventLink: true
showHiddenText: false
showDate: true
hideFinishedEvents: false
showRelativeTime: true
showLocation: true
dimFinishedEvents: true
showProgressBar: true
showTimeRemaining: true
Figures, I didn’t actually test the code I gave you. I forgot that Atomic Calendar doesn’t do auto-entities globing. You have to explicitly add each calendar entity to it that you want to track. Just add several entity stanzas and you’ll be fine
1 Like
I often need to override default check in times… this has worked fine previously. On rental control 2.02 however any manual adjustment is quickly overwritten. Is this a intended?
That shouldn’t be happening. I do overrides on a regular basis as well. A couple of questions that does come to mind, do you have a lot of reservations on the property or is it usually only one? Also, what platform are you using for your calendar?
Good to hear it isn’t meant to happen!
I am only synching with AirBnB via iCal.
Yes, there are a reasonable number of future reservations - currently I can see 10. Does Rental Control only create 6 slots?
This has never been an issue until the last few weeks…I had a guest unable to get in approx 3 weeks ago in but I initially assumed it was my mistake so didn’t note what release I was on at that point.
I’ve noted something else potentially unexpected: when I manually add the required code in a slot not managed by keymaster to work around this problem (using Zwave JS), when the default synch time arrives for keymaster, the status of the slot in the keymaster ui changes to ‘Active’. However (as the Yale/Lockwood Zwave locks don’t tolerate duplicate codes), I can see from Zwave JS that the slot manged by keymaster is actually available (ie empty).
In one sense the UI is correct so perhaps this is intended? - the required code is active - though not in the slot indicated.
Yes, there are a reasonable number of future reservations - currently I can see 10. Does Rental Control only create 6 slots?
It creates as many sensors as you specify. The default is 5. The minimum is technically 1, but feasibly it’s 2, at least if you’ve got same day turn-over.
If you’re manually programming it via ZWave-JS, then the best thing you can do is program the exact same slot that RC used in Keymaster.
I’ve got a couple of locks that still don’t program correctly (even with the Keymaster beta) but that’s mostly due to my mesh having some issues. I always make sure that I’m using the same slot that is assigned in Keymaster and it resolves issues related to code deletion and updates as well.
If this code override issue is happening consistently, then I would suggest the following:
- Turn on debug for the integration
- Raise an issue on GitHub with an attached log file (scrubbed of any PII!)
Doing something like that will help with tracking down what might be happening.
Thanks for your quick response.
However while santity-checking right now I have had two slots have a time override stick for 20 minutes. The calendar update time is 5 minutes so it looks like whatever was happening has resolved itself. I have no idea what has changed to fix that!
Thats a good tip regarding putting the code in the the correct target slot, I wasn’t sure if that would cause more trouble. In the past I used to have periodic issues with the status showing incorrectly in the Rental Control UI but that appears to have vastly improved in the recent versions.
Well the over-writing time bug is back.
Noticed it yesterday (one day before a booking) and thought I would try again same day in case this was related (it isn’t). The time would be overwritten within seconds each time.
What appears to have resolved it (for now) is making an adjustment on an unrelated slot in ZwaveJS. After changing the status of a different slot I can now change any start time and they stick.
I can’t see anything in the standard logs but will turn on debug if this happens again and raise in GitHub.
I’m seeing it too and I haven’t figured out what the cause of it is. It had started to happen on a couple (not all) of my properties before I added the recent calendar caching bits too so I’m confident it wasn’t that.
What’s weird is that some properties are having no problem at all, and others are having this semi-consistently 