-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feat] - log message for stall recovery #295
Comments
Please check v0.9.8.4beta-1 |
@swingerman I've had 3 stall messages in the last 24 hours and no recovery messages, and the sensors have recovered. Can I do anything to help debug?
|
The recovery message is an |
I've enabled info logging. |
Implemented warning and will include in the next release |
Great, working! I think perhaps the formatting is broken though: 2024-12-07 21:48:43.747 WARNING (MainThread) [custom_components.dual_smart_thermostat.climate.lounge_climate] Climate (main_bedroom_climate) - sensor (sensor.yz_e871_temperature) is stalled, call the emergency stop 2024-12-07 21:48:47.883 WARNING (MainThread) [custom_components.dual_smart_thermostat.climate.lounge_climate] Climate (main_bedroom_climate) - sensor (sensor.yz_e871_temperature) recovered with state: <state sensor.yz_e871_temperature=21.9; state_class=measurement, unit_of_measurement=°C, device_class=temperature, friendly_name=YZ E871 Temperature @ 2024-12-07T21:48:47.883473+13:00> Also, had two occurrences of stalling for 4 seconds. Given the only update every minute I wish I knew why. Perhaps bthome/HA bluetooth ? |
Not sue. What do you mean about broken formatting? |
Oh it looked like it might be print out a string representation of an object or something. Was just checking that that was intended - sounds like not a problem! Thank you very much for this feature. I'm noticing many stalls and recoveries in seconds, (1 sec and 4 sec for example). Any idea how to debug what is causing this to be considered stalled as it only send updates once per minute. |
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: