Discovered Devices Can't be Configured

Version of the custom_component

Configuration

Add your logs here.

Describe the bug

A clear and concise description of what the bug is.

Debug log

Add your logs here.

[dellrichrichdell]

I have Meross Lan installed. I’m not technical, but it works well…except that two of my devices, two Meross bulbs, are not usable. The integration discovers them, after install, but when I press the configure button in each case, and then press the submit button on the already-populated popup which appears, an error message states that the devices are already configured…but they aren’t, in the sense that they dont’ show up anywhere that I can see in order to be able to use them.

I’d be grateful for assistance.

Thanks!

[krahabb]

Hello @khs2424, The issue lies in the fact that meross_lan checks for device ‘uniqueness’ by either macaddress and/or ipaddress i.e. if the device is already registered in HA/meross_lan by the same address it replies with the error. Of course this shouldnt happen if the device being discovered is not already registered with meross_lan but there’s obviously some conflict somewhere so HA/meross_lan thinks the device is already configured (even if you can’t access it on the UI)

Here’s the link to enable debug logging in order to better understand what’s going on under the hood and identify the ‘offending’ mac/ip

this forum thread has more info on how to manage this situation.

I’m sorry for the issue but I still haven’t figured out how to reproduce it in order to finally solve it…I’ll be back on this soon

P.S. double check in your HA there are no ‘stale’ meross devices and/or disabled or ignored meross_lan integrations