gary-sargent
commented
5 months ago Captured another disconnect and got the same trace - two client connections logged, but only one debug message in HA:
2024-03-18 19:01:44.167 DEBUG (MainThread) [custom_components.meross_lan.mss110_##############################18] Polling begin
2024-03-18 19:01:44.168 DEBUG (MainThread) [custom_components.meross_lan.mss110_##############################18] TX(http) GET Appliance.System.All (messageId:061dba7cdebe44c0aa5ba2422ef4706f)
2024-03-18 19:01:46.366 DEBUG (MainThread) [custom_components.meross_lan.mss110_##############################18] HTTP ERROR GET Appliance.System.All (messageId:061dba7cdebe44c0aa5ba2422ef4706f ClientResponseError:502, message='Bad Gateway', url=URL('http://192.168.123.100/config') attempt:0)
2024-03-18 19:01:46.366 DEBUG (MainThread) [custom_components.meross_lan.mss110_##############################18] TX(http) GET Appliance.System.All (messageId:061dba7cdebe44c0aa5ba2422ef4706f)
2024-03-18 19:01:46.560 DEBUG (MainThread) [custom_components.meross_lan.mss110_##############################18] HTTP ERROR GET Appliance.System.All (messageId:061dba7cdebe44c0aa5ba2422ef4706f ClientResponseError:502, message='Bad Gateway', url=URL('http://192.168.123.100/config') attempt:1)
2024-03-18 19:01:46.560 DEBUG (MainThread) [custom_components.meross_lan.mss110_##############################18] TX(http) GET Appliance.System.All (messageId:061dba7cdebe44c0aa5ba2422ef4706f)
2024-03-18 19:01:46.830 DEBUG (MainThread) [custom_components.meross_lan.mss110_##############################18] HTTP ERROR GET Appliance.System.All (messageId:061dba7cdebe44c0aa5ba2422ef4706f ClientResponseError:502, message='Bad Gateway', url=URL('http://192.168.123.100/config') attempt:2)
2024-03-18 19:01:46.831 DEBUG (MainThread) [custom_components.meross_lan.mss110_##############################18] Polling end[19:01:44.124][192.168.123.200:56988] client connect
[19:01:45.124][192.168.123.200:56620] client connect
[19:01:45.349][192.168.123.200:56988] server connect 192.168.123.149:80
192.168.123.200:56988: POST http://192.168.123.149/config
Host: 192.168.123.149
User-Agent: HomeAssistant/2024.3.1 aiohttp/3.9.3 Python/3.12
Accept: */*
Accept-Encoding: gzip, deflate, br
Content-Length: 246
Content-Type: text/plain; charset=utf-8
{"header":{"messageId":"061dba7cdebe44c0aa5ba2422ef4706f","namespace":"Appliance.System.All","method":"GET","payloadVersion":1,"from":"Meross","timestamp":1710788504,"timestampMs":0,"sign":"f3cfd62ea10d7ad7ce2cf555b031a833"},"payload":{"all":{}}}
<< Client disconnected.
[19:01:45.362][192.168.123.200:56988] client disconnect
[19:01:45.446][192.168.123.200:56620] server connect 192.168.123.149:80
192.168.123.200:56620: POST http://192.168.123.149/config
Host: 192.168.123.149
User-Agent: HomeAssistant/2024.3.1 aiohttp/3.9.3 Python/3.12
Accept: */*
Accept-Encoding: gzip, deflate, br
Content-Length: 246
Content-Type: text/plain; charset=utf-8
{"header":{"messageId":"061dba7cdebe44c0aa5ba2422ef4706f","namespace":"Appliance.System.All","method":"GET","payloadVersion":1,"from":"Meross","timestamp":1710788504,"timestampMs":0,"sign":"f3cfd62ea10d7ad7ce2cf555b031a833"},"payload":{"all":{}}}
<< server closed connection
[19:01:46.316][192.168.123.200:56620] server disconnect 192.168.123.149:80
[19:01:46.316][192.168.123.200:56620] client disconnect
[19:01:46.325][192.168.123.200:56636] client connect
[19:01:46.466][192.168.123.200:56636] server connect 192.168.123.149:80
192.168.123.200:56636: POST http://192.168.123.149/config
Host: 192.168.123.149
User-Agent: HomeAssistant/2024.3.1 aiohttp/3.9.3 Python/3.12
Accept: */*
Accept-Encoding: gzip, deflate, br
Content-Length: 246
Content-Type: text/plain; charset=utf-8
{"header":{"messageId":"061dba7cdebe44c0aa5ba2422ef4706f","namespace":"Appliance.System.All","method":"GET","payloadVersion":1,"from":"Meross","timestamp":1710788504,"timestampMs":0,"sign":"f3cfd62ea10d7ad7ce2cf555b031a833"},"payload":{"all":{}}}
<< server closed connection
[19:01:46.509][192.168.123.200:56636] server disconnect 192.168.123.149:80
[19:01:46.509][192.168.123.200:56636] client disconnect
[19:01:46.517][192.168.123.200:56640] client connect
[19:01:46.544][192.168.123.200:56640] server connect 192.168.123.149:80
192.168.123.200:56640: POST http://192.168.123.149/config
Host: 192.168.123.149
User-Agent: HomeAssistant/2024.3.1 aiohttp/3.9.3 Python/3.12
Accept: */*
Accept-Encoding: gzip, deflate, br
Content-Length: 246
Content-Type: text/plain; charset=utf-8
{"header":{"messageId":"061dba7cdebe44c0aa5ba2422ef4706f","namespace":"Appliance.System.All","method":"GET","payloadVersion":1,"from":"Meross","timestamp":1710788504,"timestampMs":0,"sign":"f3cfd62ea10d7ad7ce2cf555b031a833"},"payload":{"all":{}}}
<< server closed connection
[19:01:46.779][192.168.123.200:56640] server disconnect 192.168.123.149:80
[19:01:46.780][192.168.123.200:56640] client disconnect
krahabb
wsw70
andker87
timnolte
Version of the custom_component
v2.6.1
Configuration
I am using the Mosquitto MQTT Broker, which I use along with Zigbee2MQTT as well. I have a unique HA user setup based on the MAC address of each device and I've configured this with each device when using the Android Custom Pairer app.
Describe the bug
As visible in the History/Logbook I see can the devices constantly going unavailable, then back online. This seems to have gotten worse with each new release of HA since the 2022.8 releases. While trying to debug this I can't even get/download the diagnostic on any of the Meross devices. My devices that were successfully setup via MQTT seem not to be also connected via HTTP. I am unable to change the Connection Protocol to anything other than MQTT for some of the devices as there is also no Host Address and also no Device Key(since it was configured with the Hacks Mode). And there seems to be no way to correct this either. I have a few devices that are connected only via HTTP, which are HomeKit Compatible devices, and those ones can't communicate via MQTT it seems, and those devices also become unavailable. I didn't want to have to have any of my devices registered through the Meross Cloud which is why I went the route of configuring them through the Custom Pairer App but I still can't seem to find the right setup that gets my devices connected via both HTTP & MQTT.
I'm really at a loss as to what to do other than remove all of my Meross devices, and the integration, and start all over again with no choice but to have my devices all connected to the Meross Cloud.
Debug log
Trying to provide relevant log entries with some of the data masked. I have the full raw logs that I'd be happy to provide in a more secure way.