Thanks for the info! For this option, weāll need to use tags. What tags allow us to do is replace the old notification with your new message. Iāll then create an option to clear the message when the Reminder Notification Entity is used. That way, others will know itās been handled. I might even add a little extra flairā¦ but youāll have to wait and see!
All good on the coding sideā¦ easy enough to do. But thanks for offering to help!
Blacky 
Hi, I am using your blueprint for my washingmachine, dishwasher etc, and they all work great!!
Now I wanted to create one for my carcharger. All the other appliances are connected to smartplugs, the charger is not.
Still, I have power sensors, energy sensors, so I thought this would be possible to set up.
But for some reason itās not working.
Here is my yaml-code:
alias: Easee laadsessies
description: ""
use_blueprint:
path: Blackshome/appliance-notifications.yaml
input:
power_sensor: sensor.25_vermogen
include_start_notify: enable_start_notify_options
start_notify_device:
- a529b70b25db87bd10e8ba76bad4879f
start_title: Easee Laadpaal
start_message: Laden R5 is gestart.
include_end_notify: enable_end_notify_options
end_notify_device:
- a529b70b25db87bd10e8ba76bad4879f
end_message: Laden R5 is gestopt.
end_message_title: Easee Laadpaal
include_power_tracking: enable_power_tracking_and_cost
end_message_cost: Stroomkosten ongeveer ā¬
include_duration_tracking: enable_duration_tracking
end_message_duration_tracking: Duur
include_cycle_counter: enable_cycle_counter_and_notify
cycle_counter_end_message: Totaal aantal laadsessies
power_consumption_sensor: sensor.25_levensduur_verbruik
end_message_kwh: Verbruik Laadpaal
cost_per_kwh: sensor.actueel_energietarief
start_power_consumption: input_number.easee_laadpaal_start_kwh
end_power_consumption: input_number.easee_laadpaal_einde_kwh
cycle_counter_helper: counter.easee_laadpaal_uses
include_custom_actions: []
end_custom_actions:
- if:
- condition: state
entity_id: sensor.25_stroom
attribute: state_inCurrentT2
state: "0"
for:
hours: 0
minutes: 5
seconds: 0
then:
- action: counter.increment
metadata: {}
data: {}
target:
entity_id: counter.easee_laadpaal_uses
enabled: false
end_appliance_power: 10
start_notify_data:
- high_priority
end_notify_data:
- high_priority
Could you have a look and tell me where I go wrong.
sensor.25_vermogen = power in kW. (session)
sensor.25_levensduur_verbruik = energy in kWh (accumulative)
Thanks!
No, I havenāt. So itās best to use that one I guess? Iāll have a look, thanks.
Yes, as it is more tailored for charging batteries, maybe even cars. Let me know if you need any help on that thread or if you have any suggestions.
Blacky
Watts your appliance up to, youāre always in the know from start to finish! 
New Features
Notification Tags - Use a tag to keep your notifications organized. When a new notification with the same tag is sent, it replaces the old one, preventing clutter from multiple notifications for the same appliance.
Reminder Notification Options - Added two new options:
Enable Reminder Notification + Notify When Done: Receive repeated reminders until the Reminder Notification Entity is ON or the maximum notification count is reached. When the entity turns ON, a one-time notification will be sent using the Notify When Done Message.
Enable Reminder Notification + Clear When Done: Receive repeated reminders until the Reminder Notification Entity is ON or the maximum notification count is reached. When the entity turns ON, the notification will be cleared.
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
Great blueprint here. Is it possible to add support for the notification timeout value and the notification icon on the android side? I can takeover the blueprint and add it manually in the notification section, but it would be nice to have it built-in.
Using the ātake overā option often defeats the purpose of blueprints, which are designed to be reusable, manageable, and updatable, without needing to dive into custom YAML unless absolutely necessary. Once someone uses ātake over,ā they:
ā¢ Lose automatic updates
ā¢ Risk breaking changes when modifying internal logic
ā¢ Often end up duplicating blueprint features unintentionally
Iāve never been a fan of this option.
Instead, I recommend using custom actions. They offer the flexibility to add personal logic while still preserving all the benefits of the blueprint model, including versioning, structure, and future-proofing.
That said, thanks for your suggestion and it has been noted in the list.
Blacky
Did you have a chance to look at this. So one can set a custom notification icon?
I couldnāt find it in the change logs between 2.8 (where I made the changes and 3.2)
Thanks for the reply! Iām aware of the ramifications of ātaking overā, and Iām aware of the custom actions. I use custom actions already to set booleans and timers for other things. Custom actions donāt fire when the reminder notifications go out though, so in this case it would not be useful (except for the one-time notification) unless I rewrote the reminder notifications logic all within a custom action. Hence my request for the additions. 
