Great to hear. Did you have to do smth special?
Iâm not getting it to trigger on the start time, just on the end timeâŚ
Hi.
I am slightly puzzled with my problem
I created CalDAV calendar and linked it with blueprint.
Automation as follows:
alias: Tesla ogrzewanie
description: ""
use_blueprint:
path: Blackshome/calendar-notifications-and-actions.yaml
input:
calendar: calendar.tesla
calendar_trigger: "#Ogrzewanie"
start_calendar_offset:
hours: 0
minutes: -30
seconds: 0
days: 0
start_notify_device:
- 1193693ddd1d4451aa997d4e3e300d57
- 4faae792f0475757ca69d6afec4c7c5c
- 9a63da0a2b57d0e5b6901eb03da672c6
start_title: >-
Ogrzewanie Tesi - {{ (trigger.calendar_event.start |
as_datetime).strftime('%H:%M') }}
start_message: NaciĹnij i przytrzymaj TYLKO jeĹli chcesz anulowaÄ.
start_notify_interruption_level: critical
include_start_action_buttons:
- enable_start_action_button_2
start_action_button_stop: Anuluj ogrzewanie
start_time_delay:
hours: 0
minutes: 1
seconds: 0
include_start_auto_actions:
- enable_start_action_1
start_action_1:
- action: notify.domoticz
metadata: {}
data:
data:
disable_notification: true
message: Grzejemy...................
enabled: true
- action: notify.domoticz
metadata: {}
data:
data:
disable_notification: true
message: >-
Event {{ trigger.calendar_event.summary }} @ {{
(trigger.calendar_event.start | as_datetime).strftime('%H:%M') }} @
{{ (trigger.calendar_event.start | as_datetime).strftime('%H') }} @
{{ (trigger.calendar_event.start | as_datetime).strftime('%M') }} @
{{ trigger.calendar_event.description }}
enabled: true
- action: input_number.set_value
target:
entity_id: input_number.tesla_heater_time
data:
value: >
{% set remaining_time = ((trigger.calendar_event.start |
as_datetime).strftime('%H:%M')).split(':') %} {{remaining_time[0] |
int * 60 + remaining_time[1] | int }}
enabled: true
- action: input_text.set_value
target:
entity_id: input_text.tesla_heater_day_of_week
data:
value: >
{{as_timestamp(trigger.calendar_event.start) |
timestamp_custom('%A',false) }}
enabled: true
- action: notify.domoticz
metadata: {}
data:
data:
disable_notification: true
message: >
tesla-heater-time:
{{states('input_number.tesla_heater_time')|string}}
tesla-heater-day-of-week:
{{states('input_text.tesla_heater_day_of_week')}}
enabled: true
- action: rest_command.tesla_heater_on
metadata: {}
data: {}
enabled: true
include_start_notify: enable_start_notify_options
include_start_action_button_confirmation: disable_start_action_button_confirmation
include_end_auto_actions:
- enable_end_action_1
end_action_1:
- action: rest_command.tesla_heater_delete_entry
metadata: {}
data: {}
end_action_2: []
end_time_delay:
hours: 0
minutes: 0
seconds: 0
start_action_button_2: Jednak grzejemy
start_action_2:
- action: notify.domoticz
metadata: {}
data:
message: start akcji 2
global_conditions:
- condition: numeric_state
entity_id: sensor.oczyszczalnia_zewn_trzna_temperatura
below: 5
The entries are punched in calendar way ahead of the scheduled start.
The automation started at 7:30 with (#Odpady plastiki) and stopped while it has no found expected keyword in calendar entry (that is clear) BUT it did not start with next schedule (#Ogrzewanie) at 7:40 - WHY ?
Could be the reason that entry (#Odpady plastiki) is from 8:00 till 9:00 (1 hour long) and is overlapping the next entry (#ogrzewanie) which is only 5 minutes long ?
Best Regards
Hello.
First of all thank You for that blueprint, hopefully it will become handy for me as I am still trying to set it up.
Major question from my side is if manual trigger in 3 dot menu right beside automation should really start it or not? For me it is not working so I am unable to test it at this point.
What I did so far:
As I only have 2 events in calendar I didnât use any keywords, I picked them directly in trigger menu (so I have 2 separate automations, one for each event).
Then I:
- unchecked âuse calendar keywordâ
- set âcalendar start offsetâ to -8h as I want to get notification on 4PM day before and calendar event are set for whole day
- moved to âstart actionsâ part and checked âEnable start auto action 1â
- in Start Action - Action 1 I added telegram bot notify action which I already use for few other things and put âBins tomorrowâ as a message
Will this work? As I mentioned earlier clicking Run Actions doesnât do anything for me, I still have âNeverâ in âLast triggeredâ column.
No
In your trigger you have a start offset of -30 min. So it should of sent the notification at 07:40.
I havenât looked at your actions. If you are having problems, I would add one easy action (basic notify) to see⌠but it should work anyway.
Also note you global condition Your sensor.oczyszczalnia_zewn_trzna_temperatura must be below 5 for it to run. You could try disabling this for testing.
Hope this helps you find it.
Blacky
You must let it run live, you canât click the run action.
For testing you can change your offset to suit the time you are curently in. You can keep editing the offset and it will work instantly but if you edit the calendar event you have to wait 15min for HA to see it.
Note: if you have 2 automations and your not using a keyword then both will run. The keyword is the link to an automation and without it, it will fire on every calendar event.
Blacky
The thing is, that automation did not start at 7:40. There was no trace of it. It is not an issue of sensor.oczyszczalnia_zewn_trzna_temperatura entity.
I tested everything and it worked perfectly using your YAML. All I changed is the device to notify and the entity in the condition.
With all your actions I get an error obviously but I get the first message came through.
Removing your actions and I added my own actions to just notify myself I have no problem.
Note that when you push your action button 2 you will get action 1 & 2 and I am not sure if this is what your after.
Blacky
Note that when you push your action button 2 you will get action 1 & 2 and I am not sure if this is what your after.
It is on purpose.
Had an issue when push action 1 was used then action 1 was executed twice - do not know why
Works like a charm, Thank You again.!
Hi there. I have a problem with the blueprint (or I do use it incorrectly, I do not know.). I want to trigger an event 1 day 11 hours before it starts. So I enter the time as show in the screenshot. First: I get the error as shown, 2nd it does not trigger anything.
Any idea what I make wrong?
Funny how other browser work, as I donât see that error. All is good just ignore the error.
The offset works in, Days : Hours : Minutes : Seconds, so you have -1 day and -11 hours. Adjust the -1 day to 0.
Blacky
Hay , why donât I see any device available? ( Start Notify - Devices To Notify ) I would like to add nspanel as a notification device, can you help me with that?
I would like him to inform me about garbage collection.
Hi, I found the answer in a older post here. the error message can be negelcted. It works.The trigger worked now when I used the keyword with an @ in front of it.
Welcome to the community.
You will need to set up your device with the HA App. First you need to set up a user for your nspanel (user name password). The install the HA App on the nspanel and login using your user name and password. Then make sure you allow notifications in the APP. You will then see the device to select. Morer info on the HA App click here
I have done a WTH post that would work really well for your nspanel if HA develops it. You can vote on it click here
Blacky
Hi @Blacky, do you believe it would make sense to add the possibility to âgroupâ notifications on the device (android only)? Introduction | Home Assistant Companion Docs
I cannot create MRs on gists, but if you want to take a look at my fork diffs: https://gist.github.com/override80/544916aa45b2d54d5856fab576fd669b/revisions
Thank you for answer ,
but HA can only be installed on nspanel pro and I donât have pro
I want to do something like that but when selecting a device it doesnât show me anything, only the phone. It was easier for me to upload the software than to create calendar notifications on nspanel now