search

PeteRager / lennoxs30

Home Assistant Lennox S40 / S30 / E30 / M30 integration
MIT License
89 stars 13 forks source link

Dropping message from unknown SenderId/SystemId [KL22E00090] #339

Open garyak opened 2 months ago

garyak commented 2 months ago

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

Integration Configuration

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 commented 2 months ago

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

garyak commented 2 months ago

Yes, apparently so.

PeteRager commented 2 months ago

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 commented 2 months ago

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 commented 1 week ago

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.