From ea9ff1f6fa1c7795a9c1d32e4c0fc49d7b28ffec Mon Sep 17 00:00:00 2001 From: John Taseff Date: Tue, 5 Mar 2024 03:31:49 -0600 Subject: [PATCH] Clarify Calendar and To-Do building block pages (#31742) * Clarify Calendar building block page * Add examples of To-do integrations to actually use building block * re-clarify calendar triggers earlier commit cleaned up a bit, but realized this paragraph was in a weird spot, moving it where it makes more sense --- source/_integrations/calendar.markdown | 11 ++++++----- source/_integrations/todo.markdown | 2 ++ 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/source/_integrations/calendar.markdown b/source/_integrations/calendar.markdown index dc539ba1af0..231c3f6c5e1 100644 --- a/source/_integrations/calendar.markdown +++ b/source/_integrations/calendar.markdown @@ -4,7 +4,8 @@ description: Instructions on how to integrate calendars within Home Assistant. ha_release: 0.33 ha_domain: calendar ha_quality_scale: internal -ha_category: [] +ha_category: + - Calendar ha_codeowners: - '@home-assistant/core' ha_integration_type: entity @@ -16,13 +17,10 @@ dashboard and can be used with automations. This page does not provide instructions on how to create calendar entities. Please see the ["Calendar" category](/integrations/#calendar) on the -integrations page to find integration offering calendar entities. +integrations page to find integrations offering calendar entities. For example, [Local Calendar](/integrations/local_calendar/) is a fully local integration to create calendars and events within your Home Assistant instance or other integrations work with other services providing calendar data. {% include integrations/building_block_integration.md %} -A calendar {% term entity %} has a {% term state %} and attributes representing the next event (only). -A calendar {% term trigger %} is much more flexible, has fewer limitations, and is -recommended for automations instead of using the entity state. ## Viewing and managing calendars @@ -43,6 +41,9 @@ event's start or end. Review the [Automating Home Assistant](/getting-started/au getting started guide on automations or the [Automation](/docs/automation/) documentation for full details. +Calendar {% term triggers %} are the best way to automate based on calendar events. +A calendar {% term entity %} can also be used to automate based on its state, but these are limited and attributes only represent the next event. + {% my automations badge %} ![Screenshot Trigger](/images/integrations/calendar/trigger.png) diff --git a/source/_integrations/todo.markdown b/source/_integrations/todo.markdown index 1351684b099..f037f008d34 100644 --- a/source/_integrations/todo.markdown +++ b/source/_integrations/todo.markdown @@ -17,6 +17,8 @@ dashboard for tracking items and whether or not they have been completed. {% include integrations/building_block_integration.md %} +For example, [Local To-do](/integrations/local_todo/) is a fully local integration to create to-do lists and tasks within your Home Assistant instance, [Shopping list](/integrations/shopping_list) specifically for shopping that can be added to with Assist, or other integrations work with online services providing to-do list data. + ## Viewing and managing to-do lists Each to-do list is represented as its own entity in Home Assistant and can be