Bugzilla – Bug 819
UPnP support via SN
Last modified: 2011-01-14 19:12:34 UTC
I could be commiting pergery here. Slim has it's own protocole, how about the intel uPNP ?
perjury would be lying under oath, so no fear of committing that here. Marking as an enhancement.
rewording summary, to make it easier to remember the request.
I think it is a good idea. I see more and more uPNP Servers and Clients. Examples: Hermstedt Hifidelio, Philips Streamium devices (http://www.streamium.com/),... More information about uPnP: http://en.wikipedia.org/wiki/UPnP http://www.upnp.org/ Would be good, if the Squeezebox would also support it, so that you can connect to other servers as well.
another UPnP server (public beta) is available: EyeConnect software enables your UPnP� AV digital media device to stream EyeTV recordings, digital photos, music and movies from your Mac onto your TV or stereo. EyeConnect Public Beta http://www.elgato.com/index.php?file=products_eyeconnect Seems to work with D-Link DSM-320 MediaLounge, Philips Streamium SL400i and Philips Streamium MX6000i.
Marking items that aren't going to be addressed immediately in 6.1 as future. Please update if this is in error or the bug has already been addressed.
I too would love to see Squeezebox supporting UPnP. It would allow access to all my Smartlists and play stats from J River Media Center, which can acts as a UPnP server. I hope this request isn't forgotten.
Shouldn't this be a bug on Product "SqueezeBox(2/V3)". IMO support for UPnP-client in the hardware/firmware is far more important that support for UPnP-server in SlimServer. (or should two separate bugs be created)
I think you're right, Carel. I voted for this enhancement assuming it was a vote for Squeezebox to support UPnP as a *client.*
Hi I'd assume Squeeze would get both ends working as uPNP,
has this idea been abandoned? surely logitech knows how to use upnp expertly?
It's extremely unlikely we will add a UPnP client to the firmware. Our products are designed to work with SqueezeCenter.
Changing the title of this bug. The idea is to support local UPnP devices on the LAN while connected to SqueezeNetwork. Thus you will be able to access local music without SC. In addition to SN work, this will need some additional firmware work to handle broadcast packets and some bug fixes in the HTTP request code. No idea when we'll get around to this, so leaving it as Future.
I wrote up a quick spec for what I think is required in the firmware to properly support UPnP via SN, and how it will work: Server -> Player: pnps (UPnP Search), 2 params: mx: max wait time (default 3) st: search string (default 'urn:schemas-upnp-org:device:MediaServer:1') Player opens a UDP multicast socket on 239.255.255.250 port 1900. Player multicasts search request on this socket: M-SEARCH * HTTP/1.1$CRLF Host: 239.255.255.250:1900$CRLF Man: "ssdp:discover"$CRLF ST: $st$CRLF MX: $mx$CRLF $CRLF All media servers on the player's LAN should immediately multicast their details. Other UPnP packets will also be received on this socket from things like routers, etc. Player -> Server: PNPR (UPnP Response) Player passes-through all packets received on the multicast socket. Server will be responsible for all parsing and filtering of packets. Player will continue to listen and pass-through all multicast responses until pnpx command is received or the connection with the server is lost. Server -> Player: Server will interact with the UPnP server using the existing 'http' command to perform standard HTTP SOAP requests. These are returned to Server via the BODY command. Player should be able to handle any size response by streaming it to Server in chunks of 1K or so. Server -> Player: pnpx (UPnP Shutdown), no params Closes multicast socket, stops listening for multicast packets.
Dean and I realized that the first request sent should just include the address and raw request to send, so: pnpr( ip, port, request )
Firmware support added in r4473. Still needs some more work on the firmware http command and a lot more work on the SN side.
Would love UPnP Client support on the Squeezebox. then I wouldn't need to change NAS-server, which is what's currently puts a halt in my plans on getting a Squeezebox..
With Squeezebox Touch have a built-in tiny SqueezeCenter ... will the existing UPnP renderer code remain in? This would then mean that Touch should be able to access 3rd-party UPnP-AV servers (and even pass info out to other SB).
HELLOOOOO????!!!! The start of this is from Feb 2005 & still hasn't implemented yet??? Received yesterday Logitechs Squeezebox Radio to incredulous recognize this things always needs a fully powered up PC/ Windows Home Server. I am using for a 85 € WiFi radio integrated UPnP from my DSL router since 2 years & now this??? Logitech which even once was at the forefront of Bluetooh headsets etc. is totally disregarding global warming & wants users to keep their PC always powered up??? If there isn't anything to be changed QUICKLY, I foresee a lot of resend devices to the internet resellers. Like I'll do within the next 2 weeks. Happily to have such consumer friendly laws here in Germany when such a for me formerly high image company like Logitech doesn't have any consumer feeling anymore.... Why am I writing like this? Because I've spent the whole day to try to figure out how I can connect this 200€ device to my UPnP server which was a 3 minutes exercise w/ my 85€ device...... And in the first place I thought RTFM, but then I recognized even there it isn't written in clear words....
why won't fix? i thought there was a desire to make local music available via SN and upnp? disappointing.