Thanks Paul.
It seems that my post was not entirely clear so I will clarify.
The DLNA server on the B2 is working well.
The DLNA/ UPnP interoperability guidelines talk about about three major pieces to the architecture of digital media delivery; Media Server, Media Renderer, and Control Point.
This is a very good description
https://audiophilestyle.com/ca/ca-academy/the-complete-guide-to-hifi-upnp-dlna-network-audio/
In my scenario:
Media Server = B2
Media Renderer = Yamaha Receiver
Control Point = Media Monkey 5 running on a Windows 10 PC
The Control Point acts as the “controller” to manage the digital media. It can see both the DLNA compliant media sources (Media servers) and compliant target rendering devices (Media renderers). It should have the smarts to know whether the format of the media source is one which the renderer can render (e.g. mp3, flac etc.) and some like Media Monkey can offer functionality to convert the source, if required, for the renderer.
It is the DLNA/UPnP Control Point functionality that I am asking to be added to the B2 functionality as part of the Web UI.
This would potentially allow the B2 to not only share its only locally stored media but media from other DLNA visible media sources on a shared network. It could also send that media to any DLNA compliant renderer on your network.
DLNA’s advantage is that it does not have the proximity constraints of Bluetooth as it uses your own TCP/IP network.
DLNA is not as Mark seems to believe “a marketing department's wet dream” but an established way of sharing digital media and supported by a number of large volume and niche AV suppliers.