Releases: tykeal/homeassistant-rental-control
v0.8.1
v0.8.0
tykeal
Andrew Grimberg
⚡ Enhancments ⚡
- Feat: Better ETA attributes @tykeal (#133)
- Feat: larger pins @tykeal (#134)
- Feat: Support more generic calendar entries @tykeal (#137)
🐛 Bug Fixes 🐛
🔧 Maintenance 🔧
- Chore: Update pre-commit hooks @tykeal (#110)
- Chore: Autoupdate pre-commit hooks @tykeal (#112)
- Chore: Update pre-commit hooks @tykeal (#114)
- Chore: Update pre-commit hooks @tykeal (#116)
- Chore: Update pre-commit hooks @tykeal (#118)
- Chore: Upgrade pre-commit hooks @tykeal (#120)
- Chore: Update pre-commit hooks @tykeal (#123)
- Chore: Update pre-commit hooks @tykeal (#125)
- Chore: Update pre-commit hooks @tykeal (#131)
- Refactor: Add mypy configuration @tykeal (#132)
- Feat: larger pins @tykeal (#134)
- Refactor: Cleanup random code generation @tykeal (#135)
🎓 Code Quality 🎓
Links
Contributors
Assets 3
v0.7.5
tykeal
Andrew Grimberg
🎆 Major Feature 🎆
This release brings in the long awaited ability to manage Keymaster slots! A few things to say about this:
- If you are not planning on doing key slot management via Keymaster make sure that you have selected the None lock during configuration as otherwise this integration will have some serious issues
- Modification of the calendar events for checkin/out times are now tracked for Keymaster based slots. Date changes are not tracked. Additionally, there is a known issue where an update to the dates coming in via the calendar is not properly replicated back to the lock slots. Please be aware of this! That being said, the lock should actually self-correct during the midnight roll-over of events though there will be a brief window in which the slot will be resetting and then setting the code again. (Issue #105)
- Overriding the generated slot code is supported. This is particularly useful if the generated code is in conflict with another code already in the door
- Do not try using the slot management functionality with a timezone that is not the timezone for your HA instance. This is a known issue (#106). Non-HA timezones are properly supported for non-managed slots. This comes with the downside of not having a way to override checkin/out times for a given event.
Please read the integration README or info files for more information on any extra setup needed.
💣 Upgrade concerns 💣
Please be aware that if you are planning on using the new Keymaster management functionality that you must have Keymaster fully functioning correctly for this integration to also work with it. This includes making sure the packages directory is correctly setup and included in your HA configuration.
Upon upgrade, if it is detected that you are trying to use Keymaster functionality you will be prompted to reconfigure your integration to properly update the configuration with the generated automations.
⚡ Enhancments ⚡
🐛 Bug Fixes 🐛
- Feat: Add support for Booking.com -- Resolves an issue with VRBO that has existed since release v0.7.1 @tykeal (#109)
🔧 Maintenance 🔧
- Refactor: Code cleanup - rename of classes @tykeal (#98)
- Chore: Update pre-commit hooks @tykeal (#103)
🎓 Code Quality 🎓
Links
Contributors
Assets 3
v0.7.5-beta.1
tykeal
Andrew Grimberg
🎆 Major Feature 🎆
This release brings in the long awaited ability to manage Keymaster slots! A few things to say about this:
- If you are not planning on doing key slot management via Keymaster make sure that you have selected the None lock during configuration as otherwise this integration will have some serious issues
- Modification of the calendar events for checkin/out times are now tracked for Keymaster based slots. Date changes are not tracked. Additionally, there is a known issue where an update to the dates coming in via the calendar is not properly replicated back to the lock slots. Please be aware of this! That being said, the lock should actually self-correct during the midnight roll-over of events though there will be a brief window in which the slot will be resetting and then setting the code again. (Issue #105)
- Overriding the generated slot code is supported. This is particularly useful if the generated code is in conflict with another code already in the door
- Do not try using the slot management functionality with a timezone that is not the timezone for your HA instance. This is a known issue (#106). Non-HA timezones are properly supported for non-managed slots. This comes with the downside of not having a way to override checkin/out times for a given event.
Please read the integration README or info files for more information on any extra setup needed.
💣 Upgrade concerns 💣
Please be aware that if you are planning on using the new Keymaster management functionality that you must have Keymaster fully functioning correctly for this integration to also work with it. This includes making sure the packages directory is correctly setup and included in your HA configuration.
Upon upgrade, if it is detected that you are trying to use Keymaster functionality you will be prompted to reconfigure your integration to properly update the configuration with the generated automations.
⚡ Enhancments ⚡
🔧 Maintenance 🔧
- Refactor: Code cleanup - rename of classes @tykeal (#98)
- Chore: Update pre-commit hooks @tykeal (#103)
🎓 Code Quality 🎓
Links
Contributors
Assets 3
v0.7.5-beta
tykeal
Andrew Grimberg
🎆 Major Feature 🎆
This release brings in the long awaited ability to manage Keymaster slots! A few things to say about this:
- If you are not planning on doing key slot management via Keymaster make sure that you have selected the None lock during configuration as otherwise this integration will have some serious issues
- Modification of the calendar events for checkin/out times are now tracked for Keymaster based slots. Date changes are not tracked. Additionally, there is a known issue where an update to the dates coming in via the calendar is not properly replicated back to the lock slots. Please be aware of this! That being said, the lock should actually self-correct during the midnight roll-over of events though there will be a brief window in which the slot will be resetting and then setting the code again. (Issue #105)
- Overriding the generated slot code is supported. This is particularly useful if the generated code is in conflict with another code already in the door
- Do not try using the slot management functionality with a timezone that is not the timezone for your HA instance. This is a known issue (#106). Non-HA timezones are properly supported for non-managed slots. This comes with the downside of not having a way to override checkin/out times for a given event.
Please read the integration README or info files for more information on any extra setup needed.
💣 Upgrade concerns 💣
Please be aware that if you are planning on using the new Keymaster management functionality that you must have Keymaster fully functioning correctly for this integration to also work with it. This includes making sure the packages directory is correctly setup and included in your HA configuration.
Upon upgrade, if it is detected that you are trying to use Keymaster functionality you will be prompted to reconfigure your integration to properly update the configuration with the generated automations.
⚡ Enhancments ⚡
🔧 Maintenance 🔧
- Refactor: Code cleanup - rename of classes @tykeal (#98)
- Chore: Update pre-commit hooks @tykeal (#103)
🎓 Code Quality 🎓
Links
Contributors
Assets 3
v0.7.2
v0.7.1
tykeal
Andrew Grimberg
⚡ Enhancments ⚡
We now extract any useful information that we can from the event description and attach it as addition attributes to event sensor.
Attributes that may show up on a given sensor are:
- Last four (last_four) -- the last 4 digits of the phone number of the booking guest (Airbnb provides this, Guesty may provide it)
NOTE: if using the last_four code generator you already had this as slot_code but now it is explicitly available as a separate attribute even if you don't use that code generator.
- Number of guests (number_of_guests) -- the number of guests in the reservation (TripAdvisor provides this)
- Guest email (guest_email) -- the email of the booking guest (Guesty may provide this)
- Phone number (phone_number) -- the phone number of the booking guest (Guesty may provide this)
- Reservation url (reservation_url) -- the URL to the reservation (Airbnb and TripAdvisor provide this)
Links
Contributors
Assets 3
v0.7.0
tykeal
Andrew Grimberg
💥 HA 2022.5 required to upgrade to this version 💥
This version switches to a new calendar data model that is introduced in HA 2022.5. It is not backwards compatible to older versions of HA.
Additionally, if you are utilizing the all_day attribute on the event sensors, this attribute no longer exists as it is not useful for the intended purpose of this integration and it is also now a calculated attribute from the base calendar object.
🔧 Maintenance 🔧
Links
Contributors
Assets 3
v0.6.0
tykeal
Andrew Grimberg
💥 Required update for HA 2022.4 💥
A change in HA 2022.4 breaks the calendar component of Rental Control. This is a required update for installation on HA 2022.4 or greater. It is backwards compatible with previous versions of HA.
This removes the 'Offset Reached' attribute from the calendar object. Please base any automations you have on the state of the calendar object instead.
🐛 Bug Fixes 🐛
- Fix: Do not translate integration title @tykeal (#88)
- Fix: Remove unneeded calendar offset @tykeal (#90)
🔧 Maintenance 🔧
Links
Contributors
Assets 3
v0.5.7
tykeal
Andrew Grimberg
⚡ Enhancments ⚡
The sensors and calendar entities have learned how to be holistically linked to a virtual device. This has had a side effect of changing how the entities are named and work.
All of the entities are now prefixed with 'Rental Control' as part of their name. This was needed due to how entities linked to devices get their default entity names set. Additionally, the sensor entities would change their name to the prefix + summary of any events or prefix + 'No reservation' if there was no reservation in a slot. This no longer happens, again, because of how entity names are handled in this configuration.
Finally, the entities are all marked as diagnostic entities. This means that by default the entities will not be added to auto-generated Lovelace dashboards. You may get them on a managed dashboard, either by building out the entity display yourself, or by going to the configuration option for the integration and select the device. This page will show you all of the entities with a link to add to Lovelace, this will allow you add the entity box to managed dashboard.