The notifications seem to be broken with 2026.01. I guess it has something to do with the transision from “trigger: platform: state” to “triggers: platform: triggers”.
Any ideas?
[edit] Obviously, I meant 2026.01 not 2016.01…
I can see with 2016.02 the following warning in the HA log for the automation
Error in 'choose[2]' evaluation: In 'template' condition: UndefinedError: 'snooze_until_entity' is undefined
and this error for the template
Template variable error: 'snooze_until_entity' is undefined when rendering '{% set ent = snooze_until_entity %} {% set snooze = states(ent) %} {% if not ent or snooze in ['unknown', 'unavailable', '', none] %} true {% else %} {% set snooze_ts = as_timestamp(snooze) %} {{ now().timestamp() >= snooze_ts }} {% endif %}'
Someone is facing the same?
I found out that the blueprint works again if I change my “Notify Services” section from “telegram_bot.send_message” to “notify.mobile_app_my_phone”…
Any Ideas how to fix this?
Hi Tony, I have a similar approach using a script and would be interested in your solution. How do you address the parameters in the notify services field?
Just as an aside: my script only notifies people who are in the house, and if no one is home, the notifications go to everyone. I’m also integrating Alexa.
@Malte Thanks for this nice blueprint.
Why do i often get this error :
Logger: homeassistant.helpers.template
Source: helpers/template/init.py:1750
First occurred: January 30, 2026 at 8:06:35 AM (41 occurrences)
Last logged: 8:07:39 AM
- Template variable warning: ‘friendly_name’ is undefined when rendering ‘The {{ friendly_name }} was left open’
- Template variable warning: ‘dict object’ has no attribute ‘description’ when rendering ‘{{ trigger.calendar_event.description }}’
I created an inspired / forked version here: ha-paul / home-assistant-blueprints · GitLab
fixed:
- clearance of notifications
- correct timestamp in notifications
2 Likes
Thank you for your work on fixing the Contact Sensor Left Open blueprint, specifically getting rid of the extraneous clearance notifications. I appreciate that you included Pushover which I also use for notifications.
@ppuschmann, thank you very much. Great work! I updated all my instances to your new blueprint. Really like the new At-Home notify option!
Thank you for maintaining this blueprint. Could you maybe add the Additional condition section of the original blueprint? This would be great!
1 Like
I have notifications going to my iPhone in other ways, but can’t find an appropriate entity in HASS that starts with “notify.” that the blueprint seems to want.
How do I find the correct entity?
That’s what I needed. thanks.
Thanks a lot for your effort, I like your new version; actually the original blueprint doesn’t show anymore the section to specify the devices to notify.
However, I am wondering why you removed the additional condition section as this was quite usefull, e.g. notify only if a window remains open for xx min in case of tmperatur range xyz.
Additional condition : Define a condition that is checked after the initial trigger before the notification is sent
2 Likes