Closed SebastienMrc closed 6 months ago
This is due to a Meross device 'stealing' the ip address from another configured Meross device. When this happens HA/meross_lan detects a somewhat valid device at the configured ip but its identity is not the configured one and so the 'critical' error (else you could be fooled thinking you issue commands to the 'Kitchen lamp' while they go to the 'Bedroom' - examples are just random).
You should try to stabilize your ip(s) so that a device always receives the correct (fixed?) ip address from the router else this will likely continue to happen and it's very dangerous (see: #341 and detailed post explaining the issue).
You can manually recover by entering the device configuration and manually fixing the ip to the intended correct device
Thanks a lot for your help! Being new on Guithub I didn’t have the reflex to see if my problem had already been referenced. And in reality I didn’t even understand what the real problem was... Thank you, now that I know where it comes from I can fix them!
Version of the custom_component
Configuration
Describe the bug
I had an update to my internet box, and since then, my Meross bulbs randomly lose connection to Home Assistant and also randomly reappear. Out of my 12 bulbs, there are always at least 3 or 4 that are permanently inaccessible, but every 15 seconds different bulbs disconnect and reappear.
This is the first time I am reporting an error on GitHub, if I forget any important information, please let me know. If I forget any important information, please let me know.
Thank you in advance for your help!
Debug log