This binding integrates LinkPlay-based audio devices (such as WiiM, Arylic, and many others) with openHAB 4.3+.
It provides playback controls, volume management, multiroom audio grouping, and device monitoring—all from the openHAB UI.
It is actually interesting that you have provided this binding because I had started the same thing (for my WiiM) 2 months ago until, during the implementation I noticed that there is already the generic upnp binding that does it for me.
It seems that your adds a bit more features Multiroom mgmt and monitoring and why did you not just use the upnp binding (just curious)?
Btw, I would recommend to link Linkplay, WiiM, Arylic in the binding docs, so in case, someone is interested, they can follow the link and see what devices these are.
The UPnP implementation is inconsistent across link play devices and often quits and craps out. The home assistant community has gone to an HTTP implementation as it’s rock solid. And I needed multi room control. I have 4 of these in my home and another 4 at that cottage. They are great
@mjcumming I had the same behaviour as you on using the UPnP with my Linkplay. Didn’t always work so I ended up not making it available in openHAB.
I’m glad you developed this binding. I own a Linkplay Muzo Cobblestone and once I have some time I will will be testing it.
Thanks @mjcumming can’t wait to try it! I was just trying to build the project locally, it looks like the git repo is missing a few files? There are missing import errors for
Before, I was using http binding to connect Wiim Amp to openhab, and now I tried the binding.
I have some observations:
Wifi Signal Strength is not showing anything
For shuffle and repaat are you using this: Arylic Audio HTTP API ? - I’m asking because as you see there are separate options for loop and loop once. I “implemented” that as an single channel with several states.
I think that it will be a good idea to add “preset” channel
I definitely would submit it as an official binding - I really need some additional testing against other setups and linkplay devices. I have the Wiim and Arylic devices and it seems good with that - however, I am certain we will find various problems somewhere
Yes, it uses standard UPnP device discovery followed by HTTP(S) to confirm the discovered device is a LinkPlay device. Note, if a device is a slave device during discovery, the slave will not be seen by UPnP.
First of all, I can confirm that binding works nicely with my WiiM Pro C490. So, good job
When I mentioned “auto-discovery” I actually meant discovering the binding as a proposed binding to be installed by scanning the network during startup of openHAB so it it will be shown under “Suggested Bindings”.
Ah, got it - the main issue I see is that determining if a device is a LinkPlay device just the UPnP discovery seems consistent - currently, the binding takes all UPnP renderers and then does an HTTP check for an endpoint on the device. I’ll look and see if there is away to discover common versions WiiM, Arylic (which I have)>