Ya, but there is a short programm running etw. 30 minutes. i try 0.1 
If you have different times then you could also try a dead zone of 0 min and then look at your troughs and work out the longest one before it rises again then set your end time delay to be longer than the longest trough. You have 5 min set now and that may work if not try increasing it.
Blacky 
I have recently moved to this blueprint from another less advanced one.
The phone notifications for start and end work in an expected time frame. But I also have set custom actions to notify me on my Google home devices (end notification). This takes about 5 mins longer than the phone notification (this time is consistent).
Any reason for this?
The other blueprint is configured with the same settings and both the phone notifications and Google notifications trigger at the same time.
Thanks for the heads up… this snuck in with the Reminder Notification. I will need to fix this. Look out for a new update.
Blacky
1 Like
Bugs Fixed 
- Fixed a bug where, when opting to use Reminder Notification with Custom Actions - End, the custom action would not be executed until the reminder notification was fully completed.
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 
Hi @Blacky
Really like your Blueprints. I have a question, is it also possible to enable Pushover notifications in your Blueprints? Currently I can only select my mobile device which has the App installed on it.
Regards,
Max
1 Like
Welcome to the community.
I don’t use pushover but I guess you could use it in the custom actions.
Blacky
It’s exactly what I was looking for, and works great for the dishwasher.
So I duplicated the automation and changed all applicable entities and values to use with my washing machine.
I got the notification that it had started, but then stopped saying:
Stopped because only a single execution is allowed
After 0.01 seconds of running after two tests for conditions to be met. (Traces)
No further logs that I’m aware of.
I hope this is clear enough
Does this have to do with my duplication?
Kind regards and many thanks.
1 Like
Glad you like it
The automation stopped because it was triggered again while it was still running. This means that if the automation is already executing, any new triggers will not start another instance until the current one finishes.
You should only receive one of these messages during each cycle, and it is logged internally. There’s no need to worry about it.
let the automation run and it should complete its cycle.
Let us know how you go.
Blacky
That’s reassuring,
So the fact that I never got the notification at the end of the cycle might just be that my end parameters are not set up correctly. Thanks!
1 Like
Hello Blacky,
Thank you for your blueprint, which seems to be perfect with so much options !
I’m bangging my head to make it work… Currently using version 2.6
This is my washing machine running a cycle :
My power sensor reports the consumption every 5 sec
I’m notified when the cycle starts but never when it ends 
In the traces, it seems the automation tries to launch several times
Any advices ?
Thanks !
EDIT : sorry as a new user i’m unable to post multiple pictures in the same post.
Welcome to the community.
You currently have a repeat count of 2, try setting it to 1. Looking at your cycle, the power may drop below 5 watts several times (it’s hard to tell), but it needs to stay below 5 watts for 2 minutes (as per your settings). It seems like it jumps back up before the 2 minutes are up, so the condition is only met at the very end of your cycle, which counts as 1 instance.
Since the automation is waiting for a second instance that never occurs, you likely don’t receive a notification. Reducing the count to 1 should resolve the issue.
Let us know how you go.
Blacky
Hi Blacky,
Thanks for building this! Really love all the options of this blueprint.
I seem to be having trouble with the end notification (start notification worked).
When I look at the trace timeline I see the following message.
Stopped because only a single execution is allowed at October 1, 2024 at 9:20:05 AM (runtime: 0.00 seconds)
Seems like it ran the Custom End action as my input_select was set to finished just like I configured it to, however I never received the End notification message.
I checked the logs but didn’t find anything in there that pointed out what happened exactly.
Please let me know if I can supply any more information to help troubleshoot this issue.
P.S. I do have Power tracking (end notify consumption+cost) and Duration tracking enabled for the end notification.
Thank you.
Been playing around with this for several hours now and I found that anytime I have a custom end action, the automation always gets stuck.
It waits for the dead zone (5 minutes) then goes to option 2, which appears to be waiting for the appliance to finish (End Power Time Delay). I have this set to 1 minute.
I’ve tried changing that value but still if there is anything in the custom end actions, it will not complete. I have to disable the custom end action and remove any custom actions, then change the value of End - Power time delay for an end notification to come through.
the message in your trace is okay.
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.
Blacky
Hey Blacky,
Thanks for getting back with me. Here is the automation
alias: Washing Machine Notification
description: ""
use_blueprint:
path: Blackshome/appliance-notifications.yaml
input:
end_power_consumption: input_number.washing_machine_end_kwh
power_sensor: sensor.washerpm_power
start_appliance_power: 5
start_time_delay: 2
running_dead_zone: 5
end_notify_device:
- f05dc6e964eb668db031e27688c49c0e
end_message: Washing machine has finished!
end_notify_data:
- channel
end_notify_channel: laundry
end_reminder_notification: enable_reminder_notification
end_reminder_notification_entity: binary_sensor.washer_contact
include_duration_tracking: disable_duration_tracking
include_power_tracking: enable_power_tracking_and_cost
power_consumption_sensor: sensor.washerpm_daily_energy
cost_per_kwh: input_number.electricity_rate
start_power_consumption: input_number.washing_machine_start_kwh
end_custom_actions:
- action: input_select.select_option
metadata: {}
data:
option: Finished
target:
entity_id: input_select.washing_machine
include_end_notify: enable_end_notify_options
include_custom_actions:
- enable_start_custom_actions
start_custom_actions:
- action: input_select.select_option
metadata: {}
data:
option: Running
target:
entity_id: input_select.washing_machine
include_start_notify: enable_start_notify_options
start_notify_device:
- f05dc6e964eb668db031e27688c49c0e
start_notify_data:
- channel
start_notify_channel: laundry
end_time_delay: 1
include_watchdog: disable_watchdog
include_time: time_disabled
end_repeat_count: 1
weekday_options: []
end_appliance_power: 5
Hi Drewski,
Thanks for you YAML. I have tested it here with the start and end custom actions changing the input select from running to finished and it worked perfectly.
This is interesting, it looks like it is in your power settings.
- You get the start notification so that is all good.
- You have a running dead zone of 5 min. Once started the automation will sit there for 5 min and do nothing, will not look at any power settings. Is this what you would like?
- Then your end power must go from above 5 watts to below 5 watts and stay below for 1 min to receive your end notification.
I think your running dead zone could be the problem… maybe when the 5 min is up the end power is already below for 5 watts… it has to go from above 5 watts to below 5 watts for 1 min as per your settings.
It must be in the power settings. Have a close look at them.
Blacky
Hello Blacky, that was indeed what needed to be modified ! Thanks again for this great template 
1 Like