#Power Plug automation if device is finished (e.g. washing machine, dish washer, ...)

1 messages · Page 1 of 1 (latest)

acoustic socket
#

Hi everyone,

I'm working on a Node-RED automation to send notifications when certain devices finish their tasks. For example, I want to get a push message when my washing machine is done.

Currently, I have a flow that triggers if the power consumption stays below 100 watts for at least one minute. However, after completing a cycle, the washing machine idles with a power usage between 0 and 1 watt. This causes the flow to incorrectly send "your device is finished" notifications whenever the consumption fluctuates within that range, even if the machine hasn't been used for days.

I'd like to add a condition to ensure the device was actively running before sending a notification. This would involve checking if the power consumption exceeded 100 watts for more than one minute and then dropped below that threshold for more than a minute. However, this approach seems overly complex.

Is there a simpler solution?

Thanks!

image.png image.png
severe parcel
#

I've got the same situation. After a bit of try and error, My automation just checkes if the value goes below 3 Watts for more than a minute and then triggeres the alarm. With this threshold my washing machine never sends me false positives

remote valve
# severe parcel I've got the same situation. After a bit of try and error, My automation just ch...

This is pretty much the way I handle our drier too.

I got a helper boolean "Drier is on" that is set to true once the Energy Current on the power plug goes to above 0.5. The 0.5 is when its not in standby but in early phases of a drying process.

Now, whenever "Drier is on" is set to true and the energy current goes below 1 (Cause during the process it changes from the early stages of 0.5 to finally 1) I set "Drier is on" to false again and can use that helper boolean as a trigger. I don't rly see any other way right now... but maybe somebody else has an idea?

acoustic socket
#

I wanted to build a automation which triggers a event state if the consumption is over 100 Watt for more than 10 minutes, which means that the device started to do its work.
After that I would like to wait 1 second and check a "current state" note if the consumption is under 10 Watt for 1 minute if yes I can do a notification if not I can wait again 1 second and check again.
This way it would check after device start each second if the device consumes less than 10 Watt for at least 1 minute and the automation stops in that case.

My big problem is that I can't setup a duration for the "current state" node if I don't choose a concret value (compare with "<" or "<="):

hot aspen
#

The really simple solution to this is "don't use nodered" - this kind of thing is incredibly basic to do with standard helpers and automation

severe parcel
severe parcel
hot aspen
#

The problem afaik is that the NodeRed trigger only looks for a state change and then lets you filter it based on what the current state is - this is what leads to it triggering at say 10W and 1W and anything <100W - because the state has changed, and the state is <100W
I believe the correct way to do it is as @remote valve mentioned, have a boolean that checks <100W, then check the state of that is true for 1 minute, and trigger off that, as then the exact power changing in the range 0-100W doesn't matter
In a standard HA Automation a numeric trigger only fires once it goes from above a limit to below the limit, which prevents this behaviour in the first place

acoustic socket
#

ok maybe I drop my node red automation.
But then I have to ask myself if there is a use case where I think I need two different places for automations.
Maybe I drop all node red automations and port them to HA automations...