I currently have a docker installation of openhab 2.5.11 and openhab 3 (not running together). In both version (I tried v3 to see if it changed), Wemo binding have stopped working. The worst is there’s no error in logs anywhere. All my Wemo bindings does absolutly nothing (doesn’t toggle switch, dimmer or plug and state isn’t the right state). When going through the wemo app, everything work.
I tried reinstalling the 2.5.0 binding, removing and putting back the bindings, nothing work. And they show as online in the interface…
There have been no recent changes ti the Wemo Binding, so we need a TRACE log and more information about your installation.
Other users confirmed there are no issues with Wemo binding and oh3. Running fine in my installation too.
funny thing is it was working about 2 weeks ago, and nothing changed.
java version "1.8.0_202"
Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)
But this is the java in my gentoo, unless I’m wrong, shouldn’t affect what’s in the docker?
In the docker container, it’s:
openjdk version "1.8.0_275"
OpenJDK Runtime Environment (Zulu 8.50.0.51-CA-linux64) (build 1.8.0_275-b01)
OpenJDK 64-Bit Server VM (Zulu 8.50.0.51-CA-linux64) (build 25.275-b01, mixed mode)
On 2.5.11 docker version.
As for the 2nd question, I’m unsure what that mean “configured to host”
edit: could it be my router? I just tried a small UPnp Test Program and here’s the result
TEST 1 - Operating System Support - PASSED
TEST 2 - SSDP Service Running Check - FAILED
TEST 3 - SSDP Service Automatic Check - FAILED
TEST 4 - UPnPHost Service Running Check - FAILED
TEST 5 - UPnPHost Service Automatic Check - FAILED
TEST 6 - UPnP Framework Firewall Exception Check - PASSED
TEST 7 - Adapter #0 - x.x.x.x - PASSED
TEST 8 - Get External IP Address (Result: x.x.x.x) - PASSED
UPnP Test Program v1.16 Copyright Mark Gillespie 2010
for added debuging, I updated my whole system (docker included), didn’t fix. I also clear cache and tmp of openhab, still same issue and still unable to discover the wemo switch I removed
If discovery is not working, you have a strong UPnP issue in your system or your network.
This is not directly related to the Wemo binding but affecting it.
I just installed a fresh openhab3 installation on another computer and it’s discovery perfectly the wemos thus network wise it’s good. I’ll try to start from scratch in the docker too to see. I don’t get what I’m suppose to add for upnp to work
There’s something either with docker or the machine. I’ll try to see to install natively from source openhab on my gentoo to see. Just tried with a fresh openhab3 install in docker and still no wemos, thus everything point to that machine. Funny, I switch to linux and docker thinking it would be simpler and more stable but for the past 2 years, my windows installation was better. Must be me XD
ok, so I installed zulu jdk 11 and a fresh install of openhab 3 directly on my gentoo installation. Same result, no wemo detected. Thus it seems something doesn’t work on the upnp side of the gentoo install. That sucks because until yesterday, the gentoo installation was the same for the past 6 months…
me again. I installed upnpc client to see if I can manually make a upnp discovery and port map. Turns out I discover the router no problem and can send a port map request without any problem.