I did - it’s broken, so is Intel’s original links. It’s a mess. But, I’ve managed to find the file, I just wanted to warn that it’s not so easy to get.
It works for me. Send me a PM wigh your email.
As I’ve said, I’ve got the file, but it wasn’t that easy unless you accept tracking.
I have a Yamaha av receiver can I help you? What do you need?
I think I’ve managed to create a working magnet link for it:
magnet:?xt=urn:btih:412672ce89df433f83dc11fc6611a51798faf7ac&dn=DeveloperToolsForUPnPTechnologies
I’m not sure, I have an Onkyo myself, but it seems that only a few UPnP devices use “embedded devices”, which is where the problem lies. I’ve been told that Marantz and Denon does this, I don’t know about Yamaha. To find out if the Yamaha does this (which I frankly doubt), you’d have to install some UPnP tool (like the one I just provided a magnet for (Windows)) and paste some output showing the UPnP information for the device.
After a few hours, it suddenly works for me too. Even after restarting openHAB. Don’t ask me why 
But I’m still skeptical. I’m waiting for Nadahar’s results.
What can also happen when you switch version is that you end with multiple version of bundle in your installation. It’s why I ask you a bundle:list to verify this point. It happens to me a few day ago, and in the case the openhab behavior is not always deterministic. But i think that most of time it load the old version, that will prevent the new one to Activate.
Laurent.
My Yamaha RX-A820 does not have any child devices.
1 Like
Sonos devices have child devices and I noticed no problem with snapshot 4952. Channels are updated as expected by the Sonos binding
Yes, but as I have explained, I don’t think the current solution will ever “work properly”, because there is a logic mismatch between how OH and jUPnP works. So, I’m trying to address that, and get things to work without this “mismatch”: