SmartThings Community

[RELEASE] Wemo WiFi Smart Dimmer

Well, that wasn’t it.

Here’s the latest logs. Narrowed down to just the one switch that seems to “keep dropping”. All the polls is me trying to get an update from the device.

e73748c2-3253-4462-8957-b1611979db43 10:27:43 PM: debug Executing subscribe(192.168.86.30:49154)

e73748c2-3253-4462-8957-b1611979db43 10:27:43 PM: debug Using ip: 192.168.86.30 and port: 49154 for device: e73748c2-3253-4462-8957-b1611979db43

e73748c2-3253-4462-8957-b1611979db43 10:27:43 PM: debug calling getHostAddress()

e73748c2-3253-4462-8957-b1611979db43 10:24:21 PM: debug Using ip: 192.168.86.30 and port: 49154 for device: e73748c2-3253-4462-8957-b1611979db43

e73748c2-3253-4462-8957-b1611979db43 10:24:21 PM: debug Executing WeMo Switch ‘subscribe’, then ‘timeSyncResponse’, then ‘poll’

e73748c2-3253-4462-8957-b1611979db43 10:24:21 PM: debug Executing WeMo Switch ‘subscribe’, then ‘timeSyncResponse’, then ‘poll’

e73748c2-3253-4462-8957-b1611979db43 10:24:18 PM: debug Using ip: 192.168.86.30 and port: 49154 for device: e73748c2-3253-4462-8957-b1611979db43

e73748c2-3253-4462-8957-b1611979db43 10:24:18 PM: debug Executing WeMo Switch ‘subscribe’, then ‘timeSyncResponse’, then ‘poll’

e73748c2-3253-4462-8957-b1611979db43 10:24:16 PM: debug Using ip: 192.168.86.30 and port: 49154 for device: e73748c2-3253-4462-8957-b1611979db43

e73748c2-3253-4462-8957-b1611979db43 10:24:16 PM: debug Executing WeMo Switch ‘subscribe’, then ‘timeSyncResponse’, then ‘poll’

e73748c2-3253-4462-8957-b1611979db43 10:22:43 PM: debug Executing subscribe(192.168.86.30:49154)

e73748c2-3253-4462-8957-b1611979db43 10:22:43 PM: debug Using ip: 192.168.86.30 and port: 49154 for device: e73748c2-3253-4462-8957-b1611979db43

e73748c2-3253-4462-8957-b1611979db43 10:22:43 PM: debug calling getHostAddress()

e73748c2-3253-4462-8957-b1611979db43 10:21:09 PM: debug Using ip: 192.168.86.30 and port: 49154 for device: e73748c2-3253-4462-8957-b1611979db43

e73748c2-3253-4462-8957-b1611979db43 10:21:09 PM: debug Executing WeMo Switch ‘subscribe’, then ‘timeSyncResponse’, then ‘poll’

e73748c2-3253-4462-8957-b1611979db43 10:21:09 PM: debug Using ip: 192.168.86.30 and port: 49154 for device: e73748c2-3253-4462-8957-b1611979db43

e73748c2-3253-4462-8957-b1611979db43 10:21:09 PM: debug Executing WeMo Switch ‘subscribe’, then ‘timeSyncResponse’, then ‘poll’

e73748c2-3253-4462-8957-b1611979db43 10:20:44 PM: debug Using ip: 192.168.86.30 and port: 49154 for device: e73748c2-3253-4462-8957-b1611979db43

e73748c2-3253-4462-8957-b1611979db43 10:20:23 PM: debug Using ip: 192.168.86.30 and port: 49154 for device: e73748c2-3253-4462-8957-b1611979db43

e73748c2-3253-4462-8957-b1611979db43 10:20:23 PM: debug Executing WeMo Switch ‘subscribe’, then ‘timeSyncResponse’, then ‘poll’

1 Like

Any idea why I would be able to find one very easily using app and no luck at all on a second, using the exact same setup?

I’m also having a problem where the dimmers will be found and work for a couple days and then one of them (sometimes more than one) will suddenly stop communicating with SmartThings.

And now all my dimmers are no longer communicating with ST. It may or may not be related to the fact that yesterday I had to reset my whole network.(?)

Hi,
After a lot of playing around trying to get 26 dimmers to work I’ve assigned all to static IP’s but now I cannot make them stay connected after power loss or network reboot. Simulating the device handler shows that the IP and port calls work with devices that haven’t been restarted but once a device has it no longer can call correctly. I can see that the IP is correct but I’m guessing the port changed and for some reason i cannot get the handler to get the updated port. Any help with this would be great as I’ve made it this far and this seems to be my last hurdle.

i seem to be having this same error, ive narrowed it down to the port not adjusting. There is code to check port and ip but i cant seem to make it execute correctly.

If you are seeing weird concerns with SmartThings and Wemo please see this thread: https://community.smartthings.com/t/whats-going-on-with-wemo-switches-working-fine-for-3yrs-april-2019

I am seeing almost a complete lockout of the original REST API with only some polling capability still working. If someone is having better luck please let me know.

I used your code and it was wonderful. Worked for a couple of weeks and now It doesn’t see the two dimmers. Actually some times they show up in the Automation panel, sometimes not. In either case they don’t update the actual state of thew device and won’t change the state. They work fine in WEMO. I haven’t tried removing the devices and reading but will if you recommend that. I’m open to suggestions.

I could add that when in the SmartThings app and I try to change state the status is TurningOff or TuriningON and seems to hang there.

Here a couple of log snippets;
For WEMO WiFi SMart Dimmer:
5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug Call subscribe on c0352c3d-cd49-4dc9-8d1e-c56e511b2af9

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug Call subscribe on 7b4acccb-c62a-4bca-a096-77e7a081840d

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug getChildDevices(true), children=2

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug Send discover command

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug subscribeToDevices() called

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug Send discover command

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug subscribeToDevices() called

5ad75ef5-5b49-4292-985e-16feb046d999 11:36:17 AM: debug Dicovered dimmer switches

5ad75ef5-5b49-4292-985e-16feb046d999 11:36:17 AM: debug REFRESH COUNT :: 28

For device 1:
5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug Call subscribe on c0352c3d-cd49-4dc9-8d1e-c56e511b2af9

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug Call subscribe on 7b4acccb-c62a-4bca-a096-77e7a081840d

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug getChildDevices(true), children=2

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug Send discover command

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug subscribeToDevices() called

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug Send discover command

5ad75ef5-5b49-4292-985e-16feb046d999 11:39:46 AM: debug subscribeToDevices() called

5ad75ef5-5b49-4292-985e-16feb046d999 11:36:17 AM: debug Dicovered dimmer switches

5ad75ef5-5b49-4292-985e-16feb046d999 11:36:17 AM: debug REFRESH COUNT :: 28

For Device 2:

7b4acccb-c62a-4bca-a096-77e7a081840d 11:44:46 AM: debug Executing subscribe(10.0.0.242:49153)

7b4acccb-c62a-4bca-a096-77e7a081840d 11:44:46 AM: debug Using ip: 10.0.0.242 and port: 49153 for device: 7b4acccb-c62a-4bca-a096-77e7a081840d

7b4acccb-c62a-4bca-a096-77e7a081840d 11:44:46 AM: debug calling getHostAddress()

7b4acccb-c62a-4bca-a096-77e7a081840d 11:40:07 AM: debug Using ip: 10.0.0.242 and port: 49153 for device: 7b4acccb-c62a-4bca-a096-77e7a081840d

7b4acccb-c62a-4bca-a096-77e7a081840d 11:39:46 AM: debug Executing subscribe(10.0.0.242:49153)

7b4acccb-c62a-4bca-a096-77e7a081840d 11:39:46 AM: debug Using ip: 10.0.0.242 and port: 49153 for device: 7b4acccb-c62a-4bca-a096-77e7a081840d

7b4acccb-c62a-4bca-a096-77e7a081840d 11:39:46 AM: debug calling getHostAddress()

7b4acccb-c62a-4bca-a096-77e7a081840d 11:39:46 AM: debug Executing subscribe(10.0.0.242:49153)

7b4acccb-c62a-4bca-a096-77e7a081840d 11:39:46 AM: debug Using ip: 10.0.0.242 and port: 49153 for device: 7b4acccb-c62a-4bca-a096-77e7a081840d

7b4acccb-c62a-4bca-a096-77e7a081840d 11:39:46 AM: debug calling getHostAddress()

7b4acccb-c62a-4bca-a096-77e7a081840d 11:37:04 AM: debug Using ip: 10.0.0.242 and port: 49153 for device: 7b4acccb-c62a-4bca-a096-77e7a081840d

In January I used the handler and app successfully after installing a new Wemo dimmer. All had worked so well that I recently installed two more Wemo dimmers. However, the app doesn’t see the new dimmers. The old dimmer is still listed as found and the Discovery Started! wheel just keeps on turning. I thought I’d post here before I uninstalled and re-installed the app and/or handler. The old dimmer is still working fine. Is there a fix? Or is this a known issue with newer Wemo dimmers?

1 Like

Hi Sirtwist, I am new with Smartthings. I have a problem with a WeMo Dimmer. I installed My SmartsApp and My Device Handlers as you suggest in graph.api.smartthings.com/ide/apps. I can’t see the app in SmartThings Classic app “Marketplace - SmartApps - My Apps”. do you know what I am going wrong? Thank you.

While @sirtwist’s smartapp+device-handler worked fine from January until sometime late March, reviving functionality was fruitless, at the time. Also I haven’t seen any updates here since then, so I had given up on this, never bothered to tinker with it, and oddly enough just left it as is. The dimmers even had static IP’s on the router & I never found the need to change any of that.

Strangely yesterday, the 18th of June 2019, I noticed they were ALL working with smartthings. Can’t think of anything that changed. There was an update on my phone to the wemo app, but that can’t be it.

I guess I had a one-second power outage in the morning. That rebooted all the dimmers, the smartthings hub and everything else. So I am not sure which device’s reboot (dimmers, the hub or maybe the wifi router) fixed it, but as I am typing this, all the wemo dimmers are working through smartthings, all the automations/lighting smartapp rules are running successfully. It was a pleasant surprise.

Perhaps when there are no obvious answers, rebooting could be one.

Great to hear someone has got the dimmers to work. When you say that now all your dimmers are working through smartthings, do you mean that @sirtwist’s smartapp+device-handler was used to find the dimmers? Or did the smartthings app itself find your dimmers? My issue is that the smartapp still discovers my original dimmer (installed January 2019) but not my two new dimmers installed May 2019.

On a side note, what’s worse is that the Alexa app sees the Wemo dimmers as a simple switch when discovered through Wemo. It’s only when discovering the dimmer through smartthings that Alexa will see it for what it is. I can voice control my original dimmer through Alexa because it is seen as a “SmartThings Light (dimmable)”. But because I can’t discover my other two dimmers through smartthings, they are each listed in the Alexa app as “WeMo Dimmer Switch”. However, there is no dimming functionality in the Alexa app, they function as a switch only.

To answer the first part; back in early January, all my wemo dimmers were “found” by sirtwist’s smart app successfully and automations were configured using the standard smart lighting smartapp. It worked great for a couple of months. It broke sometime in March. I lived without the automations till now, even gave up on it. I didn’t do anything at all (not even go back to remove/re-add sirtwist’s smartapp, or try finding the dimmers again or nothing, I just let it all be). The dimmers even showed up among my things, however trying to control them from there was pointless, always. When attempting to turn it on or off, it would say “TURNING ON or OFF” forever and nothing ever happened.

Yesterday, all of that stuff suddenly started working again. All I can think of, as to what happened in March was that the hub received a firmware update, the functionality probably broke after that. And since then…yesterday, there was a brief power outage that rebooted everything, which seemed to restore functionality. To add complexity to the thought, there may be some wemo firmware updates to the dimmers too that break these things.

To answer the second part; that is just plain bizarre. I control my dimmers with Alexa using the wemo integration and not smartthings. In fact I have disabled all the smartthings instances of these wemo devices in the Alexa app, because…smartthings integration is a luxury I can not afford at all times because of its unofficial nature and lack of reliability.

As you can see below that one of my dimmers has brightness control within the Alexa app. I have never had issues controlling the state or brightness of this device with my voice using an echo device. It just works.

And just for more clarity, here’s the detail/setting screen within Alexa app for this dimmer. It will show that it is a wemo dimmer switch that is connected via wemo.

I think maybe you should disconnect Wemo from Alexa app (and also Alexa from Wemo app). Then try re-integrating them, hopefully you can solve this issue that nobody else has. I can’t imagine how frustrating it must be to not be able to change brightness with Alexa. It should work just fine through the Alexa-Wemo connection