Last month there was a pretty major update to my SmartThings Hub and, once it was done, I found that none of my WEMO switches worked with that ecosystem any more. The things still showed up in SmartThings “stuck” in the last state that it had known them to be in prior to the update. But the state would not update as the switches were cycled, nor could I control them via SmartThings any longer.
The WEMO app continued to control the switches just fine so I knew it was unlikely to be an issue with the switches.
I conferred with SmartThings’ support folks and they pointed out that WEMO integration is a SmartThings Labs initiative. Which basically means it’s not a collaboration between Belkin and SmartThings and that Belkin can change things at any time and mess things up.
The long and short of it is that I needed to remove each WEMO switch from SmartThings, then let it discover them anew and then update every routine, SmartApp and webCoRE piston that used them as well.
This was driven home a couple of weeks later when I had to shut down my SmartThings Hub for several hours and again found the WEMO devices to be unresponsive.
The same technique worked to resolve the issue this time as well.
I’m still not 100% clear on exactly what it takes to cause the issue. Whether it’s the amount of time the SmartThings Hub is offline or if there is a confluence of events that has to happen. But I thought I’d post this to help folks who might be experiencing the same “zombie” Belkin WEMO switches in their SmartThings ecosystem.
You just need to suck it up and re-do. It’s a bit painful but you’ll resolve the issue and get on with life that much faster if you just go for it.