Send a mobile notification when add-on update is available

On-Off schedule with state persistence

Send Web UI persistent notifications to Mobile Devices

Simple Safe Scheduler

• Time of the day (dynamically provided as an input_datetime entity);
• Day of the week (multiple days can be selected);
• Week frequency (allowing to schedule the action to run i.e. every 2 weeks).

Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote

More Info

Controller - IKEA E1743 TRÅDFRI On/Off Switch & Dimmer

More Info

Controller - IKEA E1744 SYMFONISK Rotary Remote

More Info

Controller - IKEA E1766 TRÅDFRI Open/Close Remote

More Info

Controller - IKEA E1812 TRÅDFRI Shortcut button

More Info

Controller - IKEA E2001/E2002 STYRBAR Remote control

More Info

Controller - IKEA E2123 SYMFONISK sound remote, gen 2

More Info

Controller - IKEA E2201 RODRET Dimmer

More Info

Controller - IKEA E2213 SOMRIG shortcut button

More Info

Controller - IKEA ICTC-G-1 TRÅDFRI wireless dimmer

More Info

Controller - OSRAM AC025XX00NJ SMART+ Switch Mini

More Info

Controller - Philips 324131092621 Hue Dimmer switch

More Info

Controller - Philips 8718699693985 Hue Smart Button

More Info

Controller - Philips 929002398602 Hue Dimmer switch v2

More Info

Controller - SONOFF SNZB-01 Wireless Switch

More Info

Controller - Tuya ERS-10TZBVK-AA Smart knob

More Info

Controller - Xiaomi WXCJKG11LM Aqara Opple 2 button remote

More Info

Controller - Xiaomi WXCJKG12LM Aqara Opple 4 button remote

More Info

Controller - Xiaomi WXCJKG13LM Aqara Opple 6 button remote

More Info

Controller - Aqara WXKG11LM Wireless Mini Switch / Xiaomi WXKG01LM Mi Wireless Switch

More Info

Hook - Cover

More Info

Hook - Light

More Info

Hook - Media Player

More Info

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

🗿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 intended to be used with pfSense HACS Integration: GitHub - travisghansen/hass-pfsense: pfSense integration with Home Assistant . However it could be used with any device tracker that reports home when the device is up and something else when it isn't. It will create a persistent notification when triggered. Triggers / notifications can be enabled for a time period each day and/or for specific days of the week. There is also the ability to roll your own specific notification or other action as an action statement. I also found that Awesome Blueprints Matt has a blueprint to send this stuff to your phone, so I referenced that here to be helpful if you are looking for that. If you want to send these notifications to a mobile device, i suggest you look at the following blueprint to use in conjunction with this blueprint. I am not affiliated with that, but decided I didn't want to re-invent the wheel as mobile HA is not something I do every day.

🐘 Requirements

Persistent Notification Integration Required

Persistent Notification Integration Docs

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

Tasmota Rules:

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

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

The monitored areas need to be set up as zones in Home Assistant. SEE: HA ZONES LINK

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

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

🍎 There is a set of 36 event functions that will trigger on specific actions on specific sides that are listed as Group 1 actions 🍎.

🍒 There is a set of 6 event functions that will trigger on specific actions on ANY side that are listed as Group 2 sctions 🍒.

🍐 There is a set of 30 event functions that will trigger on cube flips to & froma specific sides that are listed as Group 3 sctions 🍐.

🍕 There are 2 actions (shake and drop) that only occur once and are OK to be combined with any other group. Listed as Group 4 sections 🍕.

NOTICE: This cube can be triggered 124 ways, but only 38(+54) of them are unique (with templating).

This was "forked" from >> Aqara Cube ZHA - Simplified face-based device control > Project authored by EdwardTFN (Edward Firmo) and he based on on several other giants that came up with most of the base code. >> >> ZHA - Aqara Magic Cube (57 actions) >> >> Aqara Magic Cube ZHA (51 actions) >> >> ZHA - Aqara Magic Cube (24 actions) > >I sincerely thank Them for their work. I wanted to support a version that was virtually the same as my Z2M version, and leverage all the documentation and code samples there but still port it to ZHA. I also had a better idea for troubleshooting info. _________________________

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

🍎 There is a set of 36 + 18 actions that will trigger on specific actions on specific sides that are listed as Group 1 🍎

🍒 There is a set of 6 + 3 actions that will trigger on specific actions on ANY side that are listed as Group 2 🍒

🍐 There is a set of 30 + 30 event functions that will trigger on cube flips to & from specific sides that are listed as Group 3 🍐

🍕 There are 5 actions (shake & throw for each mode & hold in scene mode) that only occur once in each mode & are OK to be combined with any other group in that mode. Listed as Group 4 sections 🍕.

NOTICE: This cube can be triggered 124 ways, but only 38(+54) of them are unique (with templating).

This blueprint has been known to freak out when there are spaces or odd characters in the MQTT Topic. Make sure there are no spaces, ONLY a single word, and ONLY A thru Z, a thru z, and 0 thru 9 in the topic. ( / is ok between device and topic) If there are, you will need to change the name of the cube to remove those characters.

IF YOU SEE --> TemplateError: Must provide a device or entity ID

This was forked from https://community.home-assistant.io/t/z2m-xiaomi-cube-controller/263006 1.2 project authored by luckypoppy and the friends he pulled together to create the base. I sincerely thank Him (Them) for their work. I felt there needed to be more documentation for rookie users to properly set this up. I had quite a few questions and when I saw a few questions in that chat from people struggling, I wanted to help. I also had a better idea for troubleshooting info.

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

🍎 There is a set of 36 event functions that will trigger on specific actions on specific sides that are listed as Group 1 actions 🍎.

🍒 There is a set of 6 event functions that will trigger on specific actions on ANY side that are listed as Group 2 actions 🍒.

🍐 There is a set of 30 event functions that will trigger on cube flips to & from specific sides that are listed as Group 3 actions 🍐.

🍕 There are 2 actions (shake and drop) that only occur once and are OK to be combined with any other group. Listed as Group 4 sections 🍕.

NOTICE: This cube can be triggered 124 ways, but only 38(+54) of them are unique (with templating).

This was forked from https://community.home-assistant.io/t/z2m-xiaomi-cube-controller/263006 1.2 project authored by luckypoppy and the friends he pulled together to create the base. I sincerely thank Him (Them) for their work. I felt there needed to be more documentation for rookie users to properly set this up. I had quite a few questions and when I saw a few questions in that chat from people struggling, I wanted to help. I also had a better idea for troubleshooting info.

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

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

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

🗿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 IS DEPRECATED & IS NO LONGER SUPPORTED. ### FOR REPLACEMENT SEE: https://github.com/SirGoodenough/HA_Blueprints/blob/master/Automations/Zigbee2MQTT%20-%20Xiaomi%20Cube%20Controller%20MQTT%20Triggered.yaml

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

2:

3:

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

A: ✔️

B: ✔️

C: ✔️

D: ✔️

E: ✔️

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

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

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

🗿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
  

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

🗿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 NOT set-up TTS for you. You will be given the opportunity to add the incorrect options that will NOT allow your TTS to function. Your best road to success will be to add a TTS session with UI, and only after that is successfully talking to you should you take the languages and options that work there and apply them in this Blueprint. The safest thing to do other than that is to start with the basic sonfiguration for the TTS_say integration that you are using and add options one at a time. The very basic requirements are for you to provide the *tts_say method that you have installed and tested, the entity that you want to send it to, and the message you want to send. Beyond that likely involves trial and error that may best be done in the Developer Tools Services area here:

⚠️ This Blueprint makes the assumption that you already have a tested & proven TTS integration installed and you know how it works and how to use 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.

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

👥 people presence 🗓️ multiple schedulers 🚶 presence sensor ↔️ proximity aka geo fencing

👥 people presence 🗓️ multiple schedulers 🚶 presence sensor ↔️ proximity aka geo fencing

💥 New In Version 3

🤙 Features

Hints

If you like my work and support feel free to support me.

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

Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote

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

Set reminders

Prerequisites

• Createa a ToDo entity to store the reminders in. You can use the button below to start the config flow

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:

Usage

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

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

📳 Appliance Notifications & Actions

• Appliance Trigger:
  • Enter the power sensor entity that measures the live current draw of the appliance. Common devices with these sensors include smart plugs, energy meters, etc.
  • The automation is triggered when the appliance's current draw exceeds a set wattage.
  • The automation ends when the appliance's current draw falls below a set value.
• Notification Options:
  • Send notification messages to one or multiple devices when the appliance starts, finishes or the watchdog is triggered.
  • Your end message can also include estimates of total power consumption and cost.
  • Include duration tracking in your end message to track the appliance's operational time for the task or cycle.
  • Opt to sends a repeated notifications to remind you when the appliance cycle is complete.
  • Limit when notifications can be sent by using Notify Time Restrictions - helpful for avoiding alerts while you're asleep.
  • Notifications are compatible with both Apple iOS and Android devices, ensuring universal accessibility.
• Run Status:
  • Display your appliance's run status on your dashboard.
• Notify Time Restrictions:
  • Restrict notifications to the specified start and end times on the selected days. Notifications outside this time range will be skipped.
• Energy Tracking:
  • Use energy tracking to estimate the total energy usage (kWh) for each completed cycle. You can also choose to include the estimated cost of that cycle in the end notification.
  • Or simply update the start and end helpers without including any energy information in the end notification - useful for your own custom actions or other Home Assistant logic.
  ⚠️ Disclaimer - These values are estimates and should only be used as a guide. Please avoid relying solely on these estimates for accuracy and use them at your own risk. We cannot be held responsible for any inaccuracies or resulting losses, damages, inconvenience, or anything else that may occur.
• Time Tracking:
  • Runtime Tracking - Records the total runtime of your appliance by updating a text helper each time it completes a full cycle.
  • Duration Tracking - Tracks how long the appliance was running during each individual cycle and includes this duration in the end notification message.
• Cycle Counter:
  • Use the cycle counter to track the total number of cycles completed by your appliance. You can also choose to include this information in your end message.
• Service Reminders:
  • Service reminders help you track appliance usage and perform timely maintenance.
  • Cycle-Based Reminder - Notifies you when a service is due based on the number of cycles completed.
  • Time-Based Reminder - Notifies you when a service is due based on the total time the appliance has been in use since the last service.
• Watchdog:
  • The watchdog option monitors an appliance cycle completion.
  • It sends a notification if a cycle completion fails within the specified time frame.
• Device Tracker:
  • You can choose to use the device tracker for Start, End, and Watchdog notifications.
  • When enabled, only selected devices currently inside the chosen zone will receive those notifications.
• Custom Actions:
  • Tailor custom actions to suit your preferences and needs, enhancing the automation's functionality.
  • Configure actions such as triggering announcements on platforms like The Voice (HA), Google, Alexa, etc., to keep you informed about appliance events.
• Custom Conditions:
  • Enter any custom conditions to further customize the automation process.

• FAQ: Click Here
• Community Support Including Updates: Click Here

🚿 Bathroom Humidity Exhaust Fan

• Auto Trigger:
  • When the derivative percentage rises above a set value, the fan turns ON
  • When the derivative percentage falls below a set value, the automation waits for a time delay and then turns the fan OFF.
  • Optional - Set a maximum humidity percentage to trigger the fan ON. This is useful when having back-to-back showers.
  Note: You must have a humidity sensor in the bathroom and set up a 'Derivative Helper' for this automation to work.
• Manual Trigger Option:
  • This feature allows you to manually trigger the automation.
• Multi-Speed Fan Control Option:
  • You have the option to use fan speeds to control the staging of your fan.
  • You can choose to stage your fan in your preferred configuration, such as High/Off, High/Low, High/Low/Off, High/Med/Low, etc.
• Winter Mode Option:
  • You have the option to use 'Winter Mode.' This mode allows for different settings to be applied, accommodating the typically higher humidity levels experienced in winter compared to summer.
• Light Control Option:
  • Use the "Light Control" option to turn ON lights, adjusting brightness levels, colour temperatures, and transition times.
  • This feature is commonly utilized with LED lights in a shower niche.
  • For expanded lighting options, consider integrating my 💡Sensor Light blueprint, which utilizes the automation link feature.
• Manual Control Option:
  • Use a manual fan switch to toggle the fan ON/OFF.
  • Opt to use the auto-OFF option for timer-like functionality.
  • This is particularly useful for removing unwanted fumes from deodorant, hairspray, or the toilet.
• Automation Link Option:
  • This feature simplifies the process of automatically disabling your other automations by providing an automation linking mechanism.
• Bypass Functionality Option:
  • This allows you to bypass the automation, offering manual control and additional customization capabilities.
• Safety Measures:
  • Set a maximum runtime safeguard for the fan to prevent continuous operation.
  • Benefit from built-in safeguards to ensure smooth operation and reliability, even if Home Assistant restarts.
• Blueprint Add-On Integration:
  • Sensor Light: Control your lights in the bathroom. Click Here to learn more.
  • Toilet Exhaust Fan: Integrate with a toilet in the bathroom. Click Here to learn more.

• FAQ: Click Here
• Community Support Including Updates: Click Here

💡 Sensor Light

• Trigger:
  • You can choose any binary sensors or schedules to trigger the automation.
  • A trigger sensor, such as a Motion Sensor, will activate lights, switches, scenes, and scripts when the automation is triggered.
  • A time delay begins the turning OFF process after all triggers are clear. See grouping sensors for more information.
  • If triggers are activated again before the time delay ends, the automation resets for continuous lighting.
• Scene and Script Integration:
  • Scenes or scripts offer additional customization for your spaces.
• Light Control Options:
  • Utilize "Light Control" to adjust brightness, colour temperature, colour, and transition times.
• Dynamic Lighting Options:
  • Opt for 'Dynamic Lighting' to automatically adjust brightness based on lux values, and/or adjust brightness and colour temperature according to the sun's position or the time of day.
  • Opt to use the 'State Control Option,' allowing you to toggle between dynamic lighting and normal lighting based on the entity's activation state.
• Manual Override:
  • Use "Bypass Options" for manual bypassing of trigger sensors, providing manual control and additional customization.
• Sun Elevation Options:
  • Implement "Sun Elevation" to restrict automation to darker conditions aligned with the sun's position.
• Ambient Light Sensing Options:
  • Set up an Ambient Light Sensor for activation in low-light conditions, customizable with specified LUX values.
• Time-Based Options:
  • Specify precise start and end times along with weekday selections to define when the automation should run.
• Device Tracker Options:
  • Utilize "Device Tracker" to activate automation when home or within specified zones, preventing unnecessary activations. This feature is particularly useful to prevent unnecessary lighting activations when pets trigger sensors while no one is home.
• Night Lights Mode:
  • Enable "Night Lights" for softer illumination during night time activities, automatically enabled based on conditions.
  • Opt to use "Night Glow". This feature activates a low-level light when no trigger is detected, creating a subtle ambient glow perfect for nighttime use.
• HA Restart Safeguards:
  • Benefit from built-in safeguards for Home Assistant restarts.
• Blueprint Add-On Integration:
  • Sensor Light Add-On - Enhances media control automation. Click Here to learn more.
  • Bathroom Humidity Exhaust Fan - Keeps the lights ON when showering. Click Here to learn more.

• The Settings & Best Practice Guidelines: Click Here
• FAQ: Click Here
• Community Support Including Updates: Click Here

Controller - IKEA E1524/E1810 TRÅDFRI Wireless 5-Button Remote

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

Automatic Gate ⛩️

Description 📝

Key Features 🌟

• Automatic Opening: Your gate will open automatically when you drive home. No need to press any buttons ! 🏠
• Smart Navigation: Directly open the gate when leaving home, or launch an itinerary when starting from outside 🚀
• Multi-User Support: Manages up to 10 drivers simultaneously 🚗
• Collision Prevention: Ensures the gate doesn't close on anyone arriving or leaving at the same time 🚧
• Security & Reliability:
  • Precise Waze and ETA calculations to have your gate fully open exactly when you arrive home 🎯
  • Real-time position tracking to adjust timing for traffic or if you pass by without entering 📍
  • Car status monitoring to cancel everything if you leave your car ✋
  • Built-in timeouts in case of an internet loss ⏳
  • Maximum entry and leaving time before auto-closing ⌛
  • Notification alerts at each decision of the automation 🚨
  • Manual actions prioritized over the automation, letting you control your gate even while the automation is running ✍️
• Customizable Settings:
  • Auto-close with iBeacon 📡
  • Adjustable notifications 💬
  • Customizable security options 🔒
  • Customizable gate operation timings 🛠️
  • Customizable travel time refresh rate 🔁
  • Multiple gates supported by reusing the blueprint ♻️

More info ℹ️

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

Itinerary tracker notification 📍

Description 📝

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

• 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

• 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)

Using this Blueprint

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