ever since version 109 or 110 a couple of my Wemo switches have decided to turn off right after being turned on and then usually will turn on again and then the same problem in reverse which means my automation to turn off the lights (they’re in the garage) sometimes doesn’t work and the lights either dont turn on or turn off.
Additionally, another switch in another location in my house frequently shows up as unavailable after I do a reboot.
I have tried both adding them using the integration (not entering them inside my yaml config file) and using static IP addresses inside my config.
I saw another post somewhere that mentioned WeMo is going to try to switch to forcing people to use the cloud? Not sure if that is part of the problem that I’m experiencing or not?
The issue is already reported and there is a pull request about that i hope it will be fixed in the next release, the problem is that it go back to off because it actually doesn’t change to the on state until the refresh method is called, so when you click ok it go back to the current state (off) because is not update at that time yet and the you can see only visually that it turn on that is because the state is refreshed before
For any future users that find this thread, what I’ve done for now to make my switches that are not working properly: I found and installed Node Red Wemo so I can still control the lights I want via Node Red since doing anything via HA still makes the lights turn on then off again then on again and so on… Here’s the link to the node I installed: https://flows.nodered.org/node/node-red-node-wemo
Here we are almost 2 years later and this is not fixed. I had the Leviton switches which are unadulterated GARBAGE - over half of them have gone bad, the relay just stops working. The Wemo switches seem of higher design quality. I haven’t had a single one fail. But I am SO SICK of turning on the light and having it turn itself off 500ms later.
As an automation device Wemo is great. As a manual device it is just plain defective.