I'm afraid we haven't tested dLeyna with a Onkyo/Samsung device, although we do test against other Samsung products without any (well many) problems. As I don't have one of these devices, I can only guess as to what the problem might be.
It could be that your code is working with XBMC and not the Onkyo as AFAIK XBMC is UPnP compliant where as Onkyo is DLNA compliant and I think DLNA devices require the meta data argument.
To do this you will need to update to the new dLeyna components. There are 4 components that need to be built.
> Can you give a small example how I should modify this for open_uri_ex?To call the new open_uri_ex method you first need to retrieve the meta-data from rygel. You can do this using mediaconsole.py in dleyna-server/test/dbus.
./mc.sh
> upnp = UPNP()
> upnp.servers()
# This should print a list of servers. Find the path for the
# Rygel server and type. The path will be
# /com/intel/dLeynaServer/server/0 if you only have one server.
> root = Device("/com/intel/dLeynaServer/server/0")
# Now you need to find the path for the file you are trying to play.
# The easiest way to do this it to use the tree command which does
# a depth first search of the entire DMS.
> root.tree()
# Note down the path of the file you are interested in, e.g.,
# /com/intel/dLeynaServer/server/0/232323
> obj = MediaObject("<PATH OF FILE>")
> obj.print_meta_data()
You should see the meta data of the file you want to play on the Onkyo.
Now you just need to provide this as the second parameter to renderer-console's open_uri_ex command, e.g.,
> renderer.open_uri_ex(args.playURI,"<META DATA>")
> Also, is there a way to select a renderer by UDN? Or even "Friendly Name"?Not currently, but I do have some code to do this. I'll update mediaconsole and renderconsole.
> Using UDN would to me make more sense then the device path, which a
> transient, where UDN is permanently unique identifier of a device....