Telegram Alert

Repeat settings

15

- 15
- 30
- 60

More detailed information can be found here

Request calendar entries fully local

Blueprint setup

Required

• Set one ore more calendar entries to be used

Optional

• Add triggers or change the existing ones
• Change or translate the settings for the phrases which will be taken from the trigger
• Change or translate the settings for the response given by Assist

These translations are already available:

• Dutch
• German

Usage

• (what's|what is) on the (calendar|agenda) [[for] {phrase}]
• (what's|what is) on {phrase}['s|s] (calendar|agenda)

Trigger sentence syntax

Examples without phrase (will return the current day)

* What's on the agenda
* What is on the calendar

Examples with a phrase (will return the requested moment)

* What's on tomorrow's calendar
* What is on the calendar for Thursday

Request the calendar entries by use of an LLM

Blueprint setup

Required

• Set one or more calendar entries for which you want to get the eventa

Optional

• Adjust the prompts for each field used in the script. The descriptions guide the LLM to provide the correct input

Note:

• Give the script a clear description. This will be used by the LLM to understand it should use this script for weather forecasts.
• Make sure to expose the script to Assist after the script has been saved

Example for script description:

Usage

Examples

What's on the calendar tomorrow?
Do I have something on the calendar this evening?
Am I busy tonight at 9?
Do I have a doctor's appointment next week?

Automation to send the reminders set by voice

Blueprint setup

Required

• Set the LLM conversation agent which will be used to process the recipients to the right names
• Set the ToDo list which is used to store the reminders
• Enter the recipient data, it should contain at least the name and description and one notifier. The notifier should be an action to send the notification, it can be any action you want, which supports the message field in the data. So a persistent notification, tts message, notify message, etc. You can add addtional action data as normal, for example a title. It is also possible to use a jinja template as condition to determine if the reminder should be sent, however, if all notifiers have a condition, and it returns false for all, the reminder will not be removed from the list. Only when at least one action is performed, the item will be removed. Lastly it is possible to add a prefix for the message, so for example you can prefix the a TTS announcement with This is a reminder for: The default setting in this selector acts as an example, make sure to adjust it to your own system.

Optional

• Adjust the trigger to check for the reminders, by default it will check every minute
• Adjust the prompt used to get the right names

Usage

More detailed information can be found here

Request calendar entries fully local

Blueprint setup

Required

• Set a todo entity to be used as default entity. This entity can be set by name in the trigger to avoid the need to add "list" after the name. By default the trigger is configered for this to be the shopping list. If you want to use another list you need to change the description in the trigger sentence.

Optional

• Add triggers or change the existing ones
• Change or translate the settings for the response given by Assist

These translations are already available:

• Dutch

Usage

• (what's|what is) on the (shopping list|list named {list_name}|{list name} list)

Trigger sentence syntax

Examples

* What's on the shopping list
* What is on the list named Blueprints to create
* What is on the Blueprints to create list

Request the todo entries by use of an LLM

Blueprint setup

Optional

• Adjust the prompts for each field used in the script. The descriptions guide the LLM to provide the correct input

Note:

• Give the script a clear description. This will be used by the LLM to understand it should use this script for the todo list items.
• Make sure to expose the script to Assist after the script has been saved

Example for script description:

Usage

Examples

What's on the shopping list?
Are there carrots on the shopping list?
Which todo items are planned for today? (only in case the todo items have due dates)

More detailed information can be found here

Request the weather forecast fully locally

Blueprint setup

Required

• Set a weather entity to use for the forecasts

Optional

• Add triggers or change the existing ones
• Change or translate the settings for the phrases which will be taken from the trigger
• Change or translate the settings for the response given by Assist

These translations are already available:

• Dutch
• German: There are multiple variants available, just mix and match whatever fits your needs
• Variant 1
• Variant 2

Usage

• what('s| is) [this|next] ({phrase}[']s|the [current]|this) weather [forecast]
• what('s| is) the weather [forecast] [for] [this|next] ({phrase}|day)
• what('ll| will) the weather [forecast] be [like] [[for] [[the] coming|this] ({pharse}|day)]

Trigger sentence syntax

Examples without phrase (will return the current day)

* What's the weather
* What will the weather be like

Examples with a phrase (will return the requested moment)

* What's the weather tomorrow
* What is the weather forecast for next Thursday
* What will the weather be like this evening

Request the weather forecast by use of an LLM

Blueprint setup

Required

• Set a weather entity to use for the forecasts

Optional

• Adjust the prompts for each field used in the script. The descriptions guide the LLM to provide the correct input

Note:

• Give the script a clear description. This will be used by the LLM to understand it should use this script for weather forecasts.
• Make sure to expose the script to Assist after the script has been saved

Example for script description:

Usage

Examples

Give me the weather forecast for this evening
Do I need to apply sunscreen if I go out tomorrow morning
Will it rain at 9 this evening
What's the weather for this weekend

Frigate Notifications

Software Version Requirements

• Minimum Home Assistant Version: 2024.11
• Minimum Frigate Version: 0.14.0
• Minimum Frigate Integration Version: 5.7.0
  • Note: "Enable the unauthenticated notification event proxy" must be ticked during setup
• An MQTT broker connected to Home Assistant and Frigate.
• Minimum iOS Version: 15.0

Required Configuration Options:

• Frigate Cameras
• Mobile Device (Running HA Companion App)

Features:

• Easily select the camera entities or mobile device using a drop-down menu.
• Configure multiple cameras in one automation.

Support

Frigate Notifications

Software Version Requirements

• Minimum Home Assistant Version: 2024.10
• Minimum Frigate Version: 0.14.0
• Minimum Frigate Integration Version: 5.7.0
  • Note: "Enable the unauthenticated notification event proxy" must be ticked during setup
• An MQTT broker connected to Home Assistant and Frigate.
• Minimum iOS Version: 15.0

Required Configuration Options:

• Frigate Cameras
• Mobile Device (Running HA Companion App)

Features:

• Easily select the camera entities or mobile device using a drop-down menu.
• Configure multiple cameras in one automation.

Support