Thanks for your input and your suggestions.
You will probably see it in my 
Notifications & Announcements BP first and then it will flow out to all the others.
Blacky 
I will be working on this error log but one thing I noticed in your YAML, your state is Detected. Not sure if that is working for you but have a look at the state in developer tools and match it. I may say on, note it is also cap sensitive.
Blacky
Iâve checked the sensor in Dev Tools and it currently shows as âonâ.
So Iâve changed the setting in the Automation to âonâ.
I assume the clear state will be âoffâ - so I set that in the End Trigger - Fixed State Option too.
Then I checked the System\Logs and saw this:
Logger: homeassistant.components.homeassistant.triggers.numeric_state
Source: components/homeassistant/triggers/numeric_state.py:153
integration: Home Assistant Core Integration (documentation, issues)
First occurred: August 30, 2024 at 2:45:00 PM (12 occurrences)
Last logged: 10:55:13 PM
Error initializing 'Notify: Family Room Presence Stuck' trigger: In 'numeric_state' condition: entity binary_sensor.family_room_presence_presence state 'off' cannot be processed as a number
Error initializing 'Notify: Family Room Presence Stuck' trigger: In 'numeric_state' condition: entity binary_sensor.family_room_presence_presence state 'on' cannot be processed as a number
Yes thank you⌠I can see it too but I thought I get you going first and then fix the problem. It is only a log issue and the automation will work.
Blacky
Thanks for the help Blacky.
1 Like
Some work is required with this update, so ensure you have time to edit your YAML files. The process is straightforward. Please see below for instructions on what to do.
New Feature - Start and End Triggers
-
Triggers - Weâve updated the start and end triggers for several reasons:
- Fixed an error log that required a new input.
- Added more trigger options, including button-triggered actions.
- Simplified usage with dropdown selections for trigger states, reducing errors.
- Improved layout for start and end triggers.
- Enhanced input descriptions for easier code management.
- Ensured continuity with other blueprints for a consistent experience.
STEPS REQUIRED WHEN UPGRADING 
If youâre unsure or uncomfortable with editing, you can delete your old automations and recreate them. However, if youâre confident with editing a bit of code, follow the steps below.
Best to record your settings by taking a screenshot or writing them down before updating the blueprint. We are only focusing on the trigger section.
-
Navigate to Settings > Automation > Filters (top right) > Blueprints and select the State Notifications & Actions blueprint. This will display a list of automations using this blueprint.
For each automation, click the three dots in the top right and select âEdit in YAMLâ. Look for the following lines of code. If you donât see these lines, you may not have selected the options, and the code might not be visible. Itâs okay if you canât find all the lines.
- entity_a_trigger:
- entity_a_state:
- below_vale_a_state:
- above_vale_a_state:
- time_delay_a_state:
- entity_b_trigger:
- entity_b_state:
- below_vale_b_state:
- above_vale_b_state:
- time_delay_b_state:
Review these settings, and either take note of your current configurations or copy the code for reference before deleting or modifying it.
-
Delete all the code containing the lines shown above, including your selections. You may see additional code not listed here; only delete the specified lines and avoid removing any other code. Do not click âSaveâ; instead, click on the three dots and select âEdit in Visual Editorâ.
-
Re-enter your inputs for both Start Trigger and End Trigger if you used these options.
-
Click Save, and youâre done
If you like this blueprint? Consider hitting the 
button in the top post 
If you like my blueprints, and would like to show your support or just say thank you? Click Here 
Enjoy
Blacky 
Is it possible to delete/cancel a notification sent with this blueprint?
What I mean:
Letâs say I watch the state of my front door and if left open for x minutes everyone in my family receives a notification via this blueprint.
So far no problem, thatâs easy.
But after someone closes the front door I donât need the notification still showing in all mobile phones cause there is no longer any action needed.
Yes you can do it through the start actions but you will need to set up your notifications there. It also depends on iOS or Android limitations.
Blacky
1 Like
Iâm migrating from Node-RED to Blueprints because of your cool blueprints, thanks for making them! I would like to have one automation to report on either a dishwasher or washing machine leak and I would like to use the entity that triggered the automation in my notification with something like {{ entity }} similar to how you can also do this with your battery blueprint. Is that possible?
Is it also possible to add a follow up action? For example, I would like to disable the power socket when the dishwasher leak sensor turns on. I canât seem to find that option in the Blueprint, but Iâm quite new to it and donât know all the extension possibilities yet.
And a small thing: there are a few typoâs mentioning âOpionâ instead of âOptionâ 
Thanks!
Your welcome.
I have a FAQ for this.
FAQ: How do I include the sensor name that triggered the automation in the message?
A: Please follow these steps Click Here
You can use either action buttons or just the action itself. However, I recommend setting up a separate automation for each leak sensor. Since itâs a water leak sensor, relying on action buttons could delay your response. Instead, itâs better to trigger the action to turn OFF the power socket immediately when a leak is detected. You can also set up an end notification to confirm the power socket is OFF or trigger any other actions you need.
Once everything is configured, make sure to perform a dry run to test and ensure it works as expected.
Edit:
I canât see where this is?
Blacky
Aaah, I see now. I have picked the Notifications & Announcement blueprint instead of this one. Apologies! Now everything is clear, thank you! The typo is also in that blueprint.
Yeah I have a few blueprints.
Thanks for the info. If you update Notifications & Announcement blueprint the typo is fixed.
Blacky
Thanks! I am using the blueprint now for my leakage sensors. I wanted to use the End trigger == OFF to report back if the leakage is solved but on every Home Assistant restart it now triggers the end trigger. Is there a way to ignore the state change on startup? Thanks!
Nice to know you all up and running⌠thanks for the heads up, I will look into this.
Blacky
1 Like
Thanks! Yes, all up and running thanks to your great blueprints! No idea how you are able to build and maintain these mega large blueprints, props!
1 Like
@ Blacky Thank you for your blueprint, it makes things a lot easier for me!
Would it be possible to set a âproximityâ function as a trigger?
If person âAâ is on the way to âZone Xâ does the automation start?
Perhaps with adjustable meters beforehand?
Iâm currently working with a different blueprint and Iâve got completely confused :-))
I havenât tested it but you would probably use option 9 as the trigger (below X) and then set your value.
Test it out see if it works and maybe let us know how you go.
Blacky
iâm looking at this one or sensor light add on strictly for smoke detectors. Would either still work if i grouped the smoke detectors? and is there a way in your blueprint to get a notifi on which smoke detector caused the alarm? Iâve noticed there really isnât a dedicated blueprint out there for smoke detectors at all. Yours seems closest.
Use this one to be notified as the Sensor Light Add ON will not notify you.
Donât group them just add them in separate then in the FAQ is shows you how you can be notified on which smoke detector caused the alarm. Click Here
Blacky
You sir are a life saver.
1 Like