Wemo Dimmer Brightness display wrong value


I’ve updated to version 3.1 of OpenHab and while everything work properly, there’s one thing that is bugging me.

I have a thing for a wemo dimmer with a dimmer item and a switch item connected to the channel. The switch item work properly, turning on/off with latest value. The dimmer also work, but always reset to 100 whatever the real value is. If I slide to 45, the light does dim to 45 but the slider stop at 45 then update to 100 everytime.

I’ve tried using a floorplan with a widget and the samething happen.

Thank you

Please set the Wemo binding to trace logging and post the output when this happens.

ok, how do I set it to trace?

Enter the following in Karaf console

log:set TRACE org.openhab.binding.wemo
2021-09-25 12:02:07.511 [TRACE] [o.internal.handler.WemoDimmerHandler] - Command 'ON' received for channel 'wemo:dimmer:Dimmer-1_0-241742K1502433:brightness'
2021-09-25 12:02:08.502 [DEBUG] [o.internal.handler.WemoDimmerHandler] - Received pair 'BinaryState':'1' (service 'basicevent1') for thing 'wemo:dimmer:Dimmer-1_0-241742K1502433'
2021-09-25 12:02:08.503 [DEBUG] [o.internal.handler.WemoDimmerHandler] - State 'ON' for device 'wemo:dimmer:Dimmer-1_0-241742K1502433' received
2021-09-25 12:02:12.251 [TRACE] [o.internal.handler.WemoDimmerHandler] - Command '40.0' received for channel 'wemo:dimmer:Dimmer-1_0-241742K1502433:brightness'
2021-09-25 12:02:12.387 [DEBUG] [o.internal.handler.WemoDimmerHandler] - Received pair 'BinaryState':'1' (service 'basicevent1') for thing 'wemo:dimmer:Dimmer-1_0-241742K1502433'
2021-09-25 12:02:12.388 [DEBUG] [o.internal.handler.WemoDimmerHandler] - State 'ON' for device 'wemo:dimmer:Dimmer-1_0-241742K1502433' received

Seems they have changed the firmware sometime after i developed this. At that time, the actual brightness was reported too.
I will add another check to only update values if there is a real change.
Unfortunately, this will take some time.

no problem, wasn’t sure if it was something on my end.


Bugfix is on the way

Fix was merged and will be available with next SNAPSHOT and upcoming milestones/release.

great, thanks!

where can I find the snapshot? I though playing around in github I’d find it but I never understood how github work…

Please read the installation docs for openHAB. You can switch to testing repo snd install openHAB 3.2.M5 to get the latest version.

ah ok, I’ll wait for the release then. Does the new version give fix for

wemo.internal.handler.WemoHandler] - Failed to get actual state for device ‘wemo:lightswitch:Lightswitch-1_0-221813K13000C6’: null

I’m getting this error more and more. I restart openhab and it start working again, but it work for maybe 1 to 3 hours and I lose control 1 by 1 of each wemo device.

It has been released with openHAB 3.2 on December 20th 2021.

The second issue you are posting has been veryfied and a fix is under investigation. Don‘t have an eta now….

Please try this new dev version of the binding, which includes the fix for your second issue.

Please note that you need to delete your Wemo Things and have them rediscovered, as I introduced new properties to be used for polling.
This will be no issue, as the Thing will get the same ID as before…

oh yeah, just saw my docker is on 3.2.0 and it seems to be fixed. I’ll check back later because I was sure that last week I had the problem. I’ll try the 3.3 snapshot

something is weird, my addons folder doesn’t seems to work, the jar file doesn’t get installed

edit: nevermind

Install the Sonos binding even you don’t use it. It will bring the UPnP feature which is needed…

Already installed for another binding. Unfortunatly, it doesn’t work. It’s nearly worst because now I lost all of them and they don’t come back :frowning:

In the things, I have this message

upnp device not registered [“Lightswitch-1_0-221801K1300AEE”]

Did you remove the things and have them rediscovered ???
What do you see on the properties page of the things ???