Hi! I have an Aeotec Smart Switch 6 connected to my Hubitat, with power reporting, and the washing machine plugged in to it.
I want to do a rule, or install an app to Hubitat, that will simply send me some signal (that I can then use for anything like to trigger an email, flash a light, I don't know yet how I'll do it) when the washing machine finishes. Based of course on the power activity of the plug.
I don't really know where to start - any helpful pointers?
Search these forums for "Laundry Monitor" there are at least two apps that handle this exact scenario. If you have Hubitat Package Manager, these apps both should be available in there, or they were the last I knew.
These apps are often better than a rule because they handle soak and fill and the multiple wash cycles easier than you could write a rule to do.
I did this quite successfully. But it was only useful on the first washer load. My dryer has a loud buzzer. And it always takes longer for the dryer to finish than the washer. So after the first load it was kinda useless.
Not gonna claim any rule I script is as good as some of what the sharper tacks in this forum can come up with...but this worked after I figured out the timing & power thresholds that the washer goes through. The announcement in "Nicole's voice" is a real hit; tho she's suppose to be Australian it's reminiscent of the dryly obnoxious computer voice in BBC's Red Dwarf if I recall right.
While there are apps, as above, here is a simple rule I wrote that works for my machine. You may need to adjust values depending on the power levels yours actually uses (this is small front-loader) as well as the the reporting settings on your outlet.
The rule in the post above is certainly another way you can handle this (and even mine could be written a bit differently given that the "duration" option could be used on that first wait instead of two waits in a row, but this rule pre-dates that feature and still works fine) ... so, lots of options. 
If you don't mind answering, what is the reason you have a private boolean requirement?
Hummm,
I may have applied a belt + suspenders approach having seen how the Priv Bool protects me from what I don't yet know will hurt me (as experienced in other cases/rules). Or I might have been testing and found that I ended up spawning multiple instances of the rule unintentionally with human intervention at the machine.
Probably not trusting a clean start & stop of the rule with a human lingering over a momentary button in the middle and the rule-end being highly dependent on a new device's measured wattage levels that I had not fully worked out yet.
Now you've got me thinking how/if this might be detrimental. 
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
