Great write-up. The only thing I don't like - not your fault :-) - is using relay-based devices on critical white goods. I've seen far too many relays fail. It would be really good to see a write=up of a non-in-line version of this post so that you were not reliant on a relay.

Thanks for the writeup and the node, it has allowed me to reliably implement notifications for most machines in my house, awesome! One suggestion for improvement: add the cost calculations to it. Some countries have multiple tarrifs for electricity during the day (I have two, one for day, one for night).

I also have different tariffs now (I did not when I first wrote the post) so I might add the feature. Thank you!

Very cool! 😁
I think I'll use that node-contrib soon.

Great tutorial! I am currently using DzVents to achieve the same goal, but definitely will look into Node-Red.
I have hooked up most of my appliances using a Sonoff POW R2 running Espurna. Since I too tend to forget to take out the laundry :)

Other than Telegram, Assistent Relay (https://github.com/greghesp... is very nice to use to broadcast a spoken message over a Google Home speaker.

I have recently equipped up my fumehood and my vacuumcleaner with a power monitor. I tend to miss hearing the doorbell when I'm cooking or vacuumcleaning. Now when one of the appliances is drawing power I can get notified by blinking the lights or just switching off of the vacuumcleaner over wifi! My wife still needs get used to it though.

Nice use case! I should do something similar when my daus are at home...
And yes, I'm sure there are several alternatives to using Telegram, I've been using PushOver for a long time.

It would be cool to eliminiate to dedicated power measurement with one at the main power supply of th e house, combined with NILM (Nonintrusive Load Monitoring) and power disagregation. Unfortnately there is no easy to use and open source system available by now.

Great tutorial. I made this with some nodes. Now my flow can be much cleaner. A problem I found with washer machine is that during some moments it have low consumption so I got wash end messages and a few minutes later a wash start. I solved it with different thresholds for started and stopped status, much like an hystheresys.
Besides a timer before stop message is thrown is useful.

Thank you. Yes, adding a separate threshold for the stop event can be useful. About the timer before the stop event, isn't that the same as the "stop after" configuration? I mean, if you are reporting power every minute a 5 here will wait for 5 minutes (with values below the threshold) to trigger the event.