Simple Blueprints

Easy to configure blueprints with 1-5 inputs

27 blueprints found

๐ŸŽ›๏ธ
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
82.5K1.3K2.7K
by home-assistanthome-assistant/core
๐ŸŽ›๏ธ
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
5279.6K3.5K
๐ŸŽ›๏ธ
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
2733.0K4.7K
๐Ÿ””
Notifications
simple
2 inputs

device_reset_script - 2023-12-07

This script was invented to be used with my Device Tracker-Monitor-Notifier Blueprint. I released it as a standalone Script Blueprint because I saw an opportunity to add another tool to my toolbox, and possibly to others toolboxes There are other places in my HA config where I need to reset something and now I can use this thing. It asks for the entity or list of entities that you want to reset and how long you want them to be off for the reset. When a Script using this Blueprint is called, it will use Homeassistant turn off to shut them off, wait the delay, then turn them back on. Simple Simple, but if you are doing it over and over in an automation, this cleans up the code quite a bit.

๐Ÿ—ฟNotice๐Ÿ‘ฎ๐Ÿฟโ€โ™‚๏ธ:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
entity
duration
2002.0K3.6K
๐Ÿ”˜
Button Actions
simple
0 inputs

long_short_toggle_4_magic_cube_and_other_things - 2023-12-07

This script was invented to be used with my Magic Cube Blueprints. I released it as a standalone Script Blueprint because I saw others struggling with how so convert cube rotation to actions in other places. To use this blueprint, install it from the source in the normal way. After that add your unique name for the Script, and add an icon and change the entity_id if desired. You should only need to run the blueprint once, as you will be calling the unique name/entity you added above to use the code. This script has no inputs in the Blueprint screen because all the data is added to control the action live at each use. This requires you call this script with a couple of data values. One is a positive or negative number between 360 and -360 that in the original, represents the input angle from the cube movement. The other data point is the entity of the device(s) that you are trying o control. Only 1 of the short_entity or long_entity is required 4 this Blueprint to work. NOTE: the trigger variable below will be different for Z2M and ZHA and others. Look at my documentation for that cube integration help if you need it. Sample call / use of this script with ZHA: yaml - service: script.cube_long_short_toggle data: angle: '{{ trigger.event.data.args.relative_degrees | default(0.1) | float(0.2) }}' short_entity: light.kitchen_down_lights long_entity: light.kitchensink Sample call / use of this script with Z2M: yaml - service: script.cube_long_short_toggle data: angle: '{{ trigger.payload_json.action_angle | default(0.1) | float(0.2) }}' short_entity: light.kitchen_down_lights long_entity: light.kitchensink

๐Ÿ—ฟNotice๐Ÿ‘ฎ๐Ÿฟโ€โ™‚๏ธ:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
2005.1K961
๐ŸŽ›๏ธ
Device Control
simple
3 inputs

Media Player Script Blueprint 2023-12-09

This provides a way to play canned media files with the big long list of YAML entries but keep the main script or automation clean. All that is required there would be a simple line like:
'- service: script.media_player_doorbell_sound'
Community link for this blueprint

๐Ÿ—ฟNotice๐Ÿ‘ฎ๐Ÿฟโ€โ™‚๏ธ:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
entity
text
2006.7K2.7K
๐Ÿ”˜
Button Actions
simple
1 inputs

volume_control_4_magic_cube_and_other_things - 2023-12-07

This script was invented to be used with my Magic Cube Blueprints. I released it as a standalone Script Blueprint because because of requests to extend the function of my BP's with how to convert cube rotation to volume in other places. Research found me this Post from Petro which had a very elegant solution to the problem, It was very easy decision to adopt it here. To use this blueprint, install it from the source in the normal way. After that add your unique name for the Script, and add an icon and change the entity_id if desired. You should only need to run the blueprint once, as you will be calling the unique name/entity you added above to use the code and provide action data. This script has one !input in the Blueprint screen to set the sensitivity of the rotation to volume changes. 30 seemed about right, but adjust as needed. Because all the data is added to control the action live at each use this is the only !input. This requires you call this generated script wth 2 data values when you want it to run. One is a positive or negative number between 360 and -360 that in the original, represents the input angle from the cube movement. The other data point is the entity of the media_player that you are trying to control. NOTE: the trigger variable below will be different for Z2M and ZHA and others. Look at my documentation for that cube integration help if you need it. Sample call / use of this script for ZHA: yaml - service: script.cube_dimmer_control_bp data: angle: '{{ trigger.event.data.args.relative_degrees | default(0.1) | float(0.2) }}' mp: media_player.farg Sample call / use of this script for Z2M: yaml - service: script.cube_dimmer_control_bp data: angle: '{{ trigger.payload_json.action_angle | default(0.1) | float(0.2) }}' mp: media_player.farg

๐Ÿ—ฟNotice๐Ÿ‘ฎ๐Ÿฟโ€โ™‚๏ธ:

  • Copies of the original Blueprint that were converted via the 'Take Control' feature or other means are officially not supported by me.
  • I may or may not be able to support you when you have a problem after you make changes to my code, as some of the code is no longer mine.
  • I & my license also require attribution as a link back to the original should you use this code in your own creation.
  • Here is a link to my license & the original github post expected to be followed & referenced as attribution should you use this code elsewhere.
number
2007.3K964
๐ŸŽ›๏ธ
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
1241.5K1.3K
๐Ÿ”˜
Button Actions
simple
2 inputs

Voice - Set Reminders - Full LLM script

Image More detailed information can be found here

Set reminders

Prerequisites

  • Createa a ToDo entity to store the reminders in. You can use the button below to start the config flow Open your Home Assistant instance and start setting up a new integration.

Blueprint setup

Required

  • Set a todo entity to be used to store the reminders

Optional

  • Change the prompt settings for the LLM
  • Change or translate the settings for the response given by Assist

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:

Tool to set reminders based on voice commands. In case not recipient is provided ask for it, in case no clear date and time is provided ask for it, in case no recipient is provided ask for it

Usage

You can request for a reminder to be set. The LLM will ask you for missing data.

Examples

Set a reminder to take out the trash
Remind me to buy flowers for my partner
Make sure I do not forget to buy a gift for Mothers day
831.4K3.8K
๐Ÿ“ท
Camera Integration
simple
3 inputs

Voice - Get ToDo Entries - Local Assist Blueprint

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
entity
834.4K1.2K
๐Ÿ“ท
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
๐ŸŽ›๏ธ
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
812.4K2.5K
๐Ÿ””
Notifications
simple
2 inputs

Announce

A script that announces a message on a media player using text-to-speech.
entity
813.5K3.6K
๐ŸŽ›๏ธ
Device Control
simple
2 inputs

Sync a light with a binary sensor

This automation keeps a light in sync with a binary sensor.
entity
619.4K1.3K
๐ŸŽ›๏ธ
Device Control
simple
2 inputs

Toggle a light with a binary sensor

This automation takes a binary_sensor to toggle a light.
entity
616.5K414
๐ŸŽ›๏ธ
Device Control
simple
3 inputs

Turn off lights on no motion

This automation turns off the lights after a certain period of motion inactivity.
target
entity
number
614.8K2.1K
๐Ÿ”˜
Button Actions
simple
2 inputs

ZHA - IKEA TRADFRI - 1 Button Remote - OnOff

This automation simulates the use of the IKEA TRADFRI SHORTCUT Button connected through ZHA.
device
entity
618.0K572
๐Ÿ””
Notifications
simple
2 inputs

Announce Message

Announce a message on a speaker
entity
615.3K1.4K
๐Ÿ”˜
Button Actions
simple
2 inputs

ZHA - Aqara Vibration - Set Sensitivity

Set the sensitivity for the Aqara Vibration sensor. Press the button on the sensor immediately after you run the script, to make sure the sensor is awake, to receive the command.
device
select
615.5K4.4K
๐Ÿ”˜
Button Actions
simple
2 inputs

Automatic Timed Turn Off

This simple blueprint is used to create an automation that will automatically turn off the specified switch after a given time period whenever the specified switch is turned on.
entity
duration
218.4K4.1K
๐ŸŽ›๏ธ
Device Control
simple
0 inputs

Announce Sonos Alarm

This blueprint is used to add a script that will announce when the next alarm is set on the specified Sonos speaker. If the alarm is less than two hours away it will indicate how long until it rings. Otherwise the alarm will indicate the time when the alarm is set using a 12 hour format (e.g. 1 AM vs 1 PM). If it cannot find an alarm it will indicate that as well. The script will gracefully handle when speakers are in groups, and restore playing music after it announces the alarm. This is helpful as part of an automation when going to bed so you don't need to use a phone app to see when/if an alarm is set. I recommend setting the mode to parallel if you will use this script on more than one speaker.
218.5K2.4K
๐ŸŽ›๏ธ
Device Control
simple
0 inputs

Play Media

This blueprint is used to add a script for playing media. The script plays the media specified and provides shuffle, repeat and volume options. If you have a multi-room setup (e.g. Sonos) additional media players can be specified. The players will be grouped together with the primary media player.
216.0K4.4K
๐ŸŽ›๏ธ
Device Control
simple
0 inputs

Play Random Media

This blueprint is used to add a script for playing media. The script randomly chooses which media to use from the list given and provides shuffle, repeat and volume options. If you have a multi-room setup (e.g. Sonos) additional media players can be specified. The players will be grouped together with the primary media player.
2110.0K4.0K
๐ŸŽ›๏ธ
Device Control
simple
0 inputs

Stop Sonos Alarm

This blueprint is used to add a script that stops current audio on the specified Sonos speaker but if nothing is playing the script checks if an alarm is coming soon and if so, prevents it from going off by disabling the alarm and then re-enabling after it would have gone off. Only one alarm is impacted. This is perfect for when you wake up earlier than your alarm and don't want the alarm to wake others. I recommend setting the mode to parallel if you will use this script on more than one speaker.
219.3K578
๐ŸŽ›๏ธ
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
206.1K738
๐ŸŽ›๏ธ
Device Control
simple
3 inputs

Motion-activated Light

Turn on a light when motion is detected.
entity
target
number
02.3K985
๐ŸŽ›๏ธ
Device Control
simple
1 inputs

LLM Helper script for fetching weather forecasts

Creates a script which will allow an LLM to fetch weather forecasts
entity
08.2K329