I would say YES and the watts will be your temp sensor reading. So your âStart - Appliance Power Setpointâ and your âEnd - Appliance Power Setpointâ will be the temp reading. Obviously you will not be able to use â*The Power Tracking Option *â.
Thanks for reply
The current version stops flashing (long) after just 12 flashes so if you are out side or away from home for an hour or so you donât see it flash -
So an additional option /should be great
flash⌠XX times
or⌠for X minutes
or âŚ. until (eg) entity / button pressed
Hi. Only 3 days in to my Home Assistant journey so forgive me if this question is obvious
I have set up my washer and drier with the blueprint and it seems to be working great.
The thing is that i would like to have the status (Ready, Running, Finished) in a card. How can I make this happen? I would guess I need an entity with this?
Also, is it possible to add a magnetic sensor for the doors so that it is possible to track Finished/Emptied?
It does not have a status (Ready, Running, Finished) and it works of power consumption for when it is finished. Currently is does not have the ability for a magnetic sensor but I will put it on the list.
Hi Blacky, many thanks for the update with the power monitoring and cost. I have it working here now and itâs fantastic. Well done!
Just some feedback - The three number helpers required by the blueprint were initially unclear to me - I initially thought that I could just specify a âCost per kWhâ and ignore both âPower Tracking - Start Number Helperâ and âPower Tracking - End Number Helperâ, but the notification didnât work when I did this.
Iâd suggest that you add in a piece of text to help explain the requirement for all three. Itâs actually a pity that these number helpers canât be dynamically created by the blueprint⌠perhaps something to pass onto the HA dev team?
Also you probably need to specify that the Power Tracking Start and End number helpers should be configured with sufficient size to take the kWh values from the power sensor. In one example that Iâm looking at I already have 27,852.31 kWh on the power sensor, so if I had created an undersized number helper with a smaller maximum value then it would probably have caused an error in the script at runtime.
Iâd suggest 1,000,000 as a maximum value.
Also the step size in the number helper should be around 0.01 so that it doesnât round-down the kWh value.
Hereâs one of my number helpers as an example:
I will provide some of my toughs through the development.
Cost number helper. I initially used an input but if you had multiple automation you would have to go into each automation every time your rate changed so having the rate in one number helper allows you to easily adjust and keep track in one spot. You can also use this in other automatons.
Start & End number helpers, allows you to use it in custom actions and you may also decide to utilize it somewhere else in your HA, add it to a dashboard or see history etc
Glad you are up and running and thanks for your feedback.
It looks like your options are sort and long. If you wanted to customize it maybe consider using a script to flash your lights with a button to cancel it and then run the script in the custom action.
Hello,
Trying out your blueprint and having an issue with a sudden brief increase in power usage.
No reason the washer would use that much power for such a short amount of time so I just assume it to be a mistake in monitoring by the plug.
Are there recommended settings to avoid this type of mistake in reading power consumption?
I have the blueprint set to start at 10 watts, delay for 5 minutes, dead zone of 1 minute, end below 15 watts end delay 1 minute.
Here is seems that since the 525 watts was above 10 watts and then subsequently stayed below 15 watts for a minute, so it triggered.
To me it looks like this shouldnât be happening, but I got the message at 06:40am!
Anyone have any thoughts?
Thatâs not a blueprint issue, it may have been an actual consumption event; some devices do this as part of a defrost cycle or mechanical exercise or such. I say that as itâs only showing ~500w consumption. Many or all of the inaccurate events that I have seen have registered values of 100,000 or even 10,000,000w rather than what you are seeing here. I applied an outlier filter to these sensors as they have a habit of doing that from time to time.
If itâs an actual problem then youâll need to apply a filter to it, but Iâd ignore it unless itâs really a problematic event.