Rental Control for Home Assistant (Marketplace integration)

Installs: 218 sharing analytics
GitHub stars: 82
Connection: Uses the vendor's cloud
Upkeep: Updated in the last 6 months
Version: v3.9.0, October 25, 2026
Category: Productivity and information, Calendars and to-dos
Kind: Marketplace integration
Needs: Needs the Marketplace (HACS on 2026.10 and older)
Domain: rental_control
Source: github.com/tykeal/homeassistant-rental-control
Issues: Report an issue

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation.

About

Rental Control is an integration that turns rental booking calendars into calendars, sensors and switches for managing a property. It reads ICS calendars from any HTTPS source and refreshes them at a set interval, with a prefix option to tell several rentals apart. Check-in and check-out times can be applied to all-day entries, and each calendar can use its own timezone. A check-in sensor tracks guest occupancy through four states, moving automatically by time, by door code use with Keymaster, or by a manual checkout action. Event sensors carry details taken from the booking description, such as guest count, email and reservation URL. With a Keymaster lock configured, the integration manages door codes and adds switches for lock monitoring and early checkout expiry. It is set up in the UI and depends on the vendor's cloud.

Automatic summary of the README and code of tykeal/homeassistant-rental-control. Something wrong, or are you the maintainer and want your own text here? Get in touch

Supports

Uses the vendor's cloud Needs an internet connection and an account with the vendor.
From the Marketplace Installed through the Marketplace, formerly HACS.
Actively maintained Its author released or pushed a change in the last six months.

Provides

Switches
Sensors
Calendars

Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

Connect

Calendar contains only confirmed bookings (never blocked dates)Enable only if this calendar never publishes blocked or unavailable dates. Booking.com no longer identifies guests in its feed, so this is required for Booking.com calendars that export booked dates only. Enabling this on a calendar that does publish blocked dates will issue door codes for those blocks.
Default Check-in time
Default Check-out time
Cleaning Window (hours)Hours to keep checkout status before returning to no reservation (0.5–48)
Door code generator
Door code length (>= 4 and an even number)
Show reservations as all-day eventsDisplays each reservation as a single all-day block. Guest arrival and departure times are hidden from the calendar.
Maximum number of days into the future to fetch
Prefix for all events (useful if linking more than one rental)
Ignore events that are not standard reservations
Keymaster configuration to manage
Number of event sensors to create
Calendar name
Refresh calendar in minutes. 0 - 1440
Starting lock slot for management

After setup

Calendar contains only confirmed bookings (never blocked dates)Enable only if this calendar never publishes blocked or unavailable dates. Booking.com no longer identifies guests in its feed, so this is required for Booking.com calendars that export booked dates only. Enabling this on a calendar that does publish blocked dates will issue door codes for those blocks.
Default Check-in time
Default Check-out time
Cleaning Window (hours)Hours to keep checkout status before returning to no reservation (0.5–48)
Door code generator
Door code length (>= 4 and an even number)
Show reservations as all-day eventsDisplays each reservation as a single all-day block. Guest arrival and departure times are hidden from the calendar.
Maximum number of days into the future to fetch
Prefix for all events (useful if linking more than one rental)
Ignore events that are not standard reservations
Keymaster configuration to manage
Number of event sensors to create
Calendar name
Refresh calendar in minutes. 0 - 1440
Starting lock slot for management

Texts from the code of tykeal/homeassistant-rental-control.

Entities

SensorsCheck-in
SwitchesKeymaster Monitoring, Early Checkout Expiry

Actions

CheckoutManually check out the current guest.Fields: Force
Set stateForce the check-in sensor into any valid state. Debug tool — bypasses all guard conditions and does not fire the integration's custom check-in/checkout events.Fields: State
Clear orphaned codesRelease orphaned shared code allocations that are proven absent from managed locks.Fields: Dry run, Force reissued holds
Force reissue codeForce one reservation or managed lock slot to receive a new code through the shared registry.Fields: Entity, Lock name, Slot, Force, Dry run
Set slot exclusionExclude one permanently unreadable managed lock slot from the door code issuance gate, or restore it. An excluded slot is still reconciled and still counts as evidence that a code may be programmed, so a code the integration cannot see may remain on the lock; verify the slot physically before excluding it. The exclusion clears itself as soon as the slot becomes readable again or leaves the managed range, and saving the entry's options discards it.Fields: Entity, Lock name, Slot, Excluded, Reason, Dry run

Troubleshooting

DiagnosticsDownloads a diagnostics file to attach to a bug report.

From the README

Rental Control is a Home Assistant integration that handles custom calendars and sensors for managing rental properties.
Ingests ICS calendars from any HTTPS source that serves a text/calendar file
Configurable refresh rate from as often as possible to once per day (default every 2 minutes)
Define checkin/checkout times that apply to all-day calendar entries
Ability to ignore 'Blocked' and 'Not available' events
Ability to treat a calendar as confirmed bookings only, for feeds like Booking.com that no longer name their guests
Calendars can have their own timezone definition that is separate from the Home Assistant instance itself. This is useful for managing properties that are in a different timezone from where Home…
Events can have a custom prefix to help differentiate between entities if you track more than one calendar in an instance
Submitting a configuration change forces a calendar refresh
Calendar fetch failure resilience: if a fetch fails the integration serves the last good data; if a fetch returns an empty calendar when events existed before, it tolerates up to 2 consecutive empty…

From the README of tykeal/homeassistant-rental-control, Apache License 2.0. Shortened.