v1.2.0

Codes for date based code generators can now optionally be auto-regenerated if the reservation is at least 1 day future and either the start or end day changes, changes to check-in/check-out times will not affect the code generator.

This defaults to being turned on for new configurations and must be explicitly enabled for upgraded configurations.

💣 NOTE: that a reservation that changes to the start day the current day or older will not regenerate the code.

⚡ Enhancments ⚡

• Feat: Date based code update @tykeal (#225)

🔧 Maintenance 🔧

• Chore: Update pre-commit hooks to latest versions @tykeal (#224)

Links

• Submit bugs/feature requests

v1.1.2

🐛 Bug Fixes 🐛

• Fix!: Cleanup mypy errors @tykeal (#209)
• Fix: Await the async_forward_entry_setups call by @tykeal (#213)

🔧 Maintenance 🔧

• Fix!: Cleanup mypy errors @tykeal (#209)
• Chore: Update pre-commit hooks @tykeal (#212)

Links

• Submit bugs/feature requests

v1.1.1

🐛 Bug Fixes 🐛

• Fix: Correct bad phone number squeeze logic @tykeal (#208)

Links

• Submit bugs/feature requests

v1.1.0

This version now supports short events. That is events for maintenance and other shorter events. The best way to use this is to create a custom calendar, such as a Google Calendar, and put your events there. If you do not configure a door code in the description (such as with Last 4 Digits: NNNN) then the fall back of start day / end day will be used.

⚡ Enhancments ⚡

• Feat: Add support for short events @tykeal (#203)

🔧 Maintenance 🔧

• Chore: Update pre-commit hooks @tykeal (#202)
• Docs: Update documentation for short events @tykeal (#204)
• Chore: Update requirements.txt for x-wr-timezone @tykeal (#205)
• Chore: Cleanup migrations of schemas @tykeal (#206)

🎓 Code Quality 🎓

• Chore: Update pre-commit hooks @tykeal (#202)

Links

• Submit bugs/feature requests

v1.0.2

⚡ Enhancments ⚡

• Feat: Add French translations @tykeal (#201)

🔧 Maintenance 🔧

• Chore: Update pre-commit hooks @tykeal (#180)
• Chore: Update pre-commit to latest frozen versions @tykeal (#185)
• Chore: GHA and pre-commit updates @tykeal (#190)
• Docs: Add FAQ @tykeal (#192)
• Docs: Docs cleanup @tykeal (#193)
• Chore: Actions updates @tykeal (#194)
• Chore: Add SPDX headers to all files @tykeal (#196)
• Chore: Update pre-commit hooks to latest versions @tykeal (#199)

🎓 Code Quality 🎓

• CI: Remove uneeded hooks and add new hooks @tykeal (#186)
• Chore: GHA and pre-commit updates @tykeal (#190)
• CI: Re-add prettier @tykeal (#191)
• Chore: Actions updates @tykeal (#194)
• Chore: Add SPDX headers to all files @tykeal (#196)
• Chore: Update pre-commit hooks to latest versions @tykeal (#199)

Links

• Submit bugs/feature requests

v1.0.1

🎆 Major Release 🎆

This is the 1.0 release! Major changes include the following

• No more automations in use! All management of slots is done by the integration
• Reloads of the integration will always cleanly work now
• KeyMaster slot management will now properly follow changes to the start and end dates of events. Start / stop times can still be overridden and even if the any of the dates change the override will not be lost
• The weird issue where events would sometimes change which slot they were assigned to should now be completely fixed
• The Mapping Sensor, which never really worked properly in the UI, has been removed.
• During a restart of the integration or Home Assistant itself, lock management will not be performed until all data is fully ready. This means that if the calendar is not accessible for some reason during startup that codes will not be cleared or added to the KeyMaster configuration until the calendar is successfully loaded. KeyMaster itself will continue to operate on already configured slots per normal, this is strictly about adding, removing, or modifying data to KeyMaster slots.
• Calendar and Event entities are Unavailable until all data is available. This avoids issues with calendar entities not being 'On' or 'Off' when they should be which could mess up automations that you may have developed to use the entity. This holds for the event entities as well where they could previously load up and provide incorrect data while the rest of the integration was still starting up.
• Requires Home Assistant 2023.9 or greater
• Requires HACS 1.32.1 or greater

💣 Upgrade concerns 💣

• During an upgrade operation you will receive information about events that cannot be found. These can be safely ignored.
• Upgrading will leave behind stale entities that we are unable to clean-up ourselves. These entities can all be found in the Entities list and searching for 'Rental Control' (you may need to clear hidden. You will not be able to clean all of these up without an additional restart of Home Assistant after the first one needed for the upgrade.
• For the cleanest upgrade:
  • remove all Rental Control integration definitions first
  • Upgrade Rental Control
  • Restart Home Assistant
  • Redefine all Rental Control integrations
• Please note that the Rental Control assigning of data to KeyMaster slots is a bit slower than in previous versions. This is a by product of how this is now being managed. Rest assured that events will get mapped in, it just may take longer than expected when first adding a Rental Control integration

⚡ Enhancments ⚡

• Feat: Remove use of frontend automations @tykeal (#173)

🐛 Bug Fixes 🐛

• Fix: Handle tracking only installations @tykeal (#174)

🔧 Maintenance 🔧

• Chore: Update pre-commit hooks @tykeal (#171)

Links

• Submit bugs/feature requests

v1.0.0

🎆 Major Release 🎆

This is the 1.0 release! Major changes include the following

• No more automations in use! All management of slots is done by the integration
• Reloads of the integration will always cleanly work now
• KeyMaster slot management will now properly follow changes to the start and end dates of events. Start / stop times can still be overridden and even if the any of the dates change the override will not be lost
• The weird issue where events would sometimes change which slot they were assigned to should now be completely fixed
• The Mapping Sensor, which never really worked properly in the UI, has been removed.
• During a restart of the integration or Home Assistant itself, lock management will not be performed until all data is fully ready. This means that if the calendar is not accessible for some reason during startup that codes will not be cleared or added to the KeyMaster configuration until the calendar is successfully loaded. KeyMaster itself will continue to operate on already configured slots per normal, this is strictly about adding, removing, or modifying data to KeyMaster slots.
• Calendar and Event entities are Unavailable until all data is available. This avoids issues with calendar entities not being 'On' or 'Off' when they should be which could mess up automations that you may have developed to use the entity. This holds for the event entities as well where they could previously load up and provide incorrect data while the rest of the integration was still starting up.
• Requires Home Assistant 2023.9 or greater
• Requires HACS 1.32.1 or greater

💣 Upgrade concerns 💣

• During an upgrade operation you will receive information about events that cannot be found. These can be safely ignored.
• Upgrading will leave behind stale entities that we are unable to clean-up ourselves. These entities can all be found in the Entities list and searching for 'Rental Control' (you may need to clear hidden. You will not be able to clean all of these up without an additional restart of Home Assistant after the first one needed for the upgrade.
• For the cleanest upgrade:
  • remove all Rental Control integration definitions first
  • Upgrade Rental Control
  • Restart Home Assistant
  • Redefine all Rental Control integrations
• Please note that the Rental Control assigning of data to KeyMaster slots is a bit slower than in previous versions. This is a by product of how this is now being managed. Rest assured that events will get mapped in, it just may take longer than expected when first adding a Rental Control integration

⚡ Enhancments ⚡

• Feat: Remove use of frontend automations @tykeal (#173)

🔧 Maintenance 🔧

• Chore: Update pre-commit hooks @tykeal (#171)

Links

• Submit bugs/feature requests

v0.9.2

🐛 Bug Fixes 🐛

• Fix: Use entry_id in device setup @tykeal (#170)

🔧 Maintenance 🔧

• update pre commit @tykeal (#166)

🎓 Code Quality 🎓

• CI: Workflow updates @tykeal (#167)

Links

• Submit bugs/feature requests

v0.9.1

🐛 Bug Fixes 🐛

• Fix: Stringify rental_control_name in automations @tykeal (#165)

Links

• Submit bugs/feature requests

v0.9.0

⚡ Enhancments ⚡

• Feat: Parse Smoobu calendars @tykeal (#161)

Last 4 digits of phone numbers will be more properly parsed even if there is no description line expressly calling out the last 4. As long as there is a 'Phone' or 'Phone Number' line in the description with a minimum of 4 digits they will be extracted and used.

🔧 Maintenance 🔧

• Chore: Update pre-commit hooks @tykeal (#158)
• Chore: Update pre-commit hooks @tykeal (#160)

Links

• Submit bugs/feature requests