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.
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)
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.
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.
Yep your correct, I tested this and it works on Android with your exact code (just changed the device and calendar). I am iOS. I did notice when I had 2 automation with 2 calendar events at the same time it only sent one voice notification once but I received 2 text messages. When I had 2 automation with 2 calendar events at the same time I got 3 voice messages and 4 text message.
Important Note:
When adding a calendar event to Home Assistant (HA), it must be scheduled at least 15 minutes into the future. This is because HA needs 15 minutes to register the event.
If you attempt to test the blueprint with a calendar event set, for example, only 1 minute before your intended notification, it will not work.
Example:
If the current time is 4:00 PM, and you want to test, your calendar event must be scheduled for 4:15 PM or later.
After adding the event, youâll need to wait for HA to register it.
For all-day events:
If you add an all-day calendar event, you still need to wait 15 minutes before testing.
I tested this 1 hour into future and it didnât workâŚThe event is not all day as far as i know, just one hour duration. Its not the duration thing, it must be something else.
So I have multiple automations from your blueprint - with same day and minus one day offset and if I have the automation with the TTS active I get the textual notification (twice, if I have two same day notifications active) but I donât get the TTS. Itâs like the âactionâ doesnât get triggered.