Sonos things offline after migrating to openHAB 3 seems to be an UPnP issue

Hi,

I hope you can help me. I am using Sonos. But the devices are very old. I have to use as example the Sonos S1 Controller instead of the Sonos S2 Controller. Maybe it is a problem with the compatibility. But I think the problem is UPnP.

I have used openHAB 2.5.1-12 on Ubuntu 18.04. Now I am using openHAB 3.1.0 on Ubuntu 20.04. Maybe it’s a general issue because of the do-release-upgrade.

As example one of my things:

UID: sonos:PLAY5:RINCON_5CAAFD0D772E01400
label: tBad_Sonos_Lautsprecher
thingTypeUID: sonos:PLAY5
configuration:
  refresh: 60
  udn: RINCON_5CAAFD0D772E01400
  notificationTimeout: 20

If I go to Settings → Things I will see on the Sonos things Error:Comm. If I click on one of the things to have a close look I will receive as example:

COMMUNICATION_ERROR
The UPnP device RINCON_5CAAFD0D772E01400 is not yet registered.

The karaf console gives me following output:

openhab>  bundle:list | grep UPnP                                               
270 │ Active  │  80 │ 2.6.0                 │ JUPnP Library
322 │ Active  │  80 │ 3.1.0                 │ openHAB Core :: Bundles :: UPnP
bundle:list -s | grep -i "sonos"                                       
301 │ Active  │  80 │ 3.1.0                 │ org.openhab.binding.sonos
bundle:list -s | grep -i "upnp"                                        
270 │ Active  │  80 │ 2.6.0                 │ org.jupnp

On openHAB 2.5 I received following output:

openhab> bundle:list -s | grep -i "upnp"
263 │ Active │  80 │ 2.5.2                   │ org.jupnp
openhab> bundle:list -s | grep -i "sonos"
290 │ Active │  80 │ 2.5.12                  │ org.openhab.binding.sonos
bundle:list | grep UPnP
263 │ Active │  80 │ 2.5.2                   │ JUPnP Library
308 │ Active │  80 │ 2.5.0                   │ openHAB Core :: Bundles :: Configuration UPnP Discovery
316 │ Active │  80 │ 2.5.0                   │ openHAB Core :: Bundles :: UPnP Transport

From another user I got the information that he received:

openhab> bundle:list -s | grep -i "upnp"
252 x Active x  80 x 2.6.0                 x org.jupnp
268 x Active x  80 x 3.1.0                 x org.openhab.core.config.discovery.upnp
270 x Active x  80 x 3.1.0                 x org.openhab.core.io.transport.upnp
openhab>  bundle:list -s | grep -i "sonos"
267 x Active x  80 x 3.1.0                 x org.openhab.binding.sonos
openhab>

So the UPnP Discovery is gone. Maybe there are another mistake.

After that I tried:

feature:install openhab-core-io-transport-upnp
feature:install openhab-transport-upnp

You can see that it works:

openhab> feature:list | grep upnp
openhab-core-io-transport-upnp                    │ 3.1.0            │ x        │ Started     │ distro-3.1.0             │
openhab-transport-upnp                            │ 3.1.0            │ x        │ Started     │ distro-3.1.0             │ UPnP Transport
openhab.tp-jupnp                                  │ 3.1.0            │          │ Started     │ distro-3.1.0             │ UPnP/DLNA library for Java
openhab-binding-upnpcontrol                       │ 3.1.0            │          │ Uninstalled │ openhab-addons-3.1.0     │ UPnP Control Binding

Migrating for me means that I have installed openHAB 3 without deleting openHAB 2. So the paths changed and all old items, things, configurations etc. are the same. Except Sonos everything gone well.

Hope you can help me. Thanks in advance.

Maybe this will help you:

Quite simplier. The netword adapter from my VM was configured with NAT. That UPnP can work you have to use bridged. Sadly 7 from 8 devices are detected. But the good answer is that it could work.