Run Devices Run Before Issue

[mastermc0]

Hi,

Not sure if this is a bug or is working as intended. I have a device set up with the following.

• energy_time: 2
  entity_id: dishwasher_eco
  run_before: '07:00:00'
  run_time: 3

I have an automation that switches off the device and sets a wait boolean if the device is turned on after 1600. It then waits for the sensor time value defined above before turning it back on. The issue I have is that this device should always complete its cycle before 0700 the following morning, however, this morning the time value of the sensor changed at 0100 hours from the value 0200 hours to the value 1300 hours meaning that the device (a dishwasher) did not run overnight to complete before 0700 as intended.

Is this intended behaviour or a bug as I think what's happening is that it always takes 0700 as 0700 tomorrow even if we're calculating times on the same day prior to 0700.

If you need any more information please just ask.

[markgdev]

I think it's a bug, I've always used the run_devices as a visual q rather than in automations so haven't noticed, will dig into it some more. I think the timers with an input Boolean and block of time might work for you already, triggering off the input Boolean.

[GGW42]

Hi @markgdev & @mastermc0
I was wondering how you trigger your automation?
The reason I ask is mine triggers when the the value of "entity_id: octopusagile.dish_washer" "start_in" goes from "0.5" to "0" (actual trigger point is less than 0.5 because less than or greater than are the only options in a home assistant automation).
Mine skipped a run in the same way this week, when I checked the history, the "start_in" never reached zero and the time reset to a latter time so my dishwasher never turned on.
I think it was One in the morning when this occurred but would need to check the history to be sure. I remember thinking it might be daylight saving related as the UK is on daylight savings time but the timers are in GMT (Zulu) time.

On this same subject my washing machine works with a simular automation and this week the the cycle was still running at 1600 which is peak period, fortunately only 15 minutes of relatively low power at the end of a wash only cycle but this shouldn't be possible with the timer set up correctly? Again daylight saving error??