After some use of this automation with my dishwasher, I have a suggestion for you.
I found that when the washing cycle is completed, my dishwasher however still mantains a certain stable low power consumption level as itâs still on, until itâs physically turned off.
Unfortunately, as expected, similar low power consumption levels occur sometimes for brief periods (a few minutes) during the cycle.
This could be overcome setting a âdelayed Job Completion durationâ value, but this causes the side effect of a delay of many minutes before the automation is allowed to detect a job completion.
In my case, but the same might be valid for other types of appliance, the cycle duration is actually almost fixed, as my dishwasher always runs the same program.
So my suggestion to improve the automation would be to add a further optional parameter called something like âAfter job started do not check job completion before:â with a value in minutes (default 0 min, i.e. not used).
In this case when the final power consumption falls under the selected threshold, the job completion state may be detected immediately without delay as the possible intervening power falls during the cycle are not taken into account.
thank you for this great blueprint. I was wondering if it is possible to have some kind of translation for the state of the machine. The reason is, we are native German speaking, and it would look better if the state would be e.g âfertigâ instead of âjob_completedâ . Is this somehow possible?
Thanks
BR
Daniel
Hi, @niknol, I have read your post, but if I understood correctly, you proposed a new âminimum duration of the power being above the configured thresholdâ, while I actually propose a new value (minutes) after the blueprint has detected a job_ongoing state, before which not to check for a job_completion state, regardless of any power level variation occurring during this interval, so the level could stay near zero even for many minutes during the cycle w/o triggering a job_completion state.
The reason for example a dishwasher is that its washing cycle never lasts less then a certain amount of time, so itâs safe and easier to ignore any power variation before this interval has expired.
I have a water softener thatâs got me stumped. It takes about 2.5 watts all the time. When it goes through a regeneration cycle, a valve opens, stays open for a few hours, then closes. You can see one of these regeneration cycles in the picture below on Nov 6 from about 12:30 AM to 3:30 AM as two spikes up to about 5.8 W.
It also has a built in light. When I open the lid to add salt, the light comes on and takes about 7.2 W, which you can see on Nov 7 at about 2:00 PM.
So the question is, how do I detect the regeneration cycles, but not the lid opening?
If you can do without the light, then, if possible, you could remove the bulb, or at least replace the light bulb with a LED one having a less power requirement.
Open your config file editor of choice, then check in folder âpackagesâ, you will find a set of files for your appliances.
If you open for example âdishwasher.yamlâ, scroll down to the end of the file and you should find something like this:
Iâm using this blueprint for our washing machine but I keep running into some issues.
When it is finished the power usage peaks a bit when the machine tumbles the drum a few times until you open the machine. The fluctuations make it hard to determine the wattage that signals the washing machine is done, if I set it too low it wonât trigger, too high and it will keep on triggering while the machine is busy.
As a workaround Iâm now using an average of the power usage for the last few minutes of the washing machine which Iâve created using the statistics integration. It is working as expected, after the machine is done the âaverageâ sensor is reporting a steady 5-10 watts of power usage. But somehow the job_cycle helper is no longer switching to job_completed when the machine is done. Only after Iâve shut down the machine will the job change to completed:
Wanted to try this blueprint today. I connected my plug to the socket, added my washing machine to the plug. Set up the helpers, added and configured the blueprint. I then set some wattages rules etc. All going well so far, it knows when itâs running or not.
But after like half an hour it stopped. The smart plug went to âoffâ so my washing machine got cut off the power. In the HA logs there is nothing directly that caused it as far as I can see. The latest wattage was quite low, while the plug handled the 2200-2300W just fine, later when it returned to just a few watts, it just turned off. Any idea how that can be? I had it connected before and it worked fine without the blueprint.
Hi @leofabri, what might be a fun addition to your blueprint is adding an âunemptiedâ state that tells you the appliance needs to be emptied. This can be achieved by using a door sensor that detects if the appliance door is opened after the job is completed. This can then be used to for example send an extra message to your phone that you really need to empty the appliance after it is done for an hour or so.
For now I have a couple of automations that control my washer states and I would like to start using your blueprint, but Iâm missing this extra state.
@millercentral Just tried your 3.1.0, but it seems to always get âstuckâ in a paused state when itâs finished. I have set the threshold to 18w and a delay of 300 seconds. Currently, itâs at 11 watts and have been for a while. Last time the ASM-automation ran was 24 minutes ago.
If I setup and use the optional HA_PowerControl addon, how does your blueprint get the pause state exactly? Just by changing the state or what exactly connects both of yours automations?
