Task Attention Blueprint

Task Attention Blueprint

The repository includes a Home Assistant automation blueprint for checkout task assignment alerts:

blueprints/automation/hospitableIntegration/checkout_task_attention.yaml

Import URL:

https://raw.githubusercontent.com/peluke/hospitableIntegration/main/blueprints/automation/hospitableIntegration/checkout_task_attention.yaml

HACS installs the custom integration. Home Assistant blueprints are imported separately from the blueprint URL above.

Use one automation instance per property. This keeps each house tied to its own Checkout Task Alert sensor and notification target.

What It Does

• Watches one Hospitable Checkout Task Alert sensor.
• Runs when the sensor state becomes on.
• Also checks at Home Assistant startup, so an existing alert is not missed after a restart.
• Runs your chosen Home Assistant notification, script, or other actions.

The Checkout Task Alert sensor turns on when at least one checkout-day task has an assignment status that needs attention, including:

• pending
• unaccepted
• not accepted
• rejected
• cancelled
• canceled
• unassigned

Accepted tasks do not trigger the alert.

Blueprint Inputs

• Checkout task alert sensor: the Hospitable Checkout Task Alert sensor for one property.
• Attention actions: the notification, message, script, or other actions to run.

Example Attention Action

Use the variables exposed by the blueprint in any action you configure:

action: notify.mobile_app_your_phone
data:
  title: "{{ task_attention_title }}"
  message: "{{ task_attention_message }}"

Available variables include:

• task_attention_title
• task_attention_message
• alert_count
• alert_tasks
• checkout_task_alert_sensor

Multi-Property Setup

Create one automation from the blueprint for each property:

Casa Manzanita -> sensor.casa_manzanita_checkout_task_alert
House 2        -> sensor.house_2_checkout_task_alert
House 3        -> sensor.house_3_checkout_task_alert
House 4        -> sensor.house_4_checkout_task_alert

Each automation can notify different phones, dashboards, or escalation scripts. That is usually cleaner than one large automation that tries to route all four houses in templates.

Notes

The alert details come from the sensor's alerts attribute. The integration uses Hospitable task detail fields including task_assignment.status and task_assignment.updated_at, so the action message can show who needs to accept the task and when the assignment was last updated.