The “Dryer Complete” automation may not work the way you expect.
It triggers when dryer_counter exceeds 20. This trigger will occur when the count changes from 20 to 21 It will not trigger when it changes from 21 to 22, or 22 to 23, etc (it triggers when the threshold value is crossed). So when the count is 21, it will check if dryer has been off for at least 5 minutes. If it has not the automation’s action is not executed … and the automation will not be triggered again (because the count has to drop below 20 and then rise above 20 to trigger the automation again).
Why not use the “Dryer Complete” automation to reset the counter? What’s the need to wait another 2 minutes before resetting it?
When “Dryer Complete” executes its action, the counter has served its purpose so you may as well reset it there as opposed to using a separate automation.
I have tried both: Xiaomi vibration sensor and power measurement and found power management far superior in terms of reliability.
You could even use the temporary additional power usage of crease protection (or anti-creasing, if your dryer has that feature) for a repeating reminder.
Interesting, never heard about 230V sockets in the U.S. My washing machine and dryer both consume 2300 Watts peak, so in Europe this translates to 10 Ampere. So there is no difference in the electrical plug.
Kinda late to the discussion but I just installed a temp/humidity sensor on mine over the weekend and made a YouTube video about it. Just incase it helps someone else.
I decided monitoring the moisture was a better approach for my situation since my dryer time seems pretty inconsistent and either leaves clothes damp or cooks them. I think this method should save me some electricity also.
Jake, I like you take on this: measure what you really want to know, i.e. are the clothes dry? I think I have all the parts here in my boxes, I think I have a new weekend project!
Ive also got the TPlink energy plug reader/sensor. I had my config setup like this (im a newb!)
But im getting random notifcations at odd times of the day when the dryer isnt running and I cant figure out why. I was hoping to tighten up my code and make it more strict.
Only problem is the dryer drops to 2.6W momentarily during its cycle to change its rotation of spin but sits at 1800W normally.
I have it currently send a notification simply once its been under 1.0W for 10 seconds but was thinking of maybe adding an IF statement somewhere to say if its been over 1000W for 10 seconds and then goes under 1.0W for 10 seconds THEN fire off a notification? Just got no idea how to write that
- alias: "Notify when dryer is done"
trigger:
platform: numeric_state
entity_id: sensor.my_tp_switch_watts
below: 1.0
for: 00:00:10
action:
service: notify.PUSHOVER
data:
title: "Dryer done"
message: "Grab the clothes!"
Hi, I have just picked up two vibration sensors, one for dryer and one for washing machine. Can you share your code with me please so I can tweak it to suit my application?
For those struggling with this like I was, I found a related post that solved my issues! Between the blue print and the idea to attach the sensor to the dryer drum it totally works now.
I went down a similar path, using the SW-420. Thought I’d share photos of a slight “upgrade” - it’s now a $5 sensor including the housing . ESP-01, carrier board, SW-420, Tic-Tac container, small piece of foam to hold the boards in place.
Is there a way to get something like this made and flashed already? I’m in way over my head here. I did finally get my preflashed s31 connected to my first homeassistant installation on my synology nas and think I have it configured to tell me when the washer power drops below 10 watts…running my first load of laundry now to see if it will work and trigger my sonos speakers in the kitchen.
I actually can’t believe I got this far but man I need help!