You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using this Emporia Vue integration in an automation to alert me when the clothes dryer is done based on sensor.dryer_3_1min also known as the Power Minute Average. The automation is triggered when sensor.dryer_3_1min is above 1 for 1 minute, and then waits for sensor.dryer_3_1min to go below 1 for 2 minutes 5 seconds, since it appeared that HA logs sensor.dryer_3_1min updates in History exactly every 2 minutes. However, sometimes the interval stretches to 4 minutes, resulting in a false alert that the clothes dryer is done. Below I highlighted the 4 minute interval, whereas the rest are 2 minute intervals.
Any idea why the interval time would be inconsistent, and if there is a way to standardize (ideally every 1 minute)?
Firmware: Vue2-631
The text was updated successfully, but these errors were encountered:
The clothes dryer is not working non-stop, but in several cycles. My automation waits for the power to be zero for 10 minutes before it triggers. Here is an example of a cycle and then a brake and then another new load later on.
I am using this Emporia Vue integration in an automation to alert me when the clothes dryer is done based on
sensor.dryer_3_1min
also known as the Power Minute Average. The automation is triggered whensensor.dryer_3_1min
is above 1 for 1 minute, and then waits forsensor.dryer_3_1min
to go below 1 for 2 minutes 5 seconds, since it appeared that HA logssensor.dryer_3_1min
updates in History exactly every 2 minutes. However, sometimes the interval stretches to 4 minutes, resulting in a false alert that the clothes dryer is done. Below I highlighted the 4 minute interval, whereas the rest are 2 minute intervals.Any idea why the interval time would be inconsistent, and if there is a way to standardize (ideally every 1 minute)?
Firmware: Vue2-631
The text was updated successfully, but these errors were encountered: