You're going to run into problems here because your washing machine stops frequently during the cycle. When it goes to fill and rinse, I would be surprised if the accelleration sensor reads anything. So, instead of getting a notification that the cycle is complete, it will notify you when it starts to rinse. For washing machines, the only truly fool-proof methods to detect if it is done is energy monitoring or a photo-sensor tied to a "Done" led on the washing machine. I've not heard of any other reliable method for washing machines.
All that does is enable the potential for cancelling.
RM is wonderfully complex now... you can have 10 items in an action. Maybe only 3 of them have a need to be cancelled. You would enable cancel on those 3, leave it not enabled on the other 7 and then when you actually issue a Cancel.. those 3 will stop.
In RM 2->3 that switch was "Cancel on truth change" -- RM 4 doesn't have "truth change" anymore. So you have to actively provide the Cancel action.
On the other hand, I do kinda like @neonturbo suggestion of Better Laundry Monitor. (I'm certainly biased, since I am actively updating that app right now.)
In RM 4.0, this is how I handle Washer/Dryer notifications based on the Power usage dropping below a threshold (e.g. 3.0 Watts) for a certain period of time (e.g 32 seconds.) If the power level goes back up above the threshold within those 32 seconds, everything resets and waits for the power to drop below the threshold again.
You have to play around with the Power Threshold and the Delay Time to prevent false alarms for your particular washer and dryer.
@leeonestop I have no idea what would cause that error. Maybe delete the rule and start over? It’s a fairly basic rule, nothing too fancy. It uses Private Boolean (for This Rule) to prevent the rule from constantly sending notifications.
@PPz is this code working for you? I have a dryer and washer that goes through different cycle and the power is up and down and I get false readings but after looking at your rule It looks like it may stop the false readings changing the max power is that correct?
The code is working for me. I realy don't think the Wmax loop does anything on this because it records only (while washing) the max power used by my machine and nothing else.
Probably the difficulty for any rule is to define exactly the perfect trigger.
In my case, the initial rule ("power changed") is not acceptable because my Zooz monitors a very small amount of energy, so always changing.
In iddle mode, the power is all the same inferior to 2 watts, that was my first trigger to initiate the rule.
when the machine is washing, the power is always higher than 5 watts until the end.
But writing this, my wife loaded a machine and I received a notification after 5 minutes, that means I need to fine-tune this rule too (probably the delay - too short)