It would be good to get to the bottom of why the upnp announcement when the port change is getting lost or file a bug for the wemo people to fix. I’m guessing when you fire up the wemo app it does discovery then, so its likely to be correct – SSDP always returns the correct port, but openhab is long running compared to the app, so if the port change message is lost then the only surefire way to change state immediately is to do the scan. Hopefully when it gets to the end of the port range it recycles.
I don’t know much about UPNP or SSDP, but if there’s anything I can do to test, review, or tweak, let me know.
It seems the dimmer is always the trouble maker though. I upgraded to 2.5.7 in hope of fixing the issue and it’s still there. My dimmer is currently not working, it’s not answering to either the switch function or the dimming function.
I don’t have any dimmers. I have to reboot my installation periodically (once every couple weeks), but it has been mostly stable since the upgrade.
The resent fixes have not been applied to the WemoDimmerHandler as nobody reported those issues for the Dimmer. I try to provide a new PR soon…
I finally tried the latest version of WeMo binding 2.5.8 based on the change from probing rolling ports using a PING vs. HTTP. I found that it was not as 99% reliable as the PING version is.
The PING version actually shows the WeMo going up and down with a THING status change. The HTTP version does NOT do this. The PING version actually comes back online after a few minutes. The reason I know this is because I monitor all my WeMo THING status’s.
I ran the 2.5.8 version for 48 hours against 32 WeMo’s (plugs, insights, 2 way switches and 3 way switches). I found that some of the plugs failed against rules that have been running for months now.
The negative side of the 2.5.0 version is it does NOT have all the new WeMo stuff programmed into (i.e. Dimmers, etc.) but it’s 99.9% reliable though.
Below is the link to the JAR that Hans and I debugged in late 2019 with the rolling port issues.
http://www.vtmc.org/download/org.openhab.binding.wemo-2.5.0-SNAPSHOT.zip
Best, Jay
1 Like
I will try to find out why there is such a difference between both solutions and also aplly a fix to the other device handlers. Just don’t know when to find time.