Did anyone ever get this ported?
Sorry, I haven’t had any time to devote to this lately, but I’ll try to get something out in the next couple of days.
Thank you Jason. I truly appreciate what you have done and are doing.
I posted a dimmer driver and an updated Connect app. If anyone would like to give those a try, install both, then add a dimmer in the Connect app and let me know if that works. (These have only been lightly tested since I don't have a dimmer.)
Jason @jason0x43 ,
I removed all devices, application, and drivers. Rebooted the hub. I then added the drivers, the user app, pulled it into Apps, and ran discover. It found the plugs and switches, but so far has not found the three dimmers. No issues identified in logs.
What do the logs look like for the Wemo Connect app while it's looking for devices? In particular, do you see messages with the following format?
Parsed discovery message: urn:Belkin:device:controllee:1
The name after "device:" denotes what kind of device is replying ("controller" is a classic switch, "lightswitch" is a newer switch, etc.). From looking at some other WeMo dimmer implementations I had assumed a dimmer would be "dimmer", but it might not be. Or there might be something else going on.
app:1312019-05-14 07:45:17.009 pm traceFound devices: [24F5A2602E55:Entry, 58EF68F434F9:Living Room Table Lamp, 302303085A61:Porch, 30230307C89D:Bedroom Fan, 24F5A24B61E1:My Bedside Lamp, 302303085AF1:Living Room Fan, 24F5A24B6325:Bedside Lamp]
app:1312019-05-14 07:44:46.614 pm traceFound devices: [24F5A2602E55:Entry, 58EF68F434F9:Living Room Table Lamp, 302303085A61:Porch, 30230307C89D:Bedroom Fan, 24F5A24B61E1:My Bedside Lamp, 302303085AF1:Living Room Fan, 24F5A24B6325:Bedside Lamp]
app:1312019-05-14 07:44:36.080 pm traceFound devices: [24F5A2602E55:Entry, 58EF68F434F9:Living Room Table Lamp, 302303085A61:Porch, 30230307C89D:Bedroom Fan, 24F5A24B61E1:My Bedside Lamp, 302303085AF1:Living Room Fan, 24F5A24B6325:Bedside Lamp]
Jason, I thought to check to see what my FING BOX had to provide re. dimmers. It identifies them as "urn:Belkin:device:dimmer:1"
Name: Living Room Spot
Devices: * urn:Belkin:device:dimmer:1*
I hope that helps.
Ohhh, I think I see what’s happening. You’re not getting any discovery messages from dimmers because I didn’t update the connect app to query dimmers. I’ll have an update out for that tomorrow.
I posted an updated version of the Connect app (
Last updated: 2019-05-15, 08:37:21-0400) that more specifically pays attention to dimmer devices. Update that, let it search for devices, and let's see if it does a bit better.
Well done, Jason.
Discovery found the three dimmers and brought them into Devices. I tested each device individually in Devices. I have built a dashboard and also tested with Google Home via Google mini voice command. Voice command works perfectly, but dashboard and device page dimmer control is not working correctly
The dimmer function within Dashboard does not cause the dimmer to dim or brighten unless you change the state. If I have a dimmer at 100 percent and lower brightness to 50 percent with slider, nothing happens. If I turn it off, the slider shows the value I set the dimmer to. If I turn it on, it decreases or increases to the value indicated on the slider. Looks like it is not generating the set command (or equivalent) to commit the slider change.
I see similar behavior with the controls on the individual device page.
Here is the log sequence from the dashboard test:
Has anyone got a WeMo insight to be discovered.
I'm not that bothered as I use it to power my HE hub and use the WEMO app to turn it on and off if I need the hub rebooted remotely.
Was just wondering though.
@bobbles Yes. I use Jason's drivers and Wemo Connect app. So far, with the newly update dimmer driver, I have it discovering all of my WEMO products. Make sure you load the latest drivers and the latest user app over on Github. If you need help, let me know.
Fellow newbie, YF.
Ah, so brightness doesn't immediately change when you move the slider, but if you turn light off and on again it ends up set to the expected brightness?
Yes, The slider retains the value, but apparently the set command to the dimmer is not being sent or handled immediately. Same behavior in the Device page, except there you can turn on/off and nothing happens. Same with the set switch.
Driver date is Last updated: 2018-09-21
App date is Last updated: 2019-05-15
These are the latest in Github.
Just doesn't find the Insight. Finds my Switch OK.
Odd. From your log it looks like it's working. At least, the dimmer acknowledges the commands that set the brightness. The fact that the brightness does eventually change implies that the driver is at least getting the new brightness value over to the bulb. Hmmm...I'll have to look into that more tonight.
Are you using both the Wemo Switch and Insight Switch updates and Fix power calculation for Wemo Insight switch drivers?
That is what I observed too. Not sure where else or how to find anything that might help. Let me know if you have any ideas on getting deeper insight into the communications or behavior besides events and logs.
@bobbles I noted that it can take a considerable amount of time to discover all devices. I just left the discovery going, then manually or through Google Home turned on/off all devices. They eventually all showed up. Open the logs in a separate window from your Hubitat discover session. You can see the log entries as it attempts to discover the devices. Look for any errors.