You are welcome! Itās fun to be part of the community
š Detect and monitor the state of an appliance based on its power consumption - V2.1.1 - Updated!
Well, I think it would have worked (and I finally got rid of that pesky last false alert) but I never checked to make sure the path to the script was right in what you had pasted. Not sure why, but my scripts have all sorts of weird names, and I canāt seem to change them (though thatās really not your problem!).
I have fixed that for next weeks load, and will circle back at that point. But I think itās going to be good 
is there a way to squelch an errant reading from the power monitor? for some reason over the past couple of weeks, no matter what i do to tweak it, my power monitor device gets these jolts of power for a couple of seconds when the appliance is not running. see the image:
itās basically an errant reading that i canāt get to stop. It actually went off in the middle of the night about a week ago causing a severe hit on the WAF for all the automation shenanigans that i have going on. For that particular issue, I created another automation to turn it off during sleep time, but it still randomly pops at least once per day. Is there a way i can tell the automation to only consider the appliance as running if it has sustained a power above the threshold for longer than a certain period of time (like we do with the job completeion timer, but for a job start?
Hi, Working great for Dryer, washing machine and dishwasher. Thanks.
Is it possible to use this to notify on power loss of say a chest freezer? I canāt seem to get it to send a notification when state is unplugged. State is reporting as unplugged.
Hi @leofabri ! I think Iāve just about got this down - but Iām continuing to have some issues with my script working properly when called by your automation.
When I run it independent of the automation, it correctly recognizes when the contact sensor on the washing machine is open, and thus ends the script. However, when itās called in the automation, it loops and doesnāt acknowledge when the contact sensor is open. I had to restart HA to get it to shut up. 
Should I perhaps just have a second automation that triggers when your automation is complete? Though I say that, and realize thatās what brought me to this thread in the first place - troubleshooting a secondary automation that wasnāt being triggered when your automation completed.
Arrrrrgh.
First and foremost, thanks for a fantastic and helpful Blueprint!
I have three suggestions:
Price for the cycle
Add the option to add an electricy price sensor which, combined with the consumed electricity during the cycle, calculates the total cost of the cycle.
Duration of the cycle
How long the cycle took.
Cycles power consumption
How much power was consumed during the cycle.
If these the suggestions would be implemented we can get notifications such as āThe washer is done, it took 3 hours and 2 minutes, consumed 2.3kWh of energy and costed 19,2 SEK.ā Thatās both interesting and would make people more aware of their appliancesā power consumption.
2 Likes
Iām working on that these days in my spare time:
Itās going to come in the form of a complementary blueprint.
6 Likes
It looks like you need V3 which includes the features you mentioned
Having a secondary automation that checks if a state of the state machine is entered is not a bad solution. Itās odd though that this is necessary.
Iāve never had any kind of problem with the custom actions, so this is confusing 
Yeah, itās both hilarious and annoying at the same time. I actually have to do my monthly ālaundry cleanerā today, so Iāll see about your ājob completedā triggering a script that in turn triggers an automation, and see if that does the trick.
I am using v3, but did not find a throttle for the start of cycle. perhaps i am looking in the wrong place. In the meantime, iāve used the filter entity to squash those spikes and it seems to be working ok. Need to fine tune it a bit as the start and completion signals are now delayed by a few minutes, but overall working well.
Okay, while it seemed to previously have been working when set up independently of your blueprint, once the ālaundry cleanerā run finished, it did the repeats just fine, but continued looping even after I did the action that should have ended it. Perhaps I should post elsewhere in the community to have someone troubleshoot that script?
How do I install your latest 3.0?
Iāve noticed this getting triggered in the logbook every 10 secs when pointed at a tasmota flashed powr3. I can see the state of the power entity refreshing this same time. Is there a way to have it react when thereās a reported change, since mine is refreshing with 0 still.
Iāve an IotaWatt that monitors the power consumption of several appliances, water heater, etc.
I use this blueprint for my laundry as I have it plugged into as switchable outlet.
Is it possible to use the iota device created for each appliance as the power monitoring source? It doesnāt have on/off control by HA.
thanks
If you are running V3 then you could use the Delayed Job Ongoing timer & Delayed Job Ongoing duration options to ignore those spikes. If you decide to use that option, then the automation will wait for the set duration before assuming that the appliance really started. Use a value that is just a little longer than the time of the longest spike and you should see it working
Hi! At the moment thereās no easy way of doing this and I believe there will never be one. The automation itself is made to work like this in order to be as stateless as possible and not memorize the trigger.
Itās not really a problem if it triggers fast, but I understand that this can be annoying.
V3
The fastest way to install V3-Dev is to open your VSCode ā Terminal and issue the following command:
cd /config/blueprints/automation/leofabri && curl -sSL https://raw.githubusercontent.com/leofabri/hassio_appliance-status-monitor/release/v3.0.0-dev/appliance-status-monitor.yaml -O
Reboot HA and you should see that the version has changed and there are more options (it should in theory not break the existing ASM automations)
Thanks, I had it configured that way, but maybe the burst was slightly larger than the delay. i will extend the delay and try again. Just to clarify, will this setting also squelch the burst before a cycle is actually running? from the wording it seems that it only looks at this while a cycle is running.
maybe the burst was slightly larger than the delay
Could be, from your previous graph I see that the burst was apparently 24 seconds long, but I used a ruler 
I can confirm that this option works before the job cycle starts. It actually affects when a cycle should be considered as started.
Iām working on V3.1 which has this feature built-in. Versioning this blueprint is such a mess.
Iām testing it at the moment, Iāll keep you posted
2 Likes
Do you have modified instructions available for 3? I am missing some helpers I would like to setup correctly.
Thanks!!