Skip to content

Commit

Permalink
Update diagnostics.md
Browse files Browse the repository at this point in the history
  • Loading branch information
PeteRager committed Jan 13, 2024
1 parent dcf1b6f commit 0bbffa3
Showing 1 changed file with 33 additions and 1 deletion.
34 changes: 33 additions & 1 deletion docs/diagnostics.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
# Lennox S30 Diagnostic Configuration

**WARNING** improperly configuring diagnostics can cause system stability issues - including excessive S30 controller reboots. communication instability and loss of control.
## Updates 2024-01

**WARNING** improperly configuring diagnostics may cause system stability issues - including excessive controller reboots. communication instability and loss of control. As of Jan 2024, Lennox firmware updates have improved the stability (or at least we are receiving less reports.)

In order to use diagnostics, your network should be setup to prevent the S30 from communicating to the Lennox Cloud. This will require router and firewall configuration.

Expand All @@ -24,6 +26,36 @@ For us Home Assistant enthusiasts, this primary use case is real-time power cons

Enabling diagnostic is done by setting the system diagnostic level from its default 0 to 2. When enabled, the system sends an update every 4 seconds containing the sensor data. This is sent to every connected client, which includes this integration, the lennox cloud and the Lennox App on your phone. This is where the problems occur. We believe when there is not be enough bandwidth to push the diagnostic data to the Lennox Cloud, across fhe cellular network to the phone apps. This causes data to start backing up in the S30 and eventually it exceeds a limit (runs out of memory?) and reboots. When it is rebooting your HVAC is off. Once it comes back up, the cycle repeats.

Note: As of December 2023 on S40s that are internet connected, it appears that Lennox is automatically disabling diagnostics after a timeout. This is likely to prevent excessive data hitting their cloud. This behavior has not been reported on S40s that are not internet connected.

```
alias: Fix Lennox S40 Diagnostics
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
```

It is certainly possible that it can be stable with an internet connected phone app. All we do know, is many stability issues have occurred when enabling diagnostic with internet connected S30s. And the only known stable systems are internet isolated.

## Blocking the internet
Expand Down

0 comments on commit 0bbffa3

Please sign in to comment.