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
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.
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â.
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.
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â
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.
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.
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!
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.
I have scoured through the posts and havenât seen if this blueprint is set to repeat the Start Notify for x times every x seconds. If not that would be a great addition to this blue print. Is there another blueprint that you have that would be an add-on to this one for that purpose?