I accidentally upgraded everything and now my working configuration is no longer. I’ve got much of it back, but I’m getting a weird upnp error in the Hue Emulation.
I’m now running openhab 2.5.5 on a raspberry pi 2 B, Jessie.
Edit: I got further along by using the iptables forwarding rule in the documentation. Now I’m getting this error in the logs:
2020-05-22 14:20:20.873 [WARN ] [ueemulation.internal.upnp.UpnpServer] - Could not send UPNP response: Cannot assign requested address (sendto failed)
Notably, I am getting /description and /api/status pages that make sense on the port 80 lookups. How can I get more visibility into what’s happening that leads to “Cannot assign requested address?”
Thanks!!
Rudy
old error for searchers:
Self test
To access any links you need be in pairing mode!
Pairing mode: On (V1) [Enable]----://192.168.1.2:8080/api/status/link | [Enable with bridge V1 emulation]----://192.168.1.2:8080/api/status/link?V1=true
22 published lights (see —://192.168.1.2:8080/api/testuser/lights)
30 published sensors (see ----://192.168.1.2:8080/api/testuser/sensors)
2020-05-22 12:11:35.947 [WARN ] [ueemulation.internal.upnp.UpnpServer] - Upnp server: Address test failed
java.util.concurrent.CompletionException: java.lang.LinkageError: ClassCastException: attempting to castbundleresource://36.fwk13970914/javax/ws/rs/client/ClientBuilder.class to bundleresource://36.fwk13970914/javax/ws/rs/client/ClientBuilder.class
at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273) ~[?:1.8.0_152]
at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280) [?:1.8.0_152]
at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:604) [?:1.8.0_152]
at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) [?:1.8.0_152]
at java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:443) [?:1.8.0_152]
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) [?:1.8.0_152]
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) [?:1.8.0_152]
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) [?:1.8.0_152]
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) [?:1.8.0_152]
Caused by: java.lang.LinkageError: ClassCastException: attempting to castbundleresource://36.fwk13970914/javax/ws/rs/client/ClientBuilder.class to bundleresource://36.fwk13970914/javax/ws/rs/client/ClientBuilder.class
at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:97) ~[?:?]
I stopped openhab, used “openhab-cli clear-cache” and restarted. I’m back to that original java exception:
2020-05-22 14:36:51.413 [WARN ] [ueemulation.internal.upnp.UpnpServer] - Upnp server: Address test failed
java.util.concurrent.CompletionException: java.lang.LinkageError: ClassCastException: attempting to castbundleresource://35.fwk4794326/javax/ws/rs/client/ClientBuilder.class to bundleresource://35.fwk4794326/javax/ws/rs/client/ClientBuilder.class
at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273) ~[?:1.8.0_152]
at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280) [?:1.8.0_152]
at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:604) [?:1.8.0_152]
at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) [?:1.8.0_152]
at java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:443) [?:1.8.0_152]
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) [?:1.8.0_152]
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) [?:1.8.0_152]
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) [?:1.8.0_152]
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) [?:1.8.0_152]
Caused by: java.lang.LinkageError: ClassCastException: attempting to castbundleresource://35.fwk4794326/javax/ws/rs/client/ClientBuilder.class to bundleresource://35.fwk4794326/javax/ws/rs/client/ClientBuilder.class
at javax.ws.rs.client.ClientBuilder.newBuilder(ClientBuilder.java:97) ~[?:?]
at javax.ws.rs.client.ClientBuilder.newClient(ClientBuilder.java:126) ~[?:?]
at org.openhab.io.hueemulation.internal.upnp.UpnpServer.performAddressTest(UpnpServer.java:249) ~[?:?]
at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) ~[?:1.8.0_152]
… 6 more
I believe the port= is where my problem was. Because I ran on a non-standard port this changed slightly. Has been over a year so don’t remember, but has been working with no issues since then.
Only you can tell is what port is correct… it depends on what port your bridge runs on. My hue emulated bridge runs on 8090. A real hue bridge typically run on 80 I believe.
Do you use config files or paper ui? Your earlier post mentioned config files.
Hi,
as i have posted in my first reply: i never changed conf-files by hand!
The pict attached shows clearly paper UI !
In your answer you say that you clear conf-files that’s why i answer: never change … see above
…
So at least: on which Port runs a original Hue bridge?
2020-06-13 14:44:26.930 [INFO ] [io.hueemulation.internal.ConfigStore] - Hue Emulation pairing disabled
2020-06-13 14:44:28.151 [WARN ] [ulation.internal.HueEmulationService] - The UPnP Server service has not been started!
How can a UPnP server in hueemulation be started - this should fix the problem!