Your welcome, thanks for letting us know.
Blacky 
1 Like
I think this is the problem, thank you:
When I use the slider it makes a comma, no Point. I can adjust it manually.
Your welcome.
You must of typed it in. As if you type it in then adjust the slider it will give you a point only not a comma. The main thing is you got it working.
Blacky
Dear Developer,
First, thank you for creating the Appliance Notifications & Actions Blueprint for Home Assistant! It has significantly streamlined notifications and actions for my appliances. However, I encountered a limitation that I hope can be addressed in a future update.
Currently, the Reminder Notification Entity only supports binary_sensor entities. This poses a challenge for users like me who rely on other entities, such as input_boolean, to manage states. Specifically, I use a Zigbee smart plug to monitor the power state of my washing machine. To handle reminders, Iāve set up an input_boolean as a helper to track when the machine is done and the plug is turned off (indicating that the laundry has been removed). Unfortunately, the Blueprint doesnāt recognize input_boolean entities, forcing me to create a binary_sensor template as a workaround.
Adding support for input_boolean as a valid Reminder Notification Entity would:
- Simplify setup for many users who rely on helpers.
- Reduce the need for additional template sensors and YAML configurations.
I believe this enhancement would make the Blueprint even more versatile and accessible. Thank you for considering this feature request, and I appreciate your continued work on improving the Home Assistant ecosystem.
Is there a variable available for the duration?
I want to send a notification via pushover, so I use the custom action for the start and end, but I want to add information on the duration.
I just want to say thank youā¦ this automation is great BUT one little quirk which threw me off, may not throw others since I am a bit well versed in electrical terms. The first entry says to enter current draw BUT in reality you are looking for wattage. I blindly entered the current draw (measured by a watt meter and clamp) and it did not work right. I returned and looked again and noticed that next entry asked for the setpoint in WATTS not AMPS. I thought the blueprint did P=IxE in the background but said OK letās try this so I entered WATTS vs AMPS under the power sensor settingā¦ and it WORKED! You know this ONE blueprint for the washer made a wife who thought HA was nice but meh (lighting)ā¦ think OK yea I am in go ahead keep going! 
Now I got garage door sensors, garage door openers, water leak sensorsā¦etc etc. Now I got to figure out what to use to monitor a dryer vs having to swap out the breaker for a smart one.
For the Reminder Notification Entity, weāre looking for a sensor to turn ON as an acknowledgment that someone has taken actionāsuch as opening a door using a contact sensor or triggering a motion sensor in the laundry room to indicate the task is complete.
Regarding the input_boolean helper youāre using to track when the machine is done: does it turn ON when the plug is turned OFF? If so, you can copy and paste the entity ID of your helper into the input field, and it should appear and function correctly. Could you try this and let us know how it works?
Blacky
Hi Mario,
This is what you would add to your message. The name Duration is from Duration Tracking - End Message - Duration input.
message: >-
{% set end_time = now().timestamp() %} {% set duration = (end_time -
start_time) | int %} {% set hours = (duration // 3600) | int %} {% set
minutes = ((duration % 3600) // 60) | int %}{% set seconds = (duration % 60)
| int %}{{'\n'}} {{ end_message_duration_tracking }} {{ '%02d' |
format(hours) }}:{{ '%02d' | format(minutes) }}:{{ '%02d' | format(seconds)
}}
This is if you would like to edit the name duration in the message and not use the Duration Tracking - End Message - Duration input.
message: >-
{% set end_time = now().timestamp() %} {% set duration = (end_time -
start_time) | int %} {% set hours = (duration // 3600) | int %} {% set
minutes = ((duration % 3600) // 60) | int %}{% set seconds = (duration % 60)
| int %}{{'\n'}} Duration {{ '%02d' |
format(hours) }}:{{ '%02d' | format(minutes) }}:{{ '%02d' | format(seconds)
}}
Blacky
1 Like
Yes your correct current = amps, maybe I should of used the word Power but I glad you got it working.
We just use smart plugs, just make sure the one you select has power / energy motoring.
Blacky
I doā¦ but for the washer. I have yet to see a 240v smart plug let alone do I know if any can handle the current for the electric dryer with enough leeway to keep it cool vs right at itās maximum current the whole time. The wife has a habbit of doing 4-5 loads in a row so that can get pretty warm drawing that much for long periods of time.
Yea, all depends on your dryer. Ours dryer only goes to max 1000 watts as it is an inverter dryer but if you have an old style dryer thenā¦ You should find 240V smart plugsā¦ ours go to max load 2300W.
You could also use a Shelly EM Gen3 if this helps you.
Blacky
I am walking before running. 
I have only been at this for about 2 months now but itās on my short list. I got to read the specs on the dryer which is only about 3-4 months old and also place a clamp on it to verify everything. BUT thanks for the suggestion, I have 2 Shelly products and they seem well made. Wish they made a wider variety.
Ahh Europeā¦ I looked at the product but seems to be for the EU. I tried going to the US site and page not found so I got to see if there is a similar product for the US market.
1 Like
I see the end and start custom actions are only fired when the start and/or end notification is enabled (I see that in the trace), why is that?
Looked into it, have the following in the trace:
choose:
- alias: Check if start of notification is enabled
conditions:
- '{{ include_start_notify == ''enable_start_notify_options'' }}'
sequence:
- alias: Send a notification to each device
repeat:
for_each: []
sequence:
- action: >-
notify.mobile_app_{{ device_attr(repeat.item, 'name') | slugify
}}
data:
title: Wasdroger
message: Yes, we zijn weer gestart!
data: '{{ start_message_data }}'
So, I donāt want a notification to a device via the default notifications, but since I need to pick a device, otherwise the loop doesnāt fire it doesnt work with my custom action. I think this part of the blueprint needs to be changed, so on every end or start situation the custom action should be fired once.
You donāt need to enable the start or end notificationā¦ all you need to do is enable the start and end custom actions.
Blacky
A, I see my mistake in reading it, see below snippet, I still donāt get the message, but in the trace I see this part is executed
i have the checkmark checked
choose:
- alias: Perform the custom start action
conditions:
- condition: template
value_template: '{{ ''enable_start_custom_actions'' in include_custom_actions }}'
sequence:
- event: ''
event_data:
action: notify.pushover
metadata: {}
data:
message: Wasmachine is gestart
UPDATE: Sorry, I feel so stupid, I created a manual action to add the event_data, but had to use the default action from the menu for using pushover and that works like a charm
Can you tell me where I set the start_time?
Returned everything to the original and created the helpers for energy prices and start and end consumtion.
Really want to move to the notifications of the pushover, but kinda stuck in setting up the custom message with energy usage and duration. If someone can help me with that, that would be great.
The reason is the power usage of the home assistant app on my phone
Hi Mario, sorry I am not following you. There is no start timeā¦ everything is triggered with the Power Settings.
You will need to Enable - Update of Start & End Helpers Only and Enable - End Notify Duration Tracking if your only using a custom action.
Below is your end message used in the end custom action.
message: >
Your end message here
{% set kwh = states(end_power_consumption) | float - states(start_power_consumption) | float %}
{{'\n'}}{{end_message_kwh}} {{kwh | round(2) }} kWh
{% set cost = (states(end_power_consumption) | float - states(start_power_consumption) | float) * (states(cost_per_kwh) | float) %}
{{'\n'}}{{end_message_cost}}{{cost | round(2) }}
{% if include_duration_tracking == "enable_duration_tracking" %}
{% set end_time = now().timestamp() %}
{% set duration = (end_time - start_time) | int %}
{% set hours = (duration // 3600) | int %}
{% set minutes = ((duration % 3600) // 60) | int %}
{% set seconds = (duration % 60) | int %}
{{'\n'}}Duration {{ '%02d' | format(hours) }}:{{ '%02d' | format(minutes) }}:{{ '%02d' | format(seconds) }}
{% endif %}
Blacky
can you tell me what Iām doing wrong?
set the tracking correctly enabled and this is my custom end message, but when I run the action I got the error:
or is it because I cant test it individually?
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
1 Like