The fix should be available since the snapshot 1316.
have you managed to add it manually to your docker addons?
I’m currently also facing those issues.
I’m running now version 2.3.0 within a docker container and added the latest snapshot version of the sonos binding manually.
Problem is, that it is not showing in the bindings section of the paperUI but I find it with
bundle:list | grep Sonos
it is stated as “installed”. But when I try to activate it (via bundle:start) I’m getting exceptions like
unresolved requirement org.eclipse.smarthome.config.discovery.upnp
anyone an idea?
So, today after some research I found a way to start the manual added binding.
I had to install the upnp feature first:
feature:install esh-io-transport-upnp
Then I could start the sonos binding:
bundle:start 000 <- bundle id
1 Like
@sheppard
Thanks for that solution - this works for me too!
Sorry I didn’t get back to you. I work a full time job and I go to school in the evenings. So I pretty much only have the weekend to tinker around…
Hos do I implement this?
Just installed the patched sonos binding and it solved the problem for me too. Great, thanks!
Same issue. Could anyone link me the latest snapshot .jar file ?