Closed andker87 closed 8 months ago
@andker87 do you have a single WiFi access point, or multiple ones (or mesh)? In my experience the Meross devices lock on to an access point when they start, and don't roam.
What that means is if their closest access point goes down at some point, they may then switch to one further away. At that point even when the closer access point comes online, they don't roam to it.
It may be that simply unplugging your devices has allowed them to connect to a closer access point, providing a more stable signal?
@andker87 do you have a single WiFi access point, or multiple ones (or mesh)? In my experience the Meross devices lock on to an access point when they start, and don't roam.
I only have one access point (but meanwhile, one of the 3 smart plugs, the nearest one to the access point, has again become unavailable)
solved, there was an hidden copy of the folder in custom_components, that I could not detect via Home Assistant Editor. deleting that folder solved the problem.
Version of the custom_component
v5.0.3
Describe the bug
I solved this issue by removing the custom_component, restarting Home Assistant and installing it again. I removed power from the 3 devices (Meross 310 smart plugs) and then reconnected them. Home Assistant immediately discovered them by dhcp and they were configured correctly. However, every time HA restarts, this error appears.
(Also, I don't know if it's related, all the custom_component configurations dialogs don't show any text...it's like they're in white text on a white background. this happens only with this custom component, others are fine. I can provide a screenshot if needed)
Debug log