Now that WeMo has shut down its cloud service, I’m wondering if anyone is looking into updating the existing binding or creating a brand new one to directly connect to WeMo devices over the LAN? There’s a python project that works to at least control devices that are already connected to a local network. They also have methods of connecting a device to a network, though I have not tested that. GitHub - pywemo/pywemo: Python module to discover and control WeMo devices.
I’d be willing to help, though I’ve never written or even edited an OH binding before. But before I dive in, I want to make sure someone else with far more skill isn’t much further along.
The Wemo Binding does not use the cloud service, it is local control only. But you needed the Wemo app and cloud to get the devices connected to your WiFi.
I only have two WeMo Insights. I don’t remember how I got them connected, but out of curiosity, and in case I will ever need to reconnect them to another access point, I looked it up.
It seems these devices creates their own Wi-Fi network, so you can connect to them using the app, and then configure their Wi-Fi settings. I can’t be sure this will still work, but it might. I believe I already made sure to have the app as APK after reading their announcement.
Yes, you connect to them through the Wemo app. But since a while, Wemo app needs a registered account to be able to connect new devices. Without their cloud service, there will be no login possible, so no new connections.
I have only one Wemo Maker and one Wemo Motion left in my installation, completely removed the rest….
Same as @hmerk, I scrapped everything except my Wemo Motion and Wemo Maker. It’s crazy how well those two devices work, considering that they were some of the first Wemos released and were abandoned by Belkin years ago.
My Wemo Motion would hiccup every now and then (and isn’t in use right now), but the Maker has been reliably controlling my gas fireplace for almost a decade.
My dad reused two of my old Wemo lightswitches for his outdoor lights. They still turn on/off as scheduled, but I’m guessing the internal clocks will slowly go out of sync with the world (not to mention Daylight Savings Time). When they eventually get too wonky, he’ll just swap them out for TP-Links.
Interesting. Right around the time WeMo shut down their cloud service, my WeMo binding stopped working. Maybe I’ll try to make it work again.
Also, I believe pywemo has a method of connecting devices to a wifi network without the app. I haven’t tested it, and I don’t know if it requires a certain firmware version.
I’ve mostly switched over the Kasa devices (which are also becoming a pain), but I still have a bunch of old WeMo that I could put to use if there was a reliable LAN connection.
If I remember correct, there was a firmware update, which tied them closer to the Wemo cloud. That could be the reason for the binding stopped working.
As said before, the binding controls the devices locally.
