Automation Notes

Automation Notes

Checkout Task Alerts

Checkout task assignment alerts are exposed per property with the Checkout Task Alert sensor. The sensor turns on when a checkout-day task assignment is pending, unaccepted, rejected, cancelled, or unassigned. Tasks with unknown assignment status are listed in attributes but do not trigger the alert.

Task diagnostics expose detail fetch counts, detail fetch errors, and sampled response keys so field-shape issues can be debugged without publishing raw task payloads.

The integration reads Hospitable's task progress_status and task_assignment.status fields. Assignment alerts trigger for pending, unaccepted, rejected, cancelled, or unassigned checkout tasks.

If the Hospitable task endpoint is unavailable for the token, the task sensors still load as 0/off and expose the API error in the hospitable_task_error attribute. Task list requests intentionally avoid unsupported per-task includes.

For most task-alert automations, use the Task Attention Blueprint instead of hand-writing each automation.

Message Current Guest

The integration provides this Home Assistant service/action:

hospitable_api.post_guest_message

You can pass a Hospitable guest sensor with a reservation_uuid attribute:

alias: Message current guest when door unlocks
triggers:
  - trigger: state
    entity_id: lock.front_door
    to: unlocked
actions:
  - action: hospitable_api.post_guest_message
    data:
      entity_id: sensor.hospitable_cabin_current_guest
      message: "The front door was unlocked. Let us know if you need anything."

You can also pass reservation_uuid directly. Provide either entity_id or reservation_uuid, not both:

actions:
  - action: hospitable_api.post_guest_message
    data:
      reservation_uuid: "your-reservation-uuid"
      message: "Your custom message"