Notify or do something when an appliance like a dishwasher or washing machine finishes

Blueprints Exchange
, ,
110

I’m having the exact same issue. Do you have any solution?

111

I’m also running into an issue that might be a little different.

Whithout changing anything in my automation I’m getting the error:

image
image699×83 8.42 KB

Any ideas?

112

I was not able to solve problem (tried with different values and platforms) so had to use completely diffent solution for achieving this.

113

Which solution did you use, i also want to implement such notifications.

114

Thanks @Rod_Poplarchick for the blueprint and @Xelloss99 for showing me how to tweak it for the smartthings multipurpose sensor! Works great! I’ve been looking at how to do this for a long time, since I, like some others, can’t use the energy monitor for the dryer. Thanks!

115

I’m on the latest HAOS on RPi and have the following issue when adding the blueprint (I used the “Import Blueprint” button in this thread!):

Message malformed: Missing input pre_actions

I’ve tried with several sensors and actions, but always the same result.

Anyone know how to fix this? Thanks!

grafik
grafik1707×1273 176 KB

3 Likes
116

Getting the same error as above, “Message malformed: Missing input pre_actions” no mater what I select.

117

The error Message malformed: Missing input pre_actions is related to the recent update of the blueprint, adding the second action block for an action when the starting threshold is crossed. If you do not have a valid action there, you’ll receive the error above.

I was able to get around it by selecting “Wait for time to pass” and leaving the duration set to 0.

1 Like
118

Hi @Sbyx

first of all, many thanks for that nice blueprint which (almost) fit my needs.
However, would it be possible to make those wattage selections more granular, means 0.5 steps instead of 1.0?

Background of this requirement is that I’d like to switch off a device (Sat-IP Server namely) after it has been in idle mode for a while.
Therefore I have to define the power threshold to something like below 14.5W, but above 14.0.

Many thanks!

119

Just type what you want into the box to the right of the slider or click on the 3 dots and go edit in YAML and type in the value you want at the right spot.

120

This fixed it! Thank you!

121

I am also getting this error now and have not changed anything.

122

WAF dropped to 0

123

The blueprint doesn’t import in 2022.05 and 2022.05.01 because of a bug:

The workaround is to place the file from the gist manually in the config/blueprint folder.

There will be a fix in 2022.05.02: Stringify enums in selectors by balloob · Pull Request #71441 · home-assistant/core · GitHub

124

I am not seeing “the forest for the trees”
I have set the power sensor menu item.
I left all the starting and finishing items as shown because that shuld work for me.
I then created an action to notify me.
The following is the yaml produced.
I do not see where any trigger info comes in to play.
What have I missed.

- id: '1651783438816'
  alias: Appliance has finished
  description: ''
  use_blueprint:
    path: sbyx/notify-or-do-something-when-an-appliance-like-a-dishwasher-or-washing-machine-finishes.yaml
    input:
      power_sensor: sensor.dishwasher_watts
      actions:
      - service: notify.brooks5123
        data:
          message: dw done
          title: dw done
      pre_actions:
      - delay: '0'

Thanks

125

Carlton, you write, if I understand correctly, that you left the starting and finishing thresholds to the defaults, and that’s why they’re not showing up in the generated yaml. If you’d changed them, they would show up as starting_hysteresis, starting_threshold, finishing_hysteresis, finishing_threshold, a bit like this:

- id: '1651783438816'
  alias: Appliance has finished
  description: ''
  use_blueprint:
    path: sbyx/notify-or-do-something-when-an-appliance-like-a-dishwasher-or-washing-machine-finishes.yaml
    input:
      starting_hysteresis: 1
      finishing_hysteresis: 1
      starting_threshold: 6
      finishing_threshold: 6
      power_sensor: sensor.dishwasher_watts
      actions:
      - service: notify.brooks5123
        data:
          message: dw done
          title: dw done
      pre_actions:
      - delay: '0'

The rest of the fun happens in code that is in the blueprint - you can click on the gist to read it and see how it works.

126

Thank you for the information.
I thought that I would try it with the defaults listed but now I know they need to be changed.
Will try it and see what happens.
Thanks

127

@Sbyx: I was wondering if you would add those triggers:

- platform: event
  event_type: automation_reloaded
- platform: homeassistant
  event: start

I think that would easily and finally make automations based on this blueprint work if
a) automations have been reloaded
b) HA has been restarted

Both cases/events rendered my automations based on this blueprint useless during the last years, cause they “forgot” their starting_threshold and starting_hysterisis have been crossed already (the automation has been triggered already and is/was running). In short: currently this blueprint is not able to survive reloading automations. Possibly those additional triggers will fix this (and make my additional “failsafe automation” useless).

I primarily use this blueprint to make my working desk power plug been switched off automatically after system has been shutdown/hibernated/removed.

(see my report from March and April 2021… Notify or do something when an appliance like a dishwasher or washing machine finishes - #54 by e-raser + Notify or do something when an appliance like a dishwasher or washing machine finishes - #55 by e-raser)

UPDATE after 7 days of testing:
3 minor modifications and this blueprint finally works perfectly. See Notify or do something when an appliance like a dishwasher or washing machine finishes - #133 by e-raser for details.

1 Like
128

@e-raser I think I might have the solution! You could give my blueprint a try!

129

Thank you. While I basically don’t like the approach of “outsourced configuration data” (by using helper entities as config parameters instead of handling all inside the blueprint/automation which is much more tidy and centralized) I will have a look at your blueprint. It looks like a very very VERY powerful one. Interesting is the external “only Italian” HA Power Control part :smiley: I don’t even get what it does, will probably head over to Google Translate to do the IT/EN or IT/DE job :wink:

I’m really quite happy with @Sbyx ones blueprint here, actually it works perfect… as soon as the bug/optimization noted here has been fixed/implemented :slight_smile: :+1:

1 Like