BubbleServer: Can't add to playlist for a Sonos OpenHome proxy

[Steven Mackenzie]

Does anyone have BubbleUpnp Server working with Sonos? I want to have an OpenHome proxy set up for my Sonos Beam Gen 2 speaker, but Bubble Upnp hangs when I send media to the renderer...

I have BubbleUpnp server installed and running on a Raspberry Pi 4, and Twonky as my media server.

Most of my media renderers are chromecast devices, and for a few of them I've used the "Create an OpenHome renderer" option and can queue items as I expect. If I do the same with my Sonos Beam then I see a renderer called

"Lounge - Sonos Beam Media Renderer - RINCON38XXXXXXXXXXXXXXX"

(I've replaced some of the hex digits with Xs above)

Although the (OpenHome) version of the renderer appears in the Android BubbleUPNP app as expected when I try to send media to it the app hangs with a message "Adding to playlist" 

The very long renderer name is ugly, and I renamed it to "Lounge Sound" in the BubbleUpnp Server, but my short name seems to be ignored.

I haven't found the logs but if you let me know where to look then I can send them on

[SimBun]

I've just been playing around with two old Play 1's, helping people move away from the redesigned Sonos app :-)

I enabled OpenHome on a stereo pair and it works great. I'm using MinimServer but that shouldn't make any difference.

If you're just adding to Playlist I wouldn't have thought the renderer mattered at all, but with DLNA/UPnP there's a lot of moving parts.

I've never had the custom name work either.

[Steven Mackenzie]

I've managed to solve the problem - thanks for suggesting it can be done!

I found the most recent log file (/home/bubbleupnp/BubbleUPnPServer.log.0)

Some messages near to the end of the file had a clue (edited): 
WARNING : GetTransportStateTask: Lounge - Sonos Beam Media Renderer - RINCON_38420BFB310601400: org.fourthline.cling.c.a.c: Current
WARNING : Client connection was aborted: java.net.ConnectException: Connection refused (Connection refused): http://xxx.xxx.xxx.89:140
WARNING : GetTransportInfo: Error: Current state of service prevents invoking that action. Connection error or no response received.

The IP address in the connection refused message is not the IP of my Sonos speaker! I've reserved a fixed address for the Sonos in my DHCP configuration, powered it off and on again, deleted the Sonos (OpenHome) renderer, restarted BubbleUPnPServer, and turned Sonos (OpenHome) back on. And...

Now it works :)

[SimBun]

I've found that using Eventing ("Enable to make the retrieval of renderer state more CPU efficient") works well with Sonos.

When using BubbleUPnP Server you need to enable it in the configuration.xml.

<openHomeUseEventing>true</openHomeUseEventing>

In the app it's part of the renderer settings.

@BubbleSoft

It would be really nice if BubbleUPnP could hide the slave renderers that are part of a group/stereo pair. I know they can be hidden, but if you hide one then separate the speakers it will remain hidden.

I don't think you can use Sonos as a library, so maybe remove them from Libraries too.