search

krahabb / meross_lan

Home Assistant integration for Meross devices
MIT License
423 stars 47 forks source link

MSS305 stopped working, updated and still not working. #461

Open hl2jeep opened 3 months ago

hl2jeep commented 3 months ago

this error report is not gunna be particularly helpful because i have no idea what is causing this, neither can i seem to get a log of it happening... my MSS305 switch is unavailble in home assistant. in the configuration screen, if i try to press the submit button i get the following error. image

as i said before, i have tried getting a debug log file but nothing related to the integration shows up. im quite new to home assistant in general and this is the 3rd time this has happened to me, before i've fixed it simply by updating however this time it hasn't fixed itself.

krahabb commented 3 months ago

It's hard to say without any log... When you hit 'CONFIGURE' in HA UI for the device you could choose the 'Diagnostics' option and enable detailed logs for the entry so to try grab better insights. Once enabled 'Debug level' log into that form, try to reload the entry with the HA 3-dots menu and/or 'Download diagnostics'.

This issue in communication during configuration is very 'definitive' though: it looks as if the device totally refuses to respond to a basic standard query for abilities which, is supposed to be standard stuff for every kind of device. This happens either because the host address is wrong (and so you are querying a totally different device) or it could be the 'device key' is wrong and the device totally refuses communication (it would be better if the device could reply a kind of error message stating this but..that's it: in my experience, different devices/firmwares, exposed different behaviors for queries with a wrong key. Also, it looks as if in the latest firmwares the 'Connection reset' is typical behavior for wrong key: a kind of safety measure to prevent brute force attacks or so I guess.

hl2jeep commented 3 months ago

It's hard to say without any log... When you hit 'CONFIGURE' in HA UI for the device you could choose the 'Diagnostics' option and enable detailed logs for the entry so to try grab better insights. Once enabled 'Debug level' log into that form, try to reload the entry with the HA 3-dots menu and/or 'Download diagnostics'.

This issue in communication during configuration is very 'definitive' though: it looks as if the device totally refuses to respond to a basic standard query for abilities which, is supposed to be standard stuff for every kind of device. This happens either because the host address is wrong (and so you are querying a totally different device) or it could be the 'device key' is wrong and the device totally refuses communication (it would be better if the device could reply a kind of error message stating this but..that's it: in my experience, different devices/firmwares, exposed different behaviors for queries with a wrong key. Also, it looks as if in the latest firmwares the 'Connection reset' is typical behavior for wrong key: a kind of safety measure to prevent brute force attacks or so I guess.

I checked the IP address on my router and it agrees with the IP specified in HA, however I have no idea how to manually get the device key, I think it just automatically pulled it from my account. It's very late for me so I'll see if I can get a log file tmrw

krahabb commented 3 months ago

No problem, the possible causes anyway might be different from those exposed..they were just hints for something to investigate. Another hint (but I guess you already did it) is to reboot the device since it also happens, sometimes, the device stack starts to behave erratically with frequent disconnections (likely due to internal fw bugs/instabilities)

hl2jeep commented 3 months ago

No problem, the possible causes anyway might be different from those exposed..they were just hints for something to investigate. Another hint (but I guess you already did it) is to reboot the device since it also happens, sometimes, the device stack starts to behave erratically with frequent disconnections (likely due to internal fw bugs/instabilities)

I finnaly got a log file error_log.txt Not really sure what I should try doing, maybe reinstalling the integration?

krahabb commented 3 months ago

Hello @hl2jeep, The log reports exactly the same error on http connection as when you try to reconfigure the device. Not sure if it's related to encryption support for newer devices (#456).

In the weekend I should be able to publish a new release with support for that. In the meantime, if you enable 'beta releases' in HACS for meross_lan you could be able to try/test it yourself (the published beta was reported as working for devices with encryption)

hl2jeep commented 3 months ago

Hello @hl2jeep, The log reports exactly the same error on http connection as when you try to reconfigure the device. Not sure if it's related to encryption support for newer devices (#456).

In the weekend I should be able to publish a new release with support for that. In the meantime, if you enable 'beta releases' in HACS for meross_lan you could be able to try/test it yourself (the published beta was reported as working for devices with encryption)

Tryed it and I get the same exact error, 104 reset by peer