📷

Voice - Get ToDo Entries - Local Assist Blueprint by TheFes

Image
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:

Usage

All sentences need to match the format defined in the trigger sentences. By default the following sentence is configured:

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

Trigger sentence syntax

All parts between square brackets are optional, the sentence will be recognized with and without those parts. A pipe | means or. All parts betwee round brackets are mandatory, but also here the pipe means or.
The {list_name} part refers to the moment you want the todo entries for. This needs to match to the actual name of the entity, aliases are not supported.

Examples

* What's on the shopping list
* What is on the list named Blueprints to create
* What is on the Blueprints to create list
83
Stars
4.4K
Views
1.2K
Imports

Import to Home Assistant

Click to import this blueprint directly into your Home Assistant instance.

Configuration

Requires 3 inputs to configure

Entity

Source Code

View on GitHub

Related Blueprints

More camera integration automations you might like

View all
📷
Camera Integration
medium
5 inputs

Send alerts using Telegram

Image

Telegram Alert

This replacement of the alert integration which sends alerts through Telegram. The alert title and all messages support templates, but you can use plain text as well.

Repeat settings

The repeat setting either needs to be provided as a number or a list of numbers. In case a list of numbers is provided, the last value will be used in case there are more repeats needed compared to items in the list Example single number:
15
Example list of numbers:
- 15
- 30
- 60
832.8K1.1K
📷
Camera Integration
medium
5 inputs

Voice - Calendar Entries - Local Assist Blueprint

Image 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:

Usage

All sentences need to match the format defined in the trigger sentences. By default the following sentences are configured:
  • (what's|what is) on the (calendar|agenda) [[for] {phrase}]
  • (what's|what is) on {phrase}['s|s] (calendar|agenda)

Trigger sentence syntax

All parts between square brackets are optional, the sentence will be recognized with and without those parts. A pipe | means or. All parts betwee round brackets are mandatory, but also here the pipe means or. The {phrase} part refers to the moment you want the calendar entries for. This can be today, tomorrow, day after tomorrow for a day related to the current day. It can also be a weekday, like Monday or Thursday. In that case the next weekday will be used. You can also use night, morning, afternoon or evening.

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
entity
832.4K4.4K
📷
Camera Integration
medium
2 inputs

Voice - Calendar entries - Full LLM script

Image

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:

Fetch calendar events from my calendar. In case the data for the weekend is requested, this means Saturday and Sunday

Usage

You can request for the calendar entries in any way yuou can think of, using any language. Unless set otherwise in the LLM configuration, the response will be in the same language as the command. You can refer to a single day, multiple days (e.g. next weekend) a part of the day (e.g. next morning) or one or more hours (e.g. from 5 to 9). You can even ask for specific events, for example, will there be a doctor's appointment in the next 2 weeks.

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?
entity
833.1K1.2K
📷
Camera Integration
medium
3 inputs

Voice - Send Reminder - Automation

Image

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

Nothing from your side is needed, the automation will check every minute if there are todo items due, and perform the actions if this is the case.
836.4K4.3K
📷
Camera Integration
simple
1 inputs

Voice - Get ToDo entries - Full LLM script

Image

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:

Fetch todo items from my todo lists. Note that the shopping list is also considered a todo list. Ignore items marked as completed, unless the uses specifically requests them.

Usage

You can request for the todo items in any way you can think of, using any language. Unless set otherwise in the LLM configuration, the response will be in the same language as the command.

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)
833.4K790