Open llamafilm opened 8 months ago
It seems that this issue happens every time one of the controlled entities turn on is delayed. Of the four 4 entities I have controlled here, it's not always the same one which is 5 seconds late.
Looks like a duration sensor that you have. Maybe adding "sensor_type: duration" helps. Here is some info about the types. https://danobot.github.io/ec-docs/intro/sensor-types/
I’m having similar challenges
I recently started suffering from the same problem, and it took me a while to figure out the cause. If you ask me, it's got all to do with what you find in the docs under 'EC goes into blocked state', and the so called 'grace period'. Presumably the solution would be to extend the default thereof ...
HOWEVER : in the docs it is said 'Unfortunately, it is not possible to detect who called a service in Home Assistant. If that was the case we could simply ignore any service calls originating from EC itself.' As far as I can see this has not been true for quite some time already, as in the logs one can clearly see what/who made a sensor go active, e.g. which entity_controller entity triggered it. Therefore, @danobot, would it not be best to use that information and thereby getting rid once and for all of this problem - and the need for this 'grace period' parameter ?
I have been seeing the same problem lately. #193 seems to have addressed grace_period already so that probably isn't the cause.
Good find ! But it raises the question why this parameter still is being accepted (and used ?) without warning, despite being 'deprecated' years ago - and why the documentation still mentions it, as well as the reason for its creation ... So, what are we to believe ??
Could it be that the solution mentioned in #193 is no longer working or at least occasionally fails, and should be brought up to date - as on several occasions has happened to other parts of EC ?
Description
Sometimes after the timer expires, EC enters blocked state and the lights remain on. This doesn't happen every time, and I can't tell what causes it.
Configuration
Steps to reproduce
Expected behavior
active_timer
idle
Actual Behaviour
active_timer
for 5 secondsblocked
and lights stay on foreverLogs
I realize this log snippet only includes 14 seconds of activity, while my delay is set for 120s. Nothing else is logged for several minutes, this is actually the end.
Version
I'm using Home Assistant 2023.10.5 but I noticed the same issue on 2023.9.