Releases: tykeal/homeassistant-rental-control
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.
🐛 Bug Fixes 🐛
Links
Contributors
Assets 3
v0.5.6
tykeal
Andrew Grimberg
⚡ Enhancments ⚡
Event sensors have learned how to report the following new information:
- slot name (aka event identifier, which for most systems will be a real name, AirBnB events will be the reservation code)
- slot code (aka the code for the lock)
Slot codes are generated in one of three ways:
- A check-in/out date based 4 digit code using the check-in day combined with the check-out day (default and fallback in the case another generator fails to produce a code)
- A random 4 digit code based on the event description
- The last 4 digits of the phone number. This only works properly if the event description contains 'Last 4 Digits' followed quickly by a 4 digit number as is the case with AirBnB and AirBnB calendars imported into Guesty . This is the most stable, but only works if the event descriptions have the needed data. The previous two methods can have the codes change if the event makes changes to length or to the description. Tripadvisor and VRBO do not appear to provide this information. I do not know if VRBO calendars imported into Guesty do.
All events will get a code associated with it. In the case that the criteria to create the code are not fulfilled, then the check-in/out date based
method will be used as a fallback.
The slot name will be null if the event is either 'Blocked' or 'Not available'.
Links
Contributors
Assets 3
v0.5.5
tykeal
Andrew Grimberg
⚡ Enhancments ⚡
Calendar refresh rate is now tunable in increments of 1 minute from 0 - 1440.
0 = refresh as often as possible
1440 = refresh once a day
Default is every 2 minutes
🔧 Maintenance 🔧
Links
Contributors
Assets 3
v0.5.4
v0.5.3
v0.5.2
v0.5.1
Initial release
⚡ Enhancments ⚡
- Docs: Add pre-commit.ci badge @tykeal (#2)
- Feat: Add configuration for checkin/out times @tykeal (#6)
- Feat: Set default times @tykeal (#9)
- Feat: Options flow @tykeal (#11)
- Docs: Add statement about Keymaster dependency @tykeal (#36)
- more calendars @tykeal (#44)
- extra options @tykeal (#48)
- Docs: Improve documentation @tykeal (#59)
- Feat: Teach calendars timezones @tykeal (#56)
- changelog @tykeal (#64)
🐛 Bug Fixes 🐛
- Fix: Correct the displayed integration name @tykeal (#4)
- Fix: Correct bad constant import @tykeal (#7)
- Fix: Required to Optional @tykeal (#8)
- Fix: Convert device_state_attributes to extra_ @tykeal (#24)
- Fix: Correct problems when editing with no lock @tykeal (#29)
- Fix: Correct fetch limit @tykeal (#33)
- Fix: Make ICS URL less strict on AirBnB @tykeal (#41)
- Fix: Make prepend work for no reservation @tykeal (#54)
- Fix: Correct bad URLs in docs @tykeal (#63)