Aha that makes sense now thanks for letting me know.
I put it on the list of suggestions.
Blacky 
1 Like
Hello, I have been struggling with setting automations with calendar events for quite a while now and found your blueprint, which looks pretty straightforward. However, in testing it, I can see it’s being triggered but fails on conditions not met and it simply stops. The log doesn’t report on what conditions are not being met. Here is the YMAL:
The trace log:
Any thoughts?
Thank you.
I have tested it here again using your settings and it worked. Looks like it is your keyword. You must have @test in your summary or description.
When you look at the trace log, click on step details and then follow the orange line in the tree until it stops and click on the step condition A/B. You will see more details.
Blacky
Thank you for taking the time to look into it, and I’m sorry you’ve had to repeat yet again that same instruction about the keyword in the description. For some reason, I seemed to recall that it worked once without the keyword in the description of the calendar event and subsequently kept skipping that step in my trials. In any case, it’s all good now.
No problem, you can opt not to use a keyword if you like by selecting Don’t use “Key Word” in calendar
Blacky
Transform Your Calendar: Turn Events Into Notifications and Actions! 
New Feature For iOS
- Notification Sound - The Home Assistant app for iOS includes built-in notification sounds, and you can import sounds from your iOS device into the app. Custom sounds can also be added via iTunes or from your cloud storage.
For more information on using sounds in the Home Assistant app, click here.
Maintenance 
- From time to time, Home Assistant updates their YAML standards and coding practices. To align with their roadmap, we’ve updated the code accordingly. We will continue to apply these updates across all our blueprints as they are revised.
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 
Good day I have been trying to get this to work - it wont trigger the automation even when i try manually
here is my yaml
alias: Calendar Notifications & Actions
description: ""
use_blueprint:
path: Blackshome/calendar-notifications-and-actions.yaml
input:
calendar: calendar.calendar
include_calendar_trigger: disable_key_word
start_calendar_offset:
hours: -24
minutes: 0
seconds: 0
days: 0
include_start_notify: enable_start_notify_options
start_notify_device:
- 6de
end_calendar_offset:
hours: -23
minutes: 0
seconds: 0
days: 0
include_start_action_button_confirmation: disable_start_action_button_confirmation
include_start_auto_actions: []
start_notify_data:
- sticky
include_end_notify: disable_end_notify_options
when I check the trace i get (Stopped because of unknown reason at December 2, 2024 at 11:29:19 PM (runtime: 0.00 seconds))
thank you
Welcome to the community.
You can’t run it manually.
Your calendar event must be added to HA 15min into the future. HA need 15 min to register the calendar event so if you try and add a calendar event in 1 min before your notification to test it then it will not work. Example if the time now is 4:00pm and you add a calendar event in to test then it must be 4:15pm. Then you have to wait. If you put in a all day calendar event then you have to wait 15 min before you can test it. You then can keep adjusting your offsets in the blueprint so you can test it quicker.
Your start offset is -24 so this will be the problem. To get your head around it try no offset and just add a calendar event in 15 min into the future, sit back and wait for 15 min to pass and you should get the notification.
Blacky
thank you for the reply - trying now have set an event in the calendar to 30min in the future with no offset
Will let you know how I get on
alias: Calendar Notifications & Actions
description: ""
use_blueprint:
path: Blackshome/calendar-notifications-and-actions.yaml
input:
calendar: calendar.calendar
include_calendar_trigger: disable_key_word
start_calendar_offset:
hours: 0
minutes: 0
seconds: 0
days: 0
include_start_notify: enable_start_notify_options
start_notify_device:
- 6de
end_calendar_offset:
hours: 0
minutes: 0
seconds: 0
days: 0
include_start_action_button_confirmation: disable_start_action_button_confirmation
include_start_auto_actions: []
start_notify_data: []
include_end_notify: disable_end_notify_options
It worked thank you great automation
Firstly, thank you for this automation I have been using it for a while.
I just updated to the latest 1.8 and I get the following error (even though I see the notification and all works)
Note: I only have the default settings in for the start notify title/description fields, and really only using it for bin days at the moment so no actions etc.
Template variable error: ‘list object’ has no attribute ‘split’ when rendering ‘{% set keywords = calendar_trigger.split(’,‘) %} {% set keywords = keywords | map(‘trim’) | list %} {{ keywords | select(‘in’, trigger.calendar_event.summary) | list | count > 0 }}’
Template variable error: ‘list object’ has no attribute ‘split’ when rendering ‘{% set keywords = calendar_trigger.split(’,‘) %} {% set keywords = keywords | map(‘trim’) | list %} {{ keywords | select(‘in’, trigger.calendar_event.description) | list | count > 0 }}’
any ideas what I might have configured wrong (fyi when I went from 1.7 to 1.8 I recreated the automation)
Regards,
Mobs
Welcome to the community.
Could you please provide us your YAML of the automation? This YAML code are the settings you have selected in the automation so I can help. To do this go into your automation, top right 3 dots, Edit in YAML, copy all the code, come back to the forum and in your reply at the top tool bar click on “</>” and paste code in there.
FYI When you update a blueprint you don’t need to recreate the automation. This is the beauty of blueprints, you can update the blueprint and it carries through all of your existing automations. You may be aware of this already.
Blacky
Thanks Blacky,
Yea the recreate was only because I was seeing the error just thought id start fresh and see if it replicated (which it did). YAML below.
alias: Bin Days - Tell House which Bins are to be put out
description: ""
use_blueprint:
path: Blackshome/calendar-notifications-and-actions.yaml
input:
calendar: calendar.bin_days
include_calendar_trigger: disable_key_word
start_calendar_offset:
hours: -5
minutes: 0
seconds: 0
days: 0
include_start_notify: enable_start_notify_options
start_notify_device:
- 2e8b983bcce5fa60516670ec489d4d66
- ad63a2cfb8aac012c5110e210afe1ab0
- e261d8fad1ad85416c415300a92045ac
- 5e1effb79cbdb21f5df174540ea7c0ee
start_notify_data:
- sticky
start_notify_interruption_level: time-sensitive
Thanks for your YAML, all fixed. Problem was if you had no keyword in the input. You can update now as it has been updated already.
Thanks for your help and reporting the bug.
Blacky
1 Like
Transform Your Calendar: Turn Events Into Notifications and Actions!
Bugs Fixes 
- Fixed error log when there was no keyword in the input.
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
Thankyou so Much Blacky too!
1 Like
Did anyone manage to get TTS notifications via companion app to work as a “Calendar Start action”? See pictures of interface, am I missing some configuration?
I could be wrong but Home Assistant does not support playing TTS audio directly through the mobile app. The mobile app is designed for text-based notifications and cannot natively handle TTS playback.
Blacky
It does work, the companion app generates the TTS (or the assistant in the phone maybe). This code snippet works in another automation that i use:
action: notify.mobile_app_vog_l29
metadata: {}
data:
message: TTS
data:
tts_text: Alarm! Someone is in the house! Inspect!
media_stream: alarm_stream
ttl: 0
priority: high
The phone “talks” it says Alarm! Someone is in the house! Inspect! .
While this from your blueprint doesn’t:
alias: Nova avtomatizacija
description: ""
use_blueprint:
path: Blackshome/calendar-notifications-and-actions.yaml
input:
calendar: calendar.sestanki_in_rojstni_dnevi
include_calendar_trigger: disable_key_word
include_start_notify: enable_start_notify_options
start_notify_device:
- 7ddf3ab80971f424ff7d5e6c3c0186b8
start_notify_data:
- high_priority
include_start_auto_actions:
- enable_start_action_1
start_action_1:
- action: notify.mobile_app_vog_l29
metadata: {}
data:
message: TTS
data:
tts_text: You have a calendar event today!
media_stream: alarm_stream
ttl: 0
priority: high
Do you see some error? How do I debug this?