Your original rule had two triggers; one for the acceleration going on and one for acceleration going off. Either one would trigger the rule. You only had one notify action. So you would have gotten notified when the acceleration went on (machine start) and off (machine stop).
The new rule looks better, but you don’t the need the “and” in the conditions.
Hmm it appears to be working, but getting some false positives when it sits for longer than 5 minutes, any suggestions for adding don’t notify until at least 30 minutes after first detecting movement? I feel like that would help.
I suppose increasing the no vibration timer over 5 minutes would help.
You’ll need to review the history for the entity through a wash cycle to see what your thresholds should be. I don’t use an acceleration sensor so I’m no help here.
I use this for my washing machine and it’s excellent! However, my dish washer is causing me problems: it always ends with a drying cycle which uses the same electricity as when it’s idle, then a brief run of the pump and back to idle, so I cannot use going to that idle power threshold for the finish event (since it will be triggered on the drying cycle, not at the end). Any ideas how to modify this automation for my use case?
If it helps I’ve attached the graph:
If the drying cycle is the same length of time, every time, then just set a time delay before the notification.
Occam’s automation in action.
Hi, fantastic blueprint. Just imported but get the error message Message malformed: Missing input pre_actions. Running on 2023.11
I have seen in the comments that this happened before. Anybody knows a fix? Would love to start using it.
Nobody has an idea??? Would be great ti get it to work. Thanks!!!
Hi, I find the answer here : https://gist.github.com/sbyx/6d8344d3575c9865657ac51915684696
“For those getting, ‘Message malformed: Missing input pre_actions’, add a wait time of 1 second into, ‘Actions when starting threshhold is crossed’ section at the bottom and it’ll be saveable.”
You can also delete this action directly after the creation.
The action really needs to be “optional”. Requiring an input just doesn’t make sense.
Hello, is it possible to add a second trigger at the end? Our dishwasher goes sometimes to zero watts in-between. I want to trigger if it does it the second time. Extending the hysteresis is not ideal as I get notified late after it really finishes.
Maybe add a “wait for trigger” including “continue on timeout” at the start of your actions?
Hello everyone,
I have used the blueprint to make my washing machine smart.
Blueprint imports first values analyzed and as soon as the machine starts I get a notification. However, it is much more difficult to know when it is ready, which is the real point of the thing.
I just can’t get any meaningful values, as the machine continues to make a short rotation every 30 seconds for about half an hour after it is finished so as not to crease and thus goes up again from the 6W to the current 29W or 90W.
I then tried it with: Send a notification when watt number is less than 7W for about 20 seconds, but that doesn’t seem to work.
Does anyone here also have this little problem and possibly a solution?
Hey there. First up! Thanks for the blueprint! I wanted to try it out today but I am getting the error message:
Message malformed: Missing input actions, pre_actions
Any idea why?
Have a great day, Cheers, Georg
Same issue here - any clues as yet?
Good afternoon,
I am trying to configure my dishwasher but with these power peaks I am not able to know what values I should put in the configuration.
Give the following a go
Starting power threshold 50w
Starting hysteresis 2 mins
Finishing power threshold 200w
Finishing hysteresis 10 mins
thank you very much! it worked!!
