Skip to content
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

How often should diagnostic entities update? #283

Closed
42Network opened this issue Nov 30, 2023 · 15 comments · Fixed by #288
Closed

How often should diagnostic entities update? #283

42Network opened this issue Nov 30, 2023 · 15 comments · Fixed by #288
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@42Network
Copy link

42Network commented Nov 30, 2023

I am noticing that none of my diagnostic-based entities, such as Cooling Rate, Blower Power, various CFM numbers, update anymore. Regular entities, such as temperature and humidity do update, however. Admittedly, I do not have my thermostat blocked from the Internet because I like to use the Lennox app. Is lack of diagnostic entity updates a symptom of letting my thermostat have internet access?

Here is a screenshot of diagnostic entities not updating:
image

FYI if I simply toggle the Diagnostic Level setting from 2 to 0 and back to 2, they will update (in the above screenshot, I had toggled 21 hours ago):
image

Here is another screenshot showing some entities updating, others not:
image

Any ideas on how I can troubleshoot?

@PeteRager
Copy link
Owner

I have seen that before. See if this issue describes the problem.

#201

@42Network
Copy link
Author

42Network commented Nov 30, 2023

Hi. It may be similar, although in my case the diagnostic entities are available, just not with any recent values. Toggling Diagnostic Level causes a one-time update, but then they don't update any further.

At the recommendation of my Lennox dealer, I did enable continuous air circulation about a week ago in an attempt to better regulate humidity throughout our house, which has three zones (Main, which is our first floor minus master bedroom suite, Master, and Upstairs). Do you think this has triggered the internal Lennox bug you mention in #201? Now that I think about it, that might be when I first noticed these stale diagnostic entity values.

I can try to disable continuous air circulation from my thermostat panel and see if the integration starts getting diagnostics updates again.

@PeteRager
Copy link
Owner

Could be. So in your case they are disabled permanently, meaning toggling diag level does just does a one time poll? You may want to reboot the s30 see if that resolves. Also from HA settings integrations/lennoxs30 download the diagnostic file and post - this will have software versions in it.

@JTF195
Copy link

JTF195 commented Dec 1, 2023

I've seen this happen with my S40, especially with the inverter energy sensor. I noticed after a reload it would update every few seconds and display a min, mean, and max, but then after an hour or two it would get frozen.

I created this automation to toggle the diagnostic level from 2 to 1 and back, every 15 minutes, and that seems to be keeping everything updated continuously, without causing any of the sensors to switch to "Unavailable" like 2->0->2 does

alias: Fix Lennox S40
description: ""
trigger:
  - platform: time_pattern
    minutes: "0"
  - platform: time_pattern
    minutes: "15"
  - platform: time_pattern
    minutes: "30"
  - platform: time_pattern
    minutes: "45"
condition: []
action:
  - service: number.set_value
    data:
      value: "1"
    target:
      entity_id: number.lennox_diagnostic_level
    enabled: true
  - service: number.set_value
    data:
      value: "2"
    target:
      entity_id: number.lennox_diagnostic_level
mode: single

Additionally, the crashing/rebooting issues mentioned throughout the documentation do not seem to be affecting my S40.

It has full internet access, and all of the alerts and dealer sharing features are enabled.

It was disconnecting from the wifi a few times a day at first (without fully resetting and losing hvac controls), but that issue was reduced significantly with the automation above, and further reduced with some tweaks to my wifi configuration (renaming 2.4GHz and 5GHz to separate SSIDs and connecting the S40 to 5GHz)

@PeteRager
Copy link
Owner

With internet access enabled all the diagnostic information also streams out to Lennox. They may not like that and/or the controller gets overwhelmed. In the past the controller used to crash but perhaps they have fixed those.

@42Network
Copy link
Author

I created this automation to toggle the diagnostic level from 2 to 1 and back, every 15 minutes, and that seems to be keeping everything updated continuously, without causing any of the sensors to switch to "Unavailable" like 2->0->2 does

alias: Fix Lennox S40
description: ""
trigger:
  ...snip...
    target:
      entity_id: number.lennox_diagnostic_level
mode: single

I have implemented your suggested automation and my metrics are updating more consistently now, thank you! I will continue to observer the behavior.

Additionally, the crashing/rebooting issues mentioned throughout the documentation do not seem to be affecting my S40.

It has full internet access, and all of the alerts and dealer sharing features are enabled.

I too run my S40 with internet enabled and it seems to stay reliably connected to both Lennox cloud and HA.

It was disconnecting from the wifi a few times a day at first (without fully resetting and losing hvac controls), but that issue was reduced significantly with the automation above, and further reduced with some tweaks to my wifi configuration (renaming 2.4GHz and 5GHz to separate SSIDs and connecting the S40 to 5GHz)

I haven't noticed any WiFi disconnects with my S40 on with my 2.4/gGhz single-SSID Unifi access points. In your case, how did you notice these WiFi disconnects?

@42Network
Copy link
Author

I've seen this happen with my S40, especially with the inverter energy sensor. I noticed after a reload it would update every few seconds and display a min, mean, and max, but then after an hour or two it would get frozen.

I created this automation to toggle the diagnostic level from 2 to 1 and back, every 15 minutes, and that seems to be keeping everything updated continuously, without causing any of the sensors to switch to "Unavailable" like 2->0->2 does

Thanks for sharing your automation. It is working for me after updating the entity name for my system. I will keep observing, but my S40 diagnostic and parameter-based entities seem to be updated regularly now.

Additionally, the crashing/rebooting issues mentioned throughout the documentation do not seem to be affecting my S40.

I agree with you that the S40 seems to not suffer as much as S30 when it has internet access enabled simultaneously with the HA integration.

It was disconnecting from the wifi a few times a day at first (without fully resetting and losing hvac controls), but that issue was reduced significantly with the automation above, and further reduced with some tweaks to my wifi configuration (renaming 2.4GHz and 5GHz to separate SSIDs and connecting the S40 to 5GHz)

What symptoms did you notice with your S40 with a combo SSID? Mine stays connected 100% as far as I can tell with my Unifi APs.

@PeteRager
Copy link
Owner

PeteRager commented Dec 5, 2023

look at the Lennoxs30.state object it has a count of reconnects.

The availability of the sensors is managed by the integration. This is why going from 2 to 1 doesn't make it unavailable.

if self._system.diagLevel not in (1, 2):

it sounds like Lennox may be turning off diags after a certain amount of time. What version of firmware are you on?

@42Network
Copy link
Author

42Network commented Dec 10, 2023 via email

@PeteRager
Copy link
Owner

That is good information, I will update the diagnostics docs with this information and the sample automation.

The evidence so far points to this being related to having the thermostats be internet connected, as you both are running in that mode and we do not have a report of this problem occurring with the thermostats not internet connected.

What could be helpful is to turn on message logging, disable the automation and run until the diags stop updating. That would allow us to see if there is a message / status update that can be used to detect the situation. It may also give us some insight into where the message is originating from.

@42Network
Copy link
Author

Ok, good idea. I've enabled logging and disabled the automation and will let it run for a while.

@42Network
Copy link
Author

Ok. I disabled the automation and now my diag based entities are 4 hours stale. I bounced the Diag mode from 2 to 1 to 2 by hand and they didn't update and then I bounced it from 2 to 0 to 2 and they did update. This should all be captured in the message log. How should I give you the log file?

@42Network
Copy link
Author

42Network commented Dec 11, 2023 via email

@PeteRager
Copy link
Owner

I analyzed the logs and don't see any notification in there that says diagnostics got turned off.

But there is an issue with the diagnostic level number entity as it only gets refreshed when the integration is loaded/reloaded or when a command is issued to set it. So it is possible it is changing value and the integration may need to poll it.

if we want to test this, disable the automation, wait for it to stop updating, reload the integration and see what the diagnostic level is. If it's not 2 that means it is being changed and we need to poll it, if it is is 2 then Lennox is not updating this value when it disables diagnostics.

@PeteRager PeteRager added bug Something isn't working documentation Improvements or additions to documentation labels Dec 30, 2023
@PeteRager PeteRager linked a pull request Jan 13, 2024 that will close this issue
@PeteRager
Copy link
Owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants