A description for the blueprint Version: yyyy.mm.dd

On-Off schedule with state persistence

A simple on-off schedule, with the addition of state persistence across disruptive events, making sure the target device is always in the expected state. 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. ℹ️ Version 2021.10.26

Send Web UI persistent notifications to Mobile Devices

Send Web UI persistent notifications with the provided ID to the specified Mobile Devices. 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. ℹ️ Version 2021.10.26

Hook - Cover

Hook automation which allows to control a cover. Supports opening, closing and tilting the cover. Features may vary depending on the selected cover. Features may vary depending on the selected Controller. An automation created with this blueprint must be linked to a Controller automation. Controllers are blueprints which allow to easily integrate a wide range of controllers (wall switches, remotes, dimmers, etc.) and use them to run a set of actions when interacting with them. They expose an abstract interface used by Hooks to create controller-based automations. A list of controllers supported by this hook is available here.

More Info

ℹ️ Version 2025.03.28 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟

Hook - Media Player

Hook automation which allows to control a media player. Supports volume setting, play/pause and track selection. Features may vary depending on the selected Controller. An automation created with this blueprint must be linked to a Controller automation. Controllers are blueprints which allow to easily integrate a wide range of controllers (wall switches, remotes, dimmers, etc.) and use them to run a set of actions when interacting with them. They expose an abstract interface used by Hooks to create controller-based automations. A list of controllers supported by this hook is available here.

More Info

ℹ️ Version 2025.03.29 📝 Changelog 📕 Full documentation regarding this blueprint is available here. 🚀 This blueprint is part of the Awesome HA Blueprints project. Please consider leaving a star on GitHub! 🌟

This sets the fan speed for a 3 speed fan (such as an IFAN03/IFAN04) based on a room temperature. In fact any fan with 3 speeds that is connected to the HA Fan Integration will work with this blueprint. NOTE: See the Sister Blueprint if you want to create an automation using MQTT. if you want to control this fan using the Home Assistant Fan Integration instead. There are action selectors for both the cycle loop and the shutdown loop for adding control of heating / cooling sources, or anything else you want Home Assistant to do for you. 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.

This sets the fan speed for a 3 speed fan (such as an IFAN03/IFAN04) based on a room temperature. In fact any fan with 3 speeds designated in MQTT [as 0,1,2,3) will work with this blueprint. NOTE: See the Sister Blueprint if you want to create a blueprint using the Home AssistantFan Entity. There are action selectors for both the cycle loop and the shutdown loop for adding control of heating / cooling sources, or anything else you want Home Assistant to do for you. 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.

This sets the amount of water sent to your Humidifier. You provide a minimum time and maximum time you want the water to run and this will send a time to the tasmota device controlling the water flow proportional to the ratio of the current humidity VS the target humidity. HA is using the Generic Hygrostat integration. My hardware is a Tasmota Sonoff SV sending the 24v to my humidifier water valve.

Tasmota Rules:

rule1 on Time#Minute|2 do var1 %var2% endon rule2 on system#boot do backlog power2 0; var2 20 endon on POWER2#state=0 do backlog power1 0; rule1 0 endon on POWER2#state=1 do rule1 1 endon rule3 on var1#state>110 do backlog power1 on;delay 1200;power1 off break on var1#state>100 do backlog power1 on;delay 1100;power1 off break on var1#state>90 do backlog power1 on;delay 1000;power1 off break on var1#state>80 do backlog power1 on;delay 900;power1 off break on var1#state>70 do backlog power1 on;delay 800;power1 off break on var1#state>60 do backlog power1 on;delay 700;power1 off break on var1#state>50 do backlog power1 on;delay 600;power1 off break on var1#state>40 do backlog power1 on;delay 500;power1 off break on var1#state>30 do backlog power1 on;delay 400;power1 off break on var1#state>20 do backlog power1 on;delay 300;power1 off break on var1#state<=20 do backlog power1 on;delay 200;power1 off endon 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.

This is Blueprint is provided as a helper for people using the Octoprint Plugin called OctoPrint-HomeAssistant. What this does is add 8 buttons, 4 of which you as the user can set your own G-Codes to for customizing. Also adds safe shutdown and presentation functions along with Change Filament and Load Filament. The first thing to remember is ANYTIME you make ANY changes to this Blueprint, you MUST restart the server so that the button entities can rebuild in the configuration you have selected. If you don't restart OctoPrint, the change may not be seen and you will wonder why and what is happening. To use this you will need the OctoPrint-MQTT plug-in installed along with the OctoPrint-HomeAssistant plugin. You will also need to be connected to an MQTT Broker that your Home Assistant instance is also connected to. Set-up for all that is covered within those packages. This also a Safe Shutdown to your setup that will stop the OctoPrint server then shut down the PI & power off your devices safely and cleanly. This works either by manually pressing a Home Assistant Button manually or it can be triggered as the temperature of the hot end ramps down with adjustable trigger points. This feature requires you to have mains power switch(s) to control power to the printer and peripherals. There is also a Presentation button that raises the Z and moves the print out for better access. Caution, this button assumes that the printer knows where home is and moves to an absolute position. The intention is to use it after a print has happened and you want access to get the item off the platter. If pressed when HOME is unknown it might bump into the end of the Y axis. Also if the Z is very high, it blindly moves the Z up 40 mm so make sure it looks like there is room. These values can be adjusted by editing the Blueprint itself if needed. 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.

This BluePrint will monitor a person or persons, and when they 'enter' or 'leave' the zone or zones you pick, it will trigger an action for both enter and leave phases. Yes, it will watch multiple people and multiple zones at the same time! I use this BluePrint to follow family members around during their day so that the family members at home know where their loved ones are. I used this to eliminate over 2 dozen separate Automations and Scripts in my Home set-up. The multiple person/multiple zone watch ability is the key. The monitored areas need to be set up as zones in Home Assistant. SEE: HA ZONES LINK The person needs LAT/LOG software running to report their location. I use Life360, but the Home Assistant App running on their phone will also work. There are likely other location monitoring methods but I am not aquainted with any of them. SEE: LIFE360 INTEGRATION LINK PERSON INTEGRATION LINK 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.

This ramps up the thermostat just enough at a time to keep your stage 2 (or emergency) heat from activating. This is meant to be run for instance in the morning when the system is recovering from overnight thermostat set-back, and you don't want it to kick in the stage 2 expensive heat source. There is an optional facility to disable this based on zone occupancy. Also there is a roll-your-own condition statement for things I haven't thought of. 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.

This uses tts.cloud_say from Nabu-Casa or Wyoming with the Piper Addon to tell you a door is open too long and a door has been closed. 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.

This will accept any 5 button presses or Binary Sensor detections and use them to preform an action. RE open a lock, or whatever. 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.

A script that gets my TV on and Reciever set-up to correct mode. 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.

🧿 This will create 3 buttons to help you. 🧿

1:

Press a button to restart ALL Tasmota Devices (Also to use during Home Assistant Restart to get all current State and Sensor readings)

2:

Press a button to update a couple of Tasmota devices to test that the new version will not break something, (Think of these units as your canary's in the coal mine.)

3:

Press a button to update ALL Tasmota devices to the latest version.

🧿 There are 5 Requirements to allow this to work. 🧿

A: ✔️

You need the Home Assistant Tasmota Integration to be functional on your system and HA needs to be able to see and interact with the devices. This Blueprint does not do that for you.

B: ✔️

This script makes the assumption that the default GroupTopic of 'Tasmotas' is available on all your Tasmota Devices. If you have devices that have been upgraded from pre V7 or so, they may be missing this GroupTiopic. If this is the case you will have to add the GroupTopic 'Tasmotas' to your device. 'https://tasmota.github.io/docs/Commands/#control'

C: ✔️

Your Home Assistant Instance needs to be or be communicating with an MQTT Broker. But this is easy because in order to have A: running, MQTT is a requirement for A:.

D: ✔️

Tasmota Devices firmware default MQTT topic is set to: %prefix%/%topic%/ If you did not change the topic in your Tasmota Devices then leave it as the default here as well. The other option available to you is to flip them as I do in my Home Assistant personally.

E: ✔️

Your Tasmota devices need to be updated to the same 'breaking change' generation as the Released version of Tasmota for this to be able to update. Again this is easy because in order to have A: running, Tasmota V9.2 minimum is a requirement for A:. Tasmota has had breaking changes in it's history. Therefore you should never stray from the upgrade path listed in the Tasmota Docs when upgrading. To upgrade your Tasmota firmware, you need to follow the path, or risk bad things happening: v1.0.11 🔀 v3.9.22 🔀 v4.2.0 🔀 v5.14.0 🔀 v6.7.1 🔀 v7.2.0 🔀 v8.5.1 🔀 v9.1 🔀 Current release. That means you currently need to manually update your firmware to v9.1 minimum for these buttons to work going forward. 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.

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 light dimming 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 1 input to select the relationship between the rotation amount and the speed of the color change. This requires you call this script wth 3 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 second data point is the entity of the light or light group that you are trying to control. The third is to tell the BP id you are controlling the red, the blue, or the green part of the color. 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_color_control data: angle: '{{ trigger.event.data.args.relative_degrees | default(0.1) | float(0.2) }}' light: light.grp_studio t_color: red Sample call / use of this script with Z2M: yaml - service: script.cube_color_control data: '{{ trigger.payload_json.action_angle | default(0.1) | float(0.2) }}' light: light.kitchensink t_color: red

🗿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.

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 light dimming 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 2 inputs in the Blueprint screen to set the sensitivity of the rotation action and the minimum bbrightness level for your lights. If the rotation is too sensitive the lights will change from dim to bright in too short of a rotation so make it less sensitive. If the lights flicker at low brightness, raise the minimum brightness level to stop it. The data is sent to the generated script to control the action live at each use. You only need to ececute this blueprint generator script if you wish to change in input values or create another dimmer script. This requires you call this script wth 2 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 light or light group 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.

🗿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. Sample call / use of this script for ZHA:

  - service: script.cube_dimmer_control_bp
    data:
      angle: '{{ trigger.event.data.args.relative_degrees | default(0.1) | float(0.2) }}'
      light: light.grp_studio
  

  Sample call / use of this script for Z2M:

  - service: script.cube_dimmer_control_bp
    data:
      angle: '{{ trigger.payload_json.action_angle | default(0.1) | float(0.2) }}'
      light: light.grp_kitch
  

Features

• toggle through scenes by order or last activated timestamp
• define a transition time
• select scenes by area and/or include/exclude specific scenes
• timeout for beginning at start if using static order

Help & FAQ: Simple Scene Toggle Version: 3.2 If you like my work and support feel free to support me.

Control anything using Aqara Wireless Switch. Customizable actions for each press. This version of the blueprint is for buttons supporting single, double and hold actions.

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

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

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

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?

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.

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

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

• 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

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 weather forecast 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 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:

Fetches the weather forecast for either a part of a day, or one or more full days. In case the weather for the weekend is requested, this means Saturday and Sunday

Usage

You can request for the forecast 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 weather conditions, for example, will it rain tomorrow. Or should I take an umbrella if I go out this evening.

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

Itinerary tracker notification 📍

Description 📝

A blueprint that notifies all selected users when another one is driving home

Key Features 🌟

• Companion app notifications 🔔
• Travel time and ETA notification updates 🔁
• On notification tap custom link 👆
• Speakers TTS support 🔊
• Adjustable notifications 💬

More info ℹ️

• Version : 1.1.0
• Set up sensors : click here
• Flowchart : click here
• Github : click here
• Discord : etiennec78

Set LED effects for Inovelli Blue Series Switches using Zigbee2MQTT. ℹ️ Version: 2025.8.0 To update this blueprint, read Re-importing a blueprint ✨ Features:

• Select one or multiple devices, entities, floors, labels, or areas with Inovelli switches
• Selectors for LED Number, Color, Brightness Level, Effect, and Duration
• LED Number, Color, Effect, and Duration can accept direct values or the “friendly name” listed in the dropdown
• Debug info to diagnose issues
  • Warning: Debug mode will create a persistent message for every entity called in the script plus 1

✅ Supported Models:

• Inovelli Blue Series On/Off Switch (VZM30-SN)
• Inovelli 2-in-1 switch + dimmer (VZM31-SN)
• Inovelli mmWave Zigbee Dimmer (VZM32-SN)
• Inovelli Fan Controller (VZM35-SN)

💬 Forum: https://community.home-assistant.io/t/z2m-inovelli-blue-series-switch-led-notification-script-vzm31-sn-vzm35-sn/489620 📜 GitHub: https://github.com/zanix/home-assistant-blueprints

Using this Blueprint

See Using the Script in the forum topic.

The main idea is you set the LED values when you call the script, the inputs below are for default values.

Set LED effects for Inovelli Blue Series Switches using Zigbee2MQTT. ℹ️ Version: 2025.8.0 To update this blueprint, read Re-importing a blueprint ✨ Features:

• Select one or multiple devices, entities, floors, labels, or areas with Inovelli switches
• Selectors for LED Number, Color, Brightness Level, Effect, and Duration
• LED Number, Color, Effect, and Duration can accept direct values or the “friendly name” listed in the dropdown
• Debug info to diagnose issues
  • Warning: Debug mode will create a persistent message for every entity called in the script plus 1

✅ Supported Models:

• Inovelli Blue Series On/Off Switch (VZM30-SN)
• Inovelli 2-in-1 switch + dimmer (VZM31-SN)
• Inovelli mmWave Zigbee Dimmer (VZM32-SN)
• Inovelli Fan Controller (VZM35-SN)

💬 Forum: https://community.home-assistant.io/t/z2m-inovelli-blue-series-switch-led-notification-script-vzm31-sn-vzm35-sn/489620 📜 GitHub: https://github.com/zanix/home-assistant-blueprints

Using this Blueprint

See Using the Script in the forum topic.

The main idea is you set the LED values when you call the script, the inputs below are for default values.