It would be great, if you would share your code. I have the same message in my logs.
1 Like
Just wanted to say thanks! This is exactly what I needed after buying a few door sensors. Not only did I learn about grouping sensors but the automations created using this blueprint work flawlessly. Well done.
I just added this to Home Assistant Blueprint: Contact Sensor Left Open Notification · GitHub
to get this running add following two scripts:
alias: 💤 Set Snooze Time from Selection
mode: single
sequence:
- variables:
selected: "{{ states('input_select.silence_duration') }}"
- choose:
- conditions:
- condition: template
value_template: "{{ selected == '1 hour' }}"
sequence:
- target:
entity_id: input_datetime.open_window_alert_snooze_until
data:
datetime: "{{ (now() + timedelta(hours=1)).isoformat() }}"
action: input_datetime.set_datetime
- conditions:
- condition: template
value_template: "{{ selected == '2 hours' }}"
sequence:
- target:
entity_id: input_datetime.open_window_alert_snooze_until
data:
datetime: "{{ (now() + timedelta(hours=2)).isoformat() }}"
action: input_datetime.set_datetime
- conditions:
- condition: template
value_template: "{{ selected == '4 hours' }}"
sequence:
- target:
entity_id: input_datetime.open_window_alert_snooze_until
data:
datetime: "{{ (now() + timedelta(hours=4)).isoformat() }}"
action: input_datetime.set_datetime
- conditions:
- condition: template
value_template: "{{ selected == '8 hours' }}"
sequence:
- target:
entity_id: input_datetime.open_window_alert_snooze_until
data:
datetime: "{{ (now() + timedelta(hours=8)).isoformat() }}"
action: input_datetime.set_datetime
- conditions:
- condition: template
value_template: "{{ selected == '12 hours' }}"
sequence:
- target:
entity_id: input_datetime.open_window_alert_snooze_until
data:
datetime: "{{ (now() + timedelta(hours=12)).isoformat() }}"
action: input_datetime.set_datetime
- conditions:
- condition: template
value_template: "{{ selected == '24 hours' }}"
sequence:
- target:
entity_id: input_datetime.open_window_alert_snooze_until
data:
datetime: "{{ (now() + timedelta(hours=24)).isoformat() }}"
action: input_datetime.set_datetime
- conditions:
- condition: template
value_template: "{{ selected == 'Overnight (until 08:00)' }}"
sequence:
- target:
entity_id: input_datetime.open_window_alert_snooze_until
data:
datetime: |
{{ (
now().replace(hour=8, minute=0, second=0, microsecond=0)
+ timedelta(days=1 if now().hour >= 8 else 0)
).isoformat() }}
action: input_datetime.set_datetime
alias: ❌ Clear Snooze
mode: single
sequence:
- target:
entity_id: input_datetime.open_window_alert_snooze_until
data:
datetime: "1970-01-01T00:00:00"
action: input_datetime.set_datetime
description: ""
Two helper - Timestamp :
Selector:
1 Like
I would like to use the repeat notification option, but just to have the notification’s text updated on my android device. I don’t want to to receive notification sounds for the updates only the initial notification.
Can we get this into the blueprint?
Is there a way to assign this to a “label” of sensors? I have a label called. “all windows to notify”. I want any binary sensor assigned to that label to give an automation.
You might want to consider to vote on the following feature request:
I’ve just set up an automation using the updated blueprint but the notifications are “broken” for me as it seems like it’s trying to use a device that doesn’t exist, in my case it’s trying to notify notify.mobile_app_jim_iphone but my phone is known to HA as notify.mobile_app_jims_16_pro and I can’t figure out where it’s getting the wrong device name from, any ideas?
Check which device is assigned to the user. This can be done in profile settings. Or delete the invalid entity.
idk if this is supported by Android/Iphone. You can try it out with the set label, which is also used to delete the notification, as soon as the window was closed. Feel free to fork the code.
I have the same problem and the correct devices are assigned in the profile.
Hi! I’m brand new to Home Assistant. I have managed to muddle my way through to get this blueprint working, but I have no idea where to start on trying to convert the initial trigger timestamp from 24 hour into AM/PM. Any suggestions?
I had an issue with a gate that was unlatched, but kept swinging shut from the wind and bouncing. Each time it bounced, it reset the open timer and never triggered as staying open. Any easy fixes?
Yes, that would be possible by using Alert Once: https://companion.home-assistant.io/docs/notifications/notifications-basic/#alert-once
@Malte are you still reading here? 
Is the " Delete notification when not in issue state anymore" still working for others?
Used to work for me, but doesn’t seem to be right now.
HA seems to be doing the right things, trace of the automation seems to show correctly.
Am running iOS 26 now.
Hello,
I’m trying to use that excellent blueprint but doesn’t seem to work !?
Problem with ‘notify_services_string’ is undefined ?
The friendly_name is not defined
Am I the only one?
been using this for while, great blueprint.
i see that you still havent added an option for android users to set high priority for the messages to deliver instantly.
with these settings:
ttl: 0
priority: high
hope you can add this someday.
Thx for this blueprint. I tried to use it with ntfy and it complains that is has an unknown action. I tried to use a ntfy topic (that starts with notify.topic_name).
Do you have any idea what I could do or does the blueprint has to be updated?
This is great!
I’m seeing lots of messages like this in my logs when a door is left open:
2025-12-06 13:52:25.106 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'friendly_name' is undefined when rendering 'The {{ friendly_name }} was left open'
I asked Claude what the issue was:
The issue is that the
friendly_namevariable is being defined inside therepeatsequence, but it’s referenced in thenotification_titleandnotification_messageinputs which are evaluated earlier in the template rendering process.
I created a forked gist at Home Assistant Blueprint: Contact Sensor Left Open Notification · GitHub with a fixed version
2 Likes
Great blueprint. It works well for app and email alerts, but not so much for TTS devices. I actually have a universal script that handles all HA alerts by sending to one or more mobile app devices, one or more email addresses and one or more TTS audio assistants. How can we the blueprint to call the script with the necessary parameters?
UPDATE: I was able to get this blueprint to work with my universal automation. I modified my script to include all 4 parameters (data, target, title, message). Now it works. I simply add my script to the notify services field and remove all my other app/email notifications.
1 Like