v0.5.6

⚡ Enhancments ⚡

• Feat: Guest identifiers and lock codes @tykeal (#83)

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

• Submit bugs/feature requests