Hi Philippe,
I'm trying to get to grips with the UPnP Bridge plugin, squeeze2upnp under LMS/Daphile running on a QNAP TS431P2 NAS (Linux version Linaro armv71). The Daphile clients run on a few laptops.
And for once I read the Squeeze2upnp UserGguide!
Through the WebUI I did not get nearly all UPnP devices that are present on the network. So, after reading the user guide, I thought I would try via the SSH console.
After sorting everything out, eventually I ran the command:
./squeeze2upnp-armv6hf-static –i –x config.xml
(as per user guide, this binary is also automatically selected in the web UI)
...and ended up with a file called -x. After renaming the file to config.xml, not trivial given the file name -x, I still ended up with an incomplete list. All devices were turned on etc.
I then thought I could edit the config.xml file to add the missing UPnP devices manually (though I don't know if this will work). However, In the file I see that MAC addresses are required. One of the missing UPnP devices is a network streamer called SMSL DP3. It uses gmediarender and HiBy streaming firmware. It has a very nasty quirk, though: every time it boots up, it has a different MAC address! Its UUID remains the same as far as I can see , however.
So I really have two questions:
config.xml file?LMS 7.9.2 on the QNAP NAS is a separate, stand-alone media server, and can be used by daphile directly but also by other UPnP clients (with BubbleUPnP as control point).
Thanks & best regards
Marco
I barely look at tickets here, it would be better if you move either to github or (better) to the squeezebox forums. But, in a nutshell
1/ The command line you've set is incorrect, the -i parameter requires a filename and here it believes that -x is the filename ...
2/ You cannot manually add player in config file
3/ the mac address hange should not be a problem b/c I'm using UUID to identify players and to build a "fake" mac for LS, s it should stay the same all the time.
4/ If it's not detected, it either ona different (sub)network or does not respond to discovery requests