meross_lan icon indicating copy to clipboard operation
meross_lan copied to clipboard

MTS200 regularly becomes unavailable in HA

Open andreweacott opened this issue 1 year ago • 3 comments

I've recently got a Meross HTS200 thermostat which was set up to work with HA via this integration (v4.4.1). It mostly works but regularly becomes 'unavailable' for hours at a time.

I've tested and have wifi connectivity to the thermostat (can ping it and control it via the Meross app) while HA is reporting unavailable, and restarting HA without touching the thermostat itself also resolves the issue.

Logs show,

2023-12-01 22:09:28.811 DEBUG (MainThread) [custom_components.meross_lan] MerossDevice(conservatory_floor_thermostat): polling start
2023-12-01 22:09:31.914 DEBUG (MainThread) [custom_components.meross_lan] MerossDevice(conservatory_floor_thermostat): ClientConnectorError(Cannot connect to host 192.168.1.181:80 ssl:default [Connect call failed ('192.168.1.181', 80)]) in async_http_request GET Appliance.System.All attempt(0)
2023-12-01 22:09:31.914 DEBUG (MainThread) [custom_components.meross_lan] MerossDevice(conservatory_floor_thermostat): polling end
2023-12-01 22:09:28.811 DEBUG (MainThread) [custom_components.meross_lan] MerossDevice(conservatory_floor_thermostat): polling start
2023-12-01 22:09:31.914 DEBUG (MainThread) [custom_components.meross_lan] MerossDevice(conservatory_floor_thermostat): ClientConnectorError(Cannot connect to host 192.168.1.181:80 ssl:default [Connect call failed ('192.168.1.181', 80)]) in async_http_request GET Appliance.System.All attempt(0)
2023-12-01 22:09:31.914 DEBUG (MainThread) [custom_components.meross_lan] MerossDevice(conservatory_floor_thermostat): polling end

But again, the IP is correct and the device is responding normally.

image

andreweacott avatar Dec 02 '23 11:12 andreweacott