Hueemulation UPNP send failure

Add-ons Bindings
1 
Platform information:
    Hardware: Raspberry Pi 4
    OS: Raspbian Buster
    Java Runtime Environment: 1.8.0_222
    openHAB version: Openhabian 2.5

Hello,
i have a warning from hueemulation in my log though there ist no hueemulation bridge in the inbox nor in the things section:

[WARN ] [ueemulation.internal.upnp.UpnpServer] - Could not send UPNP response: Cannot assign requested address (sendto failed)

I use a ConbeeII USB Gateway and the deonz binding.
Everything works fine and all needed things are found and online.

The warning comes up every 2 minutes. What i did so far:
Configuration-> Services->IO->HUE Emulation:

  • Pairing enabled
  • Unknown user-keys enabled
  • optional discovery ip set to raspberry/deconz ip

Then the hueemulation bridge appears in the inbox, but offline.

Reboot.

The Warning appears again.

Edited the hueemulation bridge-> ip4 adress of rasperry/deconz and Port:80

Hueemulation Bridge is now online.

Reboot

Nearly 100 new useless “Things” in my Inbox, something like: Flur_oben CLIP Generic Flag SensorFlur_oben, look like my items…?

Hueemulation Bridge has changed the Port to 8081, the port of my openhab installation.
The Warning appears furthermore every 2 minutes…

Deleted Hueemulation Bridge->Reboot-> Inbox empty, but warning is still there.

Has anyone an idea?

2

Try Deleting Hueemulation Bridge again then stop OH and clean cache.

sudo systenctl stop openhab2

sudo openhab-cli clean-cache

sudo systemctl start openhab2 or sudo reboot

Then reinstall the bridge (after OH has fully restarted, it will take a few minuets after a cache clean) and see if the error goes away.

3

Did that, but the error appears again :thinking:

4

Found a similar issue on github where the port is getting changed. https://github.com/openhab/openhab-addons/issues/6686

EDIT: @bloggi2363 See what happens when you set the port to 8090.

Also see some of the other closed issues…maybe there is something that can help.

5

Ok, if i understand this right, there is a bug in the binding. 8090 seems to be an example,i changed my port to 8081 with the same error. Hope for a fixed binding in the future, thx!