Trigger on Washing Machine finish

Configuration
11

The input_selector is used to indicate the washer’s current operating phase:

      - 'stop'
      - 'wash fill'
      - 'wash'
      - 'wash spin'
      - 'wash drain'
      - 'rinse fill'
      - 'rinse wait'
      - 'rinse'
      - 'rinse spin'
      - 'rinse drain'
      - 'unknown'
      - 'soak'

When the machine is washing it uses between 320 and 420 watts (depends on whether it was set to hand-wash, regular, or heavy-duty). When it’s spinning/draining it’s between 335 and 525. Similarly, when rinsing it’s between 310 and 380. All of these power ranges overlap so if it’s currently reporting 350 watts, is it washing, spinning, or rinsing? You can’t tell the difference, all you can say is it’s in a “run” phase.

The automation’s job is to interpret the Template Sensor’s changes of state into the actual operating phases and set the input_select accordingly. For example, when the Template Sensor changes from ‘stop’ to ‘fill’ that’s the initial filling of water for the wash phase so the input_select is set to ‘wash fill’. A change from ‘fill’ to ‘run’ means ‘wash’ phase has started. From ‘run’ to ‘pulse’ means ‘wash spin’ and so on and so on.

For notifications, I have an automation that checks when the input_select changes from ‘rinse drain’ to ‘stop’. That’s the last phase of the cleaning process.

I’ve also added detection for a ‘soak’ phase. Sometimes I set the machine to pre-wash, where it does a very short wash and then leaves the clothes soaking in the wash water. It remains in ‘soak’ phase until you set the machine to a normal wash. The problem is sometimes I forget and it soaks for an hour (or much longer). Now I’ve set an announcement to report when the machine is in ‘soak’ for more than 20 minutes.

12

Thanks for the elaborate explanation.

I might start with reliably reporting when the washer is done and then get into more elaborate analysis. Which means watching the sequence of cycles and matching them to the input selector sequence rather than just the final drop from 275 to 5 watts.

13

i used this code to get the state.
image

config

#               TP Link HS110 switch en energie    #
####################################################
tplink:
 switch:           
   - host: !secret ip_tplink_wasmashine
input_number: ######################################
  kosten_per_kw:
    name: Kosten per KW/h
    initial: 0.27
    min: 0
    max: 100
    step: 0.01
    mode: box
input_select: ######################################
 state_wasmachine:
  name: Wasmachine state
  icon: mdi:tumble-washingmachine
  options:
    - Standby
    - Voorwas
    - Spoelen
    - Wassen
    - Centrifugeren
    - Kreukbeveiliging
    - Klaar
    - Uit
sensor: ############################################
 - platform: template
   sensors:
     wasmachine_amps:
       value_template: '{{ states.switch.wasmachine.attributes["current_a"] | replace(" A", "") | float }}'
       unit_of_measurement: 'A'
     wasmachine_watts:
       value_template: '{{ states.switch.wasmachine.attributes["current_power_w"] | replace(" W", "") | float }}'
       unit_of_measurement: 'W'
     wasmachine_kw:
       value_template: '{{ states.switch.wasmachine.attributes["total_energy_kwh"] | replace(" kW", "") | float }}'
       unit_of_measurement: 'kW'
     wasmachine_volts:
       value_template: '{{ states.switch.wasmachine.attributes["voltage"] | replace(" V", "") | float }}'
       unit_of_measurement: 'V'   
     wasmachine_today_energy:
       value_template: '{{ states.switch.wasmachine.attributes["today_energy_kwh"] | replace(" kW", "") | float }}'
       unit_of_measurement: 'kW' 

 - platform: template
   sensors:
     wasmachine_kosten_dag:
       friendly_name: "wasmachine koster per dag"
       unit_of_measurement: '€'
       icon_template: mdi:currency-eur
       value_template: "{{ ((states('sensor.wasmachine_today_energy') | float) * (states('input_number.kosten_per_kw') | float)) | round(2) }}"
automation: ########################################
#                      Wasmashine detectie         #
#################################################### 
  - alias: wasmachine inschakelen
    trigger:
      platform: state
      entity_id: switch.wasmachine
      to: 'on'
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.state_wasmachine
          option: 'Standby'
  
  - alias: wasmachine uitschakelen
    trigger:
      platform: state
      entity_id: switch.wasmachine
      to: 'off'
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.state_wasmachine
          option: 'Uit'

  - alias: wasmachine net aan
    trigger:
     - above: 750
       entity_id: sensor.wasmachine_watts
       for: 00:01:00
       platform: numeric_state
     - platform: state
       entity_id:
         - input_select.select_option
       from: 'Standby' 
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.state_wasmachine
          option: 'Wassen'
      - service: tts.google_translate_say
        data:
          entity_id: group.all_tts
          message: 'Ga jij wat leuks doen? Dan doe ik de was. Als de washingmachine klaar is geef ik een seintje'

  - id: wasmachine_washing
    alias: 'Wasmashine - Wassen'
    trigger:
     - above: 750
       entity_id: sensor.wasmachine_watts
       for: 00:01:00
       platform: numeric_state
    action:
      - service: timer.start
        entity_id: timer.wasmachine
      - service: input_select.select_option
        data:
          entity_id: input_select.state_wasmachine
          option: 'Wassen'

  - id: wasmachine_wassen
    alias: 'Wasmashine - Spoelen'
    trigger:
     - above: 50
       below: 140
       entity_id: sensor.wasmachine_watts
       for: 00:02:00
       platform: numeric_state
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.state_wasmachine
          option: 'Spoelen'

  - id: wasmachine_centrifugeren
    alias: 'Wasmashine - Centrifugeren'
    trigger:
     - above: 140
       below: 750
       entity_id: sensor.wasmachine_watts
       for: 00:02:00
       platform: numeric_state
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.state_wasmachine
          option: 'Centrifugeren'

  - id: wasmachine_centrifugeren
    alias: 'Wasmashine - Centrifugeren'
    trigger:
     - above: 140
       below: 750
       entity_id: sensor.wasmachine_watts
       for: 00:02:00
       platform: numeric_state
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.state_wasmachine
          option: 'Centrifugeren'

  - id: wasmachine_ready
    alias: 'Wasmashine - klaar'
    trigger:
     - above: 3
       below: 30
       entity_id: sensor.wasmachine_watts
       for: 00:02:00
       platform: numeric_state
    action:
      - service: timer.cancel
        entity_id: timer.wasmachine
      - service: input_select.select_option
        data:
          entity_id: input_select.state_wasmachine
          option: 'Klaar'
      - service: tts.google_translate_say
        data:
          entity_id: group.all_tts
          message: 'De wasmachine is klaar. Je kan energie besparen door hem uit te zetten.'

  - id: wasmachine_standby
    alias: 'Wasmashine - standby state'
    trigger:
     - below: 3
       entity_id: sensor.wasmachine_watts
       for: 00:02:00
       platform: numeric_state
    action:
     - service: input_select.select_option
       data:
         entity_id: input_select.state_wasmachine
         option: 'Standby'

Lovelace wasmachine card

elements:
  - entity: switch.wasmachine
    icon: 'mdi:flash-circle'
    tap_action:
      action: toggle
    style:
      right: 0.5%
      top: 6%
      '--paper-item-icon-color': green
    type: state-icon
  - type: state-label
    entity: input_select.state_wasmachine
    style:
      color: white
      font-size: 10px
      left: 50%
      top: 6.5%
  - type: state-label
    entity: sensor.wasmachine_watts
    style:
      bottom: 9%
      left: 6%
      font-size: 10px
      color: gray
      font-weight: 400
      transform: none
      max-width: 1px
  - type: state-label
    entity: sensor.wasmachine_today_energy
    style:
      bottom: 3%
      left: 6%
      font-size: 14px
      color: gray
      font-weight: 400
      transform: none
      max-width: 1px
  - type: state-label
    entity: sensor.wasmachine_kosten_dag
    style:
      bottom: 3%
      left: 40%
      font-size: 14px
      color: gray
      font-weight: 400
      transform: none
      max-width: 1px
image: local/wasmashine.png
type: picture-elements

Lovelace price card

type: entities
entities:
  - entity: input_number.kosten_per_kw
1 Like
14

Thank you for laying this out, just have a couple of questions.
I was able to translate all state option but these.
- Kreukbeveiliging (wrinkle/crease)
- Klaar (clear)
- Uit
Looked them up on the translate platform but not sure how they apply to laundry.
Also how are the states determined to start with.
Thank you
carltonb

1 Like
15

i hope i dit the translation oké

options:
- Standby = Standby (power plug turn on but washing machine off)
- Voorwas = Prewash
- Spoelen = Rinse
- Wassen = Washing
- Centrifugeren = Spin
- Kreukbeveiliging = wrinkle protection
- Klaar = Done
- Uit = Off (power plug turn off)

16

That is perfect, thank you.

17

Hello @ielbury,

I am trying your code, but it is not triggering the automation. Please check where I am making mistake. Thanks

I am testing by setting “for” time to 30 seconds.

- id: '1622563811541'
  alias: 'Washing Machine automation '
  description: ''
  trigger:
  - platform: numeric_state
    entity_id: sensor.sonoff_1000f417f4_power
    attribute: power
    for: 00:00:30
    above: '1'
  condition: []
  action:
  - wait_for_trigger:
    - platform: numeric_state
      entity_id: sensor.sonoff_1000f417f4_power
      below: '.3'
      for: 00:00:30
      attribute: power
    continue_on_timeout: false
  - service: tts.google_translate_say
    data:
      message: wash is done
      entity_id: media_player.bedroom_speaker
  - service: switch.turn_on
    target:
      entity_id: switch.lt_washroom_sw1
  - service: tts.google_translate_say
    data:
      entity_id: media_player.kitchen_speaker
      message: wash is done
  - service: notify.mobile_app_iphone
  mode: restart

update: Code is working fine. Not sure what happened in start but now it’s working fine without any change.

18

Can above and below be in single quotes ?
I would leave a number without it, I guess it’s a string then.

19

This code generated by Home Assistant GUI. I have added automation from GUI and copied code from automation.yaml file. So syntax is correct.

20

OK… Are you sure it’s not triggered ? Or that it is but never pass the wait_for_trigger next ?
Do you see it running ? Are there traces ?
What should it do. I understand that :
it should run when power is above 1 (W ?)
then it wait 30s max until consumption drops bellow .3 (W again ?)
But does this actually happen ? Ain’t that too short so it doesn’t ever continue ?

21

Hello,

It work some times and mostly not.
The above code was for test only so I set short times to check settings. Here is my final configuration.

I want to get google home device announce that wash is done. For this I have set following as my understanding.

  1. When machine starts, it takes 2- 5 watts while you set timer etc.
  2. When machine start washing it takes around 190-230 watts until completed.
  3. in between, it takes 6-5 watts again for water drain and refill.

So I have set that if machine take power more than 1 watt for atleast 10 minutes or more. It should trigger and added condition that power must be less than .3 for 30 seconds to run actions.

Because when machine is started, it takes more than 1 watt. and when it complete it takes 0 watts.

Now its not running and I don’t know why. Is there any way to troubleshoot? So I am making any mistake in my configuration?

Please advice.

- id: '1622563811541'
  alias: 'Washing Machine automation '
  description: ''
  trigger:
  - platform: numeric_state
    entity_id: sensor.sonoff_1000000_power
    attribute: power
    for: 00:10:00
    above: '1'
  condition: []
  action:
  - wait_for_trigger:
    - platform: numeric_state
      entity_id: sensor.sonoff_1000000_power
      below: '.3'
      for: 00:00:30
      attribute: power
    continue_on_timeout: false
  - service: media_player.volume_set
    target:
      entity_id:
      - media_player.kitchen_speaker
      - media_player.bedroom_speaker
      - media_player.office_speaker
    data:
      volume_level: 1
  - wait_template: 00:00:15
  - service: tts.google_translate_say
    data:
      message: washing done
      entity_id: media_player.bedroom_speaker
  - service: tts.google_translate_say
    data:
      entity_id: media_player.kitchen_speaker
      message: washing done
  - service: notify.mobile_app_iphone
    data:
      title: Washing is done
      message: Take of the cloths from machine
  - service: switch.turn_off
    target:
      entity_id: switch.sonoff_1000000
  mode: restart
22

It’s hard to tell.
Note that “above 1 for 10mn” means that the power must not drop under 1W for the whole 10mn to trigger.
Same for “below .3 for 30s”. So if there is only 1 instance of a 1.1W after 9:59, then it won’t trigger.
I’ve not chosen to go this way, but used a larger value (30W) no delay to detect beginning.
And then an higher value (3W) for a longer time (5mn) to detect end of cycle.

23

Hi, I like your code. But don’t know what is this, another helper?
“service: timer.start
entity_id: timer.wasmachine”
In your write up not find it.

24

I have a plug with tasmota firmware, which values I have to change to integrate the switch.blitzwolf_shp6?

25

What “values” are you referring to?

26

Hey @charliesoap4,
I am a big fan of starting with a state machine, then build actual automations on top of that. A lot cleaner and feasible to maintain and extend over time.

input_select:
  waschmaschine_opstate:
    name: Waschmaschine OpState
    icon: mdi:washing-machine
    options:
      - "Off"
      - "Standby"
      - "Scheduled"
      - "Active"
      - "Finished"
    initial: "Off"

automation:
  - id: "1609362853001"
    alias: Regel Waschmaschine verbraucht 0.04W (Off)
    trigger:
      - platform: numeric_state
        entity_id: sensor.waschmachine_strommessgeraet_power
        below: 0.1
        for: "00:03:00"
    condition:
      condition: not
      conditions:
        - condition: state
          entity_id: input_select.waschmaschine_opstate
          state: "Off"
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.waschmaschine_opstate
          option: "Off"

  - id: "1609362853002"
    alias: Regel Waschmaschine verbraucht 0.4W (Standby)
    trigger:
      - platform: numeric_state
        entity_id: sensor.waschmachine_strommessgeraet_power
        above: 0.3
        below: 0.5
        for: "00:01:00"
    condition:
      condition: state
      entity_id: input_select.waschmaschine_opstate
      state:
        - "Off"
        - "Scheduled"
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.waschmaschine_opstate
          option: "Standby"

  - id: "1609362853003"
    alias: Regel Waschmaschine verbraucht 0.4W (Finished)
    trigger:
      - platform: numeric_state
        entity_id: sensor.waschmachine_strommessgeraet_power
        above: 0.3
        below: 0.5
        for: "00:01:00"
    condition:
      condition: state
      entity_id: input_select.waschmaschine_opstate
      state: "Active"
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.waschmaschine_opstate
          option: "Finished"

  - id: "1609362853004"
    alias: Regel Waschmaschine verbraucht >3W (Active)
    trigger:
      - platform: numeric_state
        entity_id: sensor.waschmachine_strommessgeraet_power
        above: 3.0
        for: "00:01:00"
    condition:
      condition: not
      conditions:
        - condition: state
          entity_id: input_select.waschmaschine_opstate
          state: "Active"
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.waschmaschine_opstate
          option: "Active"

  - id: "1609362853005"
    alias: Regel Waschmaschine verbraucht 2.9W (Scheduled)
    trigger:
      - platform: numeric_state
        entity_id: sensor.waschmachine_strommessgeraet_power
        above: 2.8
        below: 3.0
        for: "00:05:00"
    condition:
      condition: not
      conditions:
        - condition: state
          entity_id: input_select.waschmaschine_opstate
          state: "Scheduled"
    action:
      - service: input_select.select_option
        data:
          entity_id: input_select.waschmaschine_opstate
          option: "Scheduled"

  - id: "1609362853006"
    alias: Regel Waschmaschine fertig Benachrichtigung
    trigger:
      - platform: state
        entity_id: input_select.waschmaschine_opstate
        from: "Active"
        to: "Finished"
    action:
      - service: notify.mobile_app_thopn
        data:
          message: Die Waschmaschine ist fertig
          data:
            tag: waschmaschine
1 Like
27

How to link my switch.blitzwolf_shp6 to your sensor and automation

28

Try changing this line in the Template Sensor:

        {% set p = states('sensor.washer_power') %}

to this:

        {% set p = states('sensor.blitzwolf_shp6_energy_power') %}

It’s based on the assumption that your switch.blitzwolf_shp6 has an associated entity called sensor.blitzwolf_shp6_energy_power. If it’s called something else then use that name.

1 Like
29

This wouldn’t work for us, because we have different choices for the cycles.
I’d use something a lot simpler, like a pause for 5 minutes after a lot of power usage.

30

I’m quite sure we all do.
Why would what Taras posted not work?
I would say it should work on any type of washing program.