respark of Sonos compatibility
Hi
there is a necro thread from 2012 no less, on Sonos to Serviio compatibility Ive been studying,
https://forum.serviio.org/viewtopic.php?f=5&t=8120&p=56964&hilit=sonos&sid=c896bfb0ebe60d3e04f2ed0a9bb151d5#p56964
that has a half working profile created for Sonos product at the bottom..
Ive got the Serviio MS visible and folder content visible , but not able to play tracks. Error 701 unable to add to queue .
Any one have the Serviio / Sonos solution working well and cleanly ? Im reticent to 'drop my pants' and leave SMBv1 in Win 10 enabled to allow the Linux based Sonos devices to connect to Win 10 devices via SMB. V dodgy of Sonos not to sort this IMO .. Prob stuck with an old Linux build running on a miniature hardware footprint, with no room or capacity to grow to a new build .. Still , where they are with this is unacceptable ....
TIA and looking forward to your experiences..
there is a necro thread from 2012 no less, on Sonos to Serviio compatibility Ive been studying,
https://forum.serviio.org/viewtopic.php?f=5&t=8120&p=56964&hilit=sonos&sid=c896bfb0ebe60d3e04f2ed0a9bb151d5#p56964
that has a half working profile created for Sonos product at the bottom..
Ive got the Serviio MS visible and folder content visible , but not able to play tracks. Error 701 unable to add to queue .
Any one have the Serviio / Sonos solution working well and cleanly ? Im reticent to 'drop my pants' and leave SMBv1 in Win 10 enabled to allow the Linux based Sonos devices to connect to Win 10 devices via SMB. V dodgy of Sonos not to sort this IMO .. Prob stuck with an old Linux build running on a miniature hardware footprint, with no room or capacity to grow to a new build .. Still , where they are with this is unacceptable ....
TIA and looking forward to your experiences..