That's cool. Now I still need a 208V dual live wire energy monitor device for my dryer though.

I installed an Emporia Vue2 flashed with ESPHome in my home breaker box and put CT clamps on all my circuits which makes installing this integration easy.

This integration is pretty well polished and was much more polished than my simple crossing trigger I had before.

Just started using it so it hasn't learned any cycles yet.

@eightys3v3n @chaospatterns I got one that uses two CT clamps. It barely fit into the wall box with everything else in there, but I didn't shorten any of the wires to free up room. It's been a great addition to my overall monitoring infrastructure.

Was it easy to flash? I've already got mine installed but have been interested in flashing it for esphome instead.

I didn't know about this integration and have just been using an x appliance has been using power for x amount of time trigger.

Connecting the wires is a little finicky at times, but I used a pogo pin clamp which had the right pitch size to make it easy to connect and avoid soldering. Once you get it on ESPhome the first time, you can keep OTA updating new firmware

This walks through what I did

Neat, thanks!!

But why install an integration when the Appliance Notifications and Actions blueprint exists?

I think the only functional difference is that Washdata attempts to infer which cycle was run, but the blueprint doesn’t have to be configured via yaml.

They make these to put inside your breaker box too to monitor all your circuits.

sounds exactly like something that i want to set up for a while now. i just didn't find yet a good solution to overcome the two stories between our flat and the basement which houses the washing machine :/

Shelly EM Gen 3

I have been using that blueprint for the better part of a year, and just switched to WashData last week. I can confidently say that WashData absolutely blows that blueprint clean out of the water.

The biggest thing for me regarding WashData is that it can detect when a cycle starts and ends much faster than that blueprint.

That’s possibly your detection settings or method (detection criteria, etc). My washer and dryer are separate devices on separate power monitoring plugs. The only time power draw for either goes above 2 watts is when they’re cycled on.

I just told the blueprint to wait 2 minutes before deciding a cycle has started before declaring it’s started, and 5 minutes after it has ended before sending a notification.

But I mean, I’m not here to yuck your yum. If it works for you, it works for you.

I just like seeing the data and having it categorized automatically.