I installed 1.5 and control it via dlna with the wellknown android app “bubbleUpnp”.
Everything seems fine. One minor, albeit more optical problem is that within bubbleupnp, the volumio renderer is not shown under its proper name, but as null:updmpcli ??m
Actually I did rename and rebooted, and I think thats when the trouble started. BubbleUPNP, my DLNA controller on the network, does not recognize the name I gave to volumio, but always lists it as a renderer by the name of “null:upmpdcli” for some reason
What name did you give it ? There may be some illegal characters (in the computing and not the legal sense).
In the meantime I will test again but it has worked for me before.
Actually I have managed to reproduce the problem.
If the player name is blank (see below) then in Bobble the RENDERER name is displayed as “null: Upnpdcli”.
It also seems that the player name accepts spaces, underscores(_) and full stops (.)
I named it “volumio”. But now I renamed it again, restarted again and again the name was not correct. However, when changing the name and pressing the APPLY button, volumio issued a warning like “failed - background worker busy”
I named it “volumio”. But now I renamed it again, restarted again and again the name was not correct. However, when changing the name and pressing the APPLY button, volumio issued a warning like “failed - background worker busy”
Don’t work for me.
But if I the service mangement Airplay at On, the name is ok on the Upnp controleur point…
Strange. But it’s work with this setting… A problem with the server name with upnp ?
As I was the original poster I just wanted to say: Same for me, if I switch Airplay on, then the name of DLNA renderer is shown as I set it up in the menu.