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'm getting great log messages from the stall feature now thank you.
My next request is a log message for recovery. These days it happens fairly oftem, so I go and check the temp to see if the line has some angles. It would be much better if I could see the sensor recover in the logs if thats possible.
I tried to understand the code base to make a PR but unfortunately I couldn't work it out exactly (_remove_stale_tracking?). I was wondering if when the code that would reset the time, could check if the state was currently stalled, then log that it's being reset as part of the reset process.
The reason I'd like this is to see how long the stalls are. Can't tell if they are just over my 5 min timer, or longer etc.
This is what I see. This is mainly due to bluetooth issues.
2024-09-12 00:50:11.969 WARNING (MainThread) [custom_components.dual_smart_thermostat.climate] Climate (main_bedroom_climate) - sensor (sensor.yz_e871_temperature) is stalled, call the emergency stop
2024-09-12 02:20:14.948 WARNING (MainThread) [custom_components.dual_smart_thermostat.climate] Climate (main_bedroom_climate) - sensor (sensor.yz_e871_temperature) is stalled, call the emergency stop
2024-09-12 03:49:14.110 WARNING (MainThread) [custom_components.dual_smart_thermostat.climate] Climate (main_bedroom_climate) - sensor (sensor.yz_e871_temperature) is stalled, call the emergency stop
Thanks,
Jacob
The text was updated successfully, but these errors were encountered:
Hi,
I'm getting great log messages from the stall feature now thank you.
My next request is a log message for recovery. These days it happens fairly oftem, so I go and check the temp to see if the line has some angles. It would be much better if I could see the sensor recover in the logs if thats possible.
I tried to understand the code base to make a PR but unfortunately I couldn't work it out exactly (_remove_stale_tracking?). I was wondering if when the code that would reset the time, could check if the state was currently stalled, then log that it's being reset as part of the reset process.
The reason I'd like this is to see how long the stalls are. Can't tell if they are just over my 5 min timer, or longer etc.
This is what I see. This is mainly due to bluetooth issues.
Thanks,
Jacob
The text was updated successfully, but these errors were encountered: