Dropping message from unknown SenderId/SystemId [KL22E00090]

[garyak]

Describe the bug
Error in HA log:
2024-08-26 03:07:09.742 ERROR (MainThread) [lennoxs30api.s30api_async] processMessage dropping message from unknown SenderId/SystemId [KL22E00090] - please consult https://github.com/PeteRager/lennoxs30/blob/master/docs/sibling.md for configuration assistance
To Reproduce
Occasionally on HA startup.

Version

• Home Assistant:
• Core 2024.8.2
• Supervisor 2024.08.0
• Operating System 13.1
• Frontend 20240809.0
• This Integration: 2024.8.0

**Integration Configuration **

• Cloud or Local Connection: Local
• Inverter or Sensor Diagnostics Enabled: No
• App IDs are different
• Two s30s 1-zone, 4-zone

Additional context
Reload of the 4-zone system caused these, more familiar errors:

2024-08-26 03:28:38.796 ERROR (MainThread) [custom_components.lennoxs30] async_unload_entry entry [lennoxs30_192.168.3.94] error [Code [11] Reference [400] [logout Client Connector Error - failed due host not reachable url [https://192.168.3.94/Endpoints/ha_prod/Disconnect]Message ConnectionKey(host='192.168.3.94', port=443, is_ssl=True, ssl=<ssl.SSLContext object at 0x7f2d89b30650>, proxy=None, proxy_auth=None, proxy_headers_hash=None)Message [Errno 113] Connect call failed ('192.168.3.94', 443)]]
2024-08-26 03:28:41.932 ERROR (MainThread) [custom_components.lennoxs30] async_setup unexpected error login Client Connector Error - failed due host not reachable url [https://192.168.3.94/Endpoints/ha_prod/Connect]Message ConnectionKey(host='192.168.3.94', port=443, is_ssl=True, ssl=<ssl.SSLContext object at 0x7f2d80421950>, proxy=None, proxy_auth=None, proxy_headers_hash=None)Message [Errno 113] Connect call failed ('192.168.3.94', 443)
2024-08-26 03:29:44.780 ERROR (MainThread) [custom_components.lennoxs30] async_setup host [192.168.3.94] unexpected error Code [11] Reference [400] [login Client Connector Error - failed due host not reachable url [https://192.168.3.94/Endpoints/ha_prod/Connect]Message ConnectionKey(host='192.168.3.94', port=443, is_ssl=True, ssl=<ssl.SSLContext object at 0x7f2d80421950>, proxy=None, proxy_auth=None, proxy_headers_hash=None)Message [Errno 113] Connect call failed ('192.168.3.94', 443)]

A HA restart following the appearance of the errors above resulted in no errors from the integration. I did find that the temperature and humidity sensors were no enabled on on of the s30s even though values were being reported.

[PeteRager]

I'm not sure what qlqw233 is asking but it looks Ike an attempt to get you to download malware

[garyak]

Yes, apparently so.

[PeteRager]

I did find that the temperature and humidity sensors were no enabled on on of the s30s even though values were being reported.

Gary, Please clarify this statement.

[garyak]

As part of the device configuration, sensors are enabled/disabled by checkbox. For the single-zone s30, I had the temperature and humidity sensors enabled. For the multi-zone s30 I did not. However, values were being reported. This may not have anything to do with the communication issues. Just thought I'd add my discovery.

[PeteRager]

Apologies for the long delay. I'm adding code to dump the sibling message that is causing the log entry. That'll be in the upcoming release.

[PeteRager]

additional logging has been added

https://github.com/PeteRager/lennoxs30/releases/tag/2024.11.0

[PeteRager]

From @garyak

Startup results for 2024.11.0 lennox on HA 2024.11.1 core.

2024-11-10 06:57:56.577 ERROR (MainThread) [lennoxs30api.s30api_async]
processMessage dropping message from unknown SenderId/SystemId
[WL15L03440] - please consult
https://github.com/PeteRager/lennoxs30/blob/master/docs/sibling.md for
configuration assistance
2024-11-10 06:57:56.577 ERROR (MainThread) [lennoxs30api.s30api_async] {
    "MessageId": 0,
    "SenderID": "WL15L03440",
    "TargetID": "homeassistant_2",
    "MessageType": "PropertyChange",
    "Data": {
        "zones": [
            {
                "publisher": {
                    "publisherName": "lcc"
                },
                "status": {
                    "fan": false,
                    "allergenDefender": false,
                    "humidity": 37,
                    "temperature": 69,
                    "damper": 100,
                    "heatCoast": false,
                    "defrost": false,
                    "humidityStatus": "good",
                    "period": {
                        "systemMode": "off",
                        "fanMode": "auto",
                        "husp": 40,
                        "sp": 73,
                        "desp": 50,
                        "csp": 71,
                        "hsp": 43,
                        "hspC": 6,
                        "startTime": 0,
                        "humidityMode": "dehumidify",
                        "spC": 23,
                        "cspC": 21.5
                    },
                    "humOperation": "off",
                    "scheduleExceptionIds": [],
                    "balancePoint": "none",
                    "tempOperation": "off",
                    "ventilation": false,
                    "demand": 0,
                    "aux": false,
                    "coolCoast": false,
                    "ssr": false,
                    "temperatureStatus": "good",
                    "temperatureC": 20.5
                },
                "id": 2
            }
        ]
    }
}

Subsequent HA Core restart did not log this error.

[PeteRager]

I think this is a startup sequencing issue that is improperly detecting it as an unknown sender. Depending on the order and timing of messages this may or may not occur at startup which is what you are experiencing.

You have two systems

System 1:
app_id: homeassistant_1?
lennox_id: WL15L03440

System 2:
app_id: homeassistant_2
lennox_id:

Look at the two lennoxs30. entities in developer tools / states. This should list the sibling Ids and the sibling ip addresses. I would expect to see WL15L03440 to be listed in there. Is the sibling message drop counter increasing on either?

If it is a sequencing error i would expect to see a warning logged that looks like this when the error does not occur.

                    _LOGGER.warning(
                        f"processMessage dropping message from sibling [{sysId}] for system [{system.sysId}] - please consult https://github.com/PeteRager/lennoxs30/blob/master/docs/sibling.md for configuration assistance"
                    )

If that is not the case, then it appears that lennox is sometimes sending the sibling message and other times it is not.

[PeteRager]

This error AFAIK is not related to the sibling error

2024-11-10 07:06:37.706 ERROR (MainThread) [custom_components.lennoxs30] reinitialize_task host [192.168.3.94] Code [11] Reference [400] [login Client Connector Error - failed due host not reachable url [https://192.168.3.94/Endpoints/ha_prod/Connect]Message ConnectionKey(host='192.168.3.94', port=443, is_ssl=True, ssl <ssl.SSLContext object at 0x7f29c8467a50>, proxy=None, proxy_auth=None, proxy_headers_hash=None)Message [Errno 113] Connect call failed ('192.168.3.94', 443)]
2024-11-10 07:07:37.930 ERROR (MainThread) [custom_components.lennoxs30] reinitialize_task host [192.168.3.94] Code [11] Reference [400] [login Client Connector Error - failed due host not reachable url [https://192.168.3.94/Endpoints/ha_prod/Connect]Message ConnectionKey(host='192.168.3.94', port=443, is_ssl=True, ssl=<ssl.SSLContext object at 0x7f29c8467a50>, proxy=None, proxy_auth=None, proxy_headers_hash=None)Message [Errno 113] Connect call failed ('192.168.3.94', 443)]

The integration is recovering from the error and reconnecting? How often does this occur? The lennoxs30. entity should have metrics. I used to see this on a regular basis on my system (daily); periodically it looked like the S30's network stack would get restarted (or crashed and restarted).

From the other issue I see these are the firmware versions?

3.81.207 - South
3.81.213 - North

what is the version running on 192.168.3.94? If it is 207, you may want to upgrade it to 213.

[garyak]

Here's a snapshot:

System 1 (North)
app_id: ha_prod
lennox_id: WL15L03440
s30 fw: 03.81.0213
hub fw: 03.89.0314

sender_message_drop: 0
sibling_message_drop: 0

System 2 (South)
app_id: homeassistant_2
lennox_id: KL22E00090
s30 fw: 03.81.0207
hub fw: 03.81.0783

sender_message_drop: 9
sibling_message_drop: 1071

S30 Hub for South is a newer version of hardware. I'll try and get firmware versions synced up.

[PeteRager]

Before you upgrade. Make those app_id different. Restart the s30s and restart HA. That should decrease the sibling message drop.

[garyak]

They were different. I've edited the previous post to correct the copy/paste error.

South is now:
s30 fw: 3.95.146
hub fw: 3.95.700

North is now.
s30 fw: 3.95.146
hub fw: 3.95.350

[garyak]

All dropped message counters for both s30's have remained at zero following the firmware updates. No new errors have occurred over the past 12 hours and several HA restarts. Will reopen issue if errors return,

[PeteRager]

That sounds encouraging. I'll add a note to the readme to mention this issue and that this new firmware version appears to resolve - assuming it runs well for you over the next several days.

[garyak]

You might revisit S30 Configuration Considerations also. I switched off Auto Update a couple years ago. Thanks for keeping this working as well as it does.

[PeteRager]

I still think that is recommended. Lennox at anytime could disable the interface that the integration uses.

[garyak]

Good point. I'll switch updates back off until next time.

[garyak]

Updated to HA Core 2024.12.0 running on HAOS 14.0 and following a clean startup, these errors have returned:

2024-12-06 09:33:21.267 ERROR (MainThread) [custom_components.lennoxs30] reinitialize_task host [192.168.x.xx] Code [11] Reference [400] [login Client Connector Error - failed due host not reachable url [https://192.168.x.xx/Endpoints/ha_prod/Connect]Message ConnectionKey(host='192.168.x.xx', port=443, is_ssl=True, ssl=<ssl.SSLContext object at 0x7fd938b922a0>, proxy=None, proxy_auth=None, proxy_headers_hash=None)Message [Errno 111] Connect call failed ('192.168.x.xx', 443)]
2024-12-06 09:40:07.624 ERROR (MainThread) [custom_components.lennoxs30] reinitialize_task host [192.168.x.xx] Code [11] Reference [400] [login Client Connector Error - failed due host not reachable url [https://192.168.x.xx/Endpoints/ha_prod/Connect]Message ConnectionKey(host='192.168.x.xx', port=443, is_ssl=True, ssl=<ssl.SSLContext object at 0x7fd938b922a0>, proxy=None, proxy_auth=None, proxy_headers_hash=None)Message [Errno 113] Connect call failed ('192.168.x.xx', 443)]
2024-12-06 09:41:07.658 ERROR (MainThread) [custom_components.lennoxs30] reinitialize_task host [192.168.x.xx] Code [11] Reference [400] [login Client Connector Error - failed due host not reachable url [https://192.168.x.xx/Endpoints/ha_prod/Connect]Message ConnectionKey(host='192.168.x.xx', port=443, is_ssl=True, ssl=<ssl.SSLContext object at 0x7fd938b922a0>, proxy=None, proxy_auth=None, proxy_headers_hash=None)Message [Errno 111] Connect call failed ('192.168.x.xx', 443)]
2024-12-06 09:42:45.606 ERROR (MainThread) [custom_components.lennoxs30] reinitialize_task host [192.168.x.xx] Code [11] Reference [400] [login Client Connector Error - failed due host not reachable url [https://192.168.x.xx/Endpoints/ha_prod/Connect]Message ConnectionKey(host='192.168.x.xx', port=443, is_ssl=True, ssl=<ssl.SSLContext object at 0x7fd938b922a0>, proxy=None, proxy_auth=None, proxy_headers_hash=None)Message [Errno 111] Connect call failed ('192.168.x.xx', 443)]

message_count: 422
send_count: 8
receive_count: 464
bytes_in: 1157767
bytes_out: 2468
error_count: 6
http_2xx_cnt: 464
http_4xx_cnt: 0
http_5xx_cnt: 0
timeouts: 2
client_response_errors: 8

This is the 4-zone system (North). Sensors are reporting as expected. Communication was apparently established following these four errors as I monitored the HA log for ten minutes or so without seeing new errors occur. North is sometimes slow to display (unavailable) following a restart or update.