I have checked it here with iOS and Android and I got the message. Are you using android or iOS?.
That trace is showing that it is waiting for it to drop below 1 watt for 1 min not time. Look back on the trace line. It can be confusing.
I use iOS 17.6 (latest). All other notifications come trough.
It hasnāt dropped below 1 watt. Look at the time notes in the trace you will see āThis step was not executed and so no further trace information is available.ā it waiting for the power to drop. iOS will come through.
Your at this point on your trace line.
Check.
With the time limits set to 0,25 (both start and end) i could trigger it with the Developers tools ā State setting it to over the minimum limit. Got the notifications! So it is workingā¦
Thank you for your quick reply and problem solving. My bad for not thinking about the State setting before.
Keep up the good work!
Nice one glad you got it up and running again
HAPPY DAYS!!
Blacky
Hi. This uses to work, but does not fit my washer or dryer. They are producing watts. I also notice nothing happens when I press run. I am running 2.3
alias: "Appliance: Washer Finished"
description: ""
use_blueprint:
path: Blackshome/appliance-notifications.yaml
input:
power_sensor: sensor.washing_machine_electric_consumption_w
include_end_notify: enable_end_notify_options
end_notify_device:
- 82efe31776fb16cca3166c33f756fef5
- 1cfea90cb9e83023f6859604452adeb5
end_notify_interruption_level: time-sensitive
include_watchdog: disable_watchdog
watchdog_timeframe:
hours: 1
minutes: 30
seconds: 0
watchdog_notify_interruption_level: time-sensitive
include_custom_actions: []
end_custom_actions:
- metadata: {}
data:
entity_id: media_player.sonos_first_floor
message: Washer is finished
action: tts.cloud_say
- metadata: {}
data:
value: "{{ state_attr('media_player.sonos_first_floor', 'volume_level') }}"
target:
entity_id: input_number.media_player_volume_backuo
alias: Get the current volume
enabled: false
action: input_number.set_value
- metadata: {}
data:
volume_level: "{{ states('input_number.media_player_volume_backup') | float }}"
target:
entity_id: media_player.sonos_first_floor
enabled: false
action: media_player.volume_set
end_message_title: Washer done!
end_message: Yippee the washing machine is finished!
watchdog_message: Uh-oh! Time to check the washer.
include_duration_tracking: disable_duration_tracking
include_start_notify: enable_start_notify_options
start_notify_device:
- 1cfea90cb9e83023f6859604452adeb5
- 82efe31776fb16cca3166c33f756fef5
start_notify_data:
- channel
- sticky
end_appliance_power:
Looks like you were editing the automation in YAML. There is a missing input. Adjust the End - Appliance Power Setpoint to your liking.
end_appliance_power: 5
Full code for you
alias: "Appliance: Washer Finished"
description: ""
use_blueprint:
path: Blackshome/appliance-notifications.yaml
input:
power_sensor: sensor.washing_machine_electric_consumption_w
include_end_notify: enable_end_notify_options
end_notify_device:
- 82efe31776fb16cca3166c33f756fef5
- 1cfea90cb9e83023f6859604452adeb5
end_notify_interruption_level: time-sensitive
include_watchdog: disable_watchdog
watchdog_timeframe:
hours: 1
minutes: 30
seconds: 0
watchdog_notify_interruption_level: time-sensitive
include_custom_actions: []
end_custom_actions:
- metadata: {}
data:
entity_id: media_player.sonos_first_floor
message: Washer is finished
action: tts.cloud_say
- metadata: {}
data:
value: "{{ state_attr('media_player.sonos_first_floor', 'volume_level') }}"
target:
entity_id: input_number.media_player_volume_backuo
alias: Get the current volume
enabled: false
action: input_number.set_value
- metadata: {}
data:
volume_level: "{{ states('input_number.media_player_volume_backup') | float }}"
target:
entity_id: media_player.sonos_first_floor
enabled: false
action: media_player.volume_set
end_message_title: Washer done!
end_message: Yippee the washing machine is finished!
watchdog_message: Uh-oh! Time to check the washer.
include_duration_tracking: disable_duration_tracking
include_start_notify: enable_start_notify_options
start_notify_device:
- 1cfea90cb9e83023f6859604452adeb5
- 82efe31776fb16cca3166c33f756fef5
start_notify_data:
- channel
- sticky
end_appliance_power: 5
Blacky
Thanks, yes, was copying and pasting from my phone (nightmare). Got it working now, thanks!
Somehow the blueprint is not triggering for me. Iām using a smart plug to track the power usage of my dryer. The automation should trigger above 20W and it clearly goes above that threshold:
The settings:
alias: Wasdroger is klaar
description: ""
use_blueprint:
path: Blackshome/appliance-notifications.yaml
input:
power_sensor: sensor.plug_droger_power
end_appliance_power: 10
include_watchdog: disable_watchdog
watchdog_timeframe:
hours: 3
minutes: 30
seconds: 0
watchdog_notify_data:
- high_priority
include_custom_actions:
- enable_end_custom_actions
end_custom_actions:
- data:
message: Wasdroger is klaar!
title: Wasdroger š¤
action: notify.notificatiegroep
start_appliance_power: 20
running_dead_zone: 1
watchdog_message: Uh-oh! Time to check the dryer
watchdog_custom_actions: []
include_duration_tracking: disable_duration_tracking
Iām guessing the condition is not matching somehow when I test it by taking control:
Edit: the time option has been disabled:
I have tested your YAML here and it works. I did not test your end custom action though. Remember it must go from below 20W to above to trigger the automation and you have set 1 min that it must be above. You then have a 1 min dead zone and then when if finishes it must go below 10W for 1 min to trigger your end action.
I do not support take control.
Blacky
Hy Blacky, thank you for your quick response. I used take control to debug the triggers. No changes of course
I think the automation didnāt trigger because I accidentally chose the wrong entity (total kwh used vs watts in use at this moment - power). If I test it by running the dryer again it seems to trigger.
Thanks for all the hard work!
Hey,
First of all, thank you for developing this blueprint.
I have an issue with the finish notifications that are being sent incorrectly due to another automation that switches off the appliance during peak times.
Due to the appliance being switched off, the energy use obviously goes to zero, which meets the blueprint conditions of the appliance finished.
Is there a way to stop the finish notification if the appliance is switched off?
Regards
Dave
Hi Dave and welcome to the community.
The automation must start to receive the end notification. Make sure your start it a true start, then when you just turn it OFF it will not send the notification.
Blacky
Is it possible to use Telegram for notifications?
I know that I can use ātake controlā to modify the automation, but I donāt prefer to do so.
Update: I missed the custom end action, will use that to send the same message (template) as being used for the main message.
Update2 on this; it is working great!
Hey Blacky, thanks so much for this blueprint - it was really plug and play without any issues for me and allowed me to skip a lot of figuring things out.
I do however have one request: is it possible to add tag and notification_icon support for the start and end notifications? Or perhaps just a dictionary style input to extend the notification data, whichever is easier.
On Android that would allow superseding the HomeAssistant icon on the Lockscreen notifications (e.g. with a washing machine) and automatically replacing start with end notification if not already dismissed instead of showing both.
Itās purely cosmetic and not worth ātaking controlā or pumping everything through custom actions right now, but it would be a very welcome addition
Hi Eric,
Welcome to the community.
Yes, you can use the custom actions to include anything you like in your notifications. I will also add it to the suggestion listā¦ thanks for your input.
Blacky
@Blacky
Bug Report (I think):
I got this from HA logsā¦
Logger: homeassistant.helpers.template
Source: helpers/template.py:2651
First occurred: 11:41:45 AM (29 occurrences)
Last logged: 2:46:35 PM
Template variable warning: 'watchdognotify_data' is undefined when rendering... etc.
Searching the blueprint watchdognotify_data
only appears once on line 822 in my downloaded version, and line 738 on your github version (first time Iāve noticed how different the local downloaded file is).
Looking at the rest of the script Iām pretty sure that itās supposed to be watchdog_notify_data
.
Cheers.
Thanks Rick,
Your 100% correct. I can see the code is wrong but I cant test it until I get back from Holidays. I have updated it already as I know it is wrong.
Thanks for doing the leg work and for letting us know
If you would be so kind to update the blueprint to version 2.4 and let us know if it is all resolved.
Thanks again for your help!
Blacky