We know the blueprint works as it runs everyday here in fact it is running now for me. You also seen it work, you know your settings work so you should be all good there
Thanks @Blacky and sorry for the inconvenience. I really donāt know whatās the problem. The next washing machine worked as expected. The same as the last time I wrote here.
Wish you a nice weekend.
I had 3 loads of washing yesterday and it worked every timeā¦ good thing you have seen it work so that helps.
I have tested your last YAML you posted of the automation (copy / paste). It is a very basic set up. I changed the power sensor and added my device and set the delay time to 0.1 to speed up the test. Worked first time, so you YAML is good and works
Try this test:
Get another appliance that has high wattage like hair dryer, heater, kettle etc. Plug it into the power sensor.
You can adjust the time delays for start and end to 0.1 to speed things up if you like.
Turn it ON see if you get the start message.
Turn it OFF see if you get the end message.
If this fails and you donāt have another power sensor to test with then you can use a temp sensor as it works of a numeric state. Just adjust the watts to suit the temp range your working in.
It is just to know how long the machine ran. If it could be implemented in the same way as the energy tracking it would be nice. Or even with less effort as no data needs to be pulled from an energy meter etc. Maybe this can be fully included into the blueprint without the need of creating helpers etc? Just a an checkbox āEnable run time trackingā?
Is it necessary to have the automation trigger properly to test a custom notification that includes a power consumption template? As I read this YAML after pasting it Iām thinking the answer is yes. My guess is that the variables arenāt set if the whole blueprint doesnāt run.
It would be nice to have your full YAML not just a snippet so I can see what is happening.
Looks like you have a custom actionā¦ not sure if it is the start or the end custom action. If you would like to do a custom action with power it must be an end custom action. For power to work you must fill out all power tracking options. You must enable one option. If you are just using custom actions then you just enable the one as shown below. Once you do all that you should get the information your after in your custom action.
I was wondering if itās possible test it without having the whole automation/blueprint triggered by the power sensor as I had an error when I hit ārunā on the custom action. I didnāt find a note about testing in the instruction posts, but couldāve missed it.
In the end, a run cycle and it notified as I hoped. I just needed to be patient and let it run itās course.
Blacky, Iāve constantly been impressed by your blueprint first, then your documentation, and finally your support. It truly is above and beyond. Thank you for all that you!
Yeah, when you hit run it will do the start actions not the end as it waits for the power to drop below so you need to actually run a real test using the actual trigger.
Great blueprint with many options covered. A couple of enhancement suggestions would be the ability to report how long the device was on as part of the notification. Also the ability to use the Power Used and Cost of Wash in the optional Custom Actions - perhaps populating them to number variables?
Hi @Blacky ,
since dishwasches hat this stupid behavior of 2 peaks (at start and somehere in middle) and then end. Maybe it would be an option for this automation. Count Powerpeaks X for 1 cycleā¦ somethink like that. maybe with powerpeak range ex. 500-700W
Have you looked at using the āRunning - Dead Zoneā. If you look at your cycle and work out your dips (not the peaks) and what time the dips are then set the running dead zone past that time so it will ignore your dips.
If you are unsure maybe post your graph of a cycle and I may be able to help more.
You donāt need to be informed exactly at the end. I mean itās not like you are cooking something and the end has to be the end. Set a trigger level, start a timer. You know how long your cycle is.
Unit starts, power above a level for so long, start timer. Wait the amount of time that takes you into the last cycle. Watch for the off condition below some level for a certain time and fire the action you want.
Wow! @Blacky - your appliance blueprint has evolved a lot.
and I am using it for various purposes in my household.
Many thanks!
How could I stop the automation?
it has detected a run of appliance but not its end. Most likely a configuration issue on my end. But itās still running and seems to wait for the end condition. Which would most likely only occur with the next run of the appliance.
This might lead to a potential extension of the blueprint:
what about adding an optional setting for the maximum duration of a run? If the run time is beyond this setting the automation stops (configurable?) and/or a notification could be sent about the potential misbehavior.
This is related, but maybe out of scope. Blacky, feel free to ask me to make a separate postā¦
Is this realistic, or do I likely have something configured wrong? Seems low to me, but I donāt have a point of reference. Itās a 2-3 year old mid level Samsung washer after a ānormalā load. Many load have had similar outcomes.