It really hard to look at these graphs and see the detail of the watts.
It looks like it starts and you have 2 dips before a large increase. Then the final one is the finish. Say the 2 dips went from 100 to 20 and then the final one went to 0 then your End - Appliance Power Setpoint would be 10.
Yes because you disabled the Energy Tracking and you now have an End - Repeat Count of 1. So long a all you power settings are correct then it will work.
TIP NOTE: when pasting code into this forum you best to use the </> and paste you code were indicated. It keeps the format so it easier to use and share.
The running dead zone is a period of time during which power measurements are ignored.
If your applianceās power fluctuates between the Start and End Setpoints, causing the automation to repeatedly stop and start, you can use the running dead zone to ignore that section of time.
During the running dead zone, the automation simply pauses and waits for the time to pass. Once the dead zone period ends, the automation resumes and starts monitoring your power sensor again.
Looking at your graph again, you probably donāt need a running dead zone. Try setting it to 0 and see how it goes.
This blueprint can do anything you can imagine - thank you Blacky, once again I can discover one of your works.
For the display in the dashboard, Iāll try a helper (binary_sensor.waschmaschine), which should be switched on and off at the start and end of the wash cycle.
Iām curious to see if everything works, so far Iāve only executed individual actions directly in the blueprint once (have nothing to wash right now ), but everything seems to be okay.
I also receive notifications on several Echos, but these voice messages are not sent simultaneously but one after the other with a noticeable delay. The latter is probably unavoidable, isnāt it?
Many thanks again!
Hi @Blacky! First thing, thanks for the wonderful blueprints. Iām using some of them, and they are AMAZING!
Iām writing this message to reach for help. Right now my appliances trigger the automation, and I can see the start notification; they increase the cycle count and change the run status, and yet I canāt get the end notification.
Like, this is the power graph for my washing machine:
You can see those drops in the energy from time to time during the first hour. Itās normal; the machine runs for a minute and then stops for no more than 10 minutes and repeats this for some time.
So, Iāve set the Running - Dead Zone to 10 minutes.
The End - Power Time Delay is set to 5 minutes, which is the max value available.
Could those two values be the source of my issue here?
Anyway, Iām pasting my config here in the hope that I could receive the end notifications that Iāve been waiting so much
The running dead zone is from when it starts. So say it started at 7:30 the automation wont look at any energy readings for 10 min until 7:40. Normally this will always be set to 0 but in some cases you may need to have a dead zone.
All the dips during the start to the end⦠what are they and what is the lowest reading?
Say you lowest reading is 1 watt. Then you could type in 0.5 watts if you like in your End - Appliance Power Setpoint. As long as the end goes from above 0.5 watts to below 0.5 watts for your End - Power Time Delay you will receive the end notification.
If the lowest reading during the cycle is 3 watts then you can set the End - Appliance Power Setpoint to 2 watts.
With All the settings, you can type the value in. So for you End - Power Time Delay only goes to 5⦠you can type in 8.5 if you like. Personally I try to get the End - Power Time Delay down as low as possible (under a minute) so when it finishes you get notified quicker.
The dips are moments that my washing machine stops, waits for some time, and then works again. A kind of āquick soakā. During that time the reading goes to 0.
Thanks for clarifying the Dead Zone behavior. So, it only works right after the start and not during the entire program, right?
I donāt know if my socket can read anything under 1 watt.
Iāve changed the configs here. Letās hope it works on the next laundry.
I didnāt understand what you meant by that or how to do it. Iām probably still too much of a ābeginnerā in HA.
But the good news is that I have found a solution that works. Create a speaker group in the Alexa app with the desired participants. The group then appears under āAlexa Devicesā and can be used in the Blueprint. The announcement is then made simultaneously over all speakers.
Aha, that helps. So youāll need to decide if this normally happens during a cycle. You could set a running dead zone of about 90 minutes, which would cover the period from the start to the 9 a.m. mark on your graph. This will disregard that part of your cycle.
Next, take note of the dips shown on the graph and see how long they last. Letās say theyāre about 2 minutes 40 seconds at most⦠in that case, set your End - Power Time Delay to 3 minutes, or slightly less if you prefer, but no less than 2 minutes 50 seconds. See below. Then reset your cycle count to 1.