-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Available SIDs #7
Comments
Unfortunately I haven't found a way to see which SID are in use/were used when setting up the service. The Sonos documentation recommends "Valid values are 240-253, and 255 inclusive." |
You can use my new library to list the current services.
Got this list with the following code. const SonosDevice = require('@svrooij/sonos').SonosDevice
const XmlHelper = require('@svrooij/sonos').XmlHelper
const sonos = new SonosDevice(process.env.SONOS_HOST || '192.168.x.x')
sonos.MusicServicesService.ListAvailableServices().then(resp => {
var musicServiceList = XmlHelper.DecodeAndParseXml(resp.AvailableServiceDescriptorList)
musicServiceList.Services.Service.forEach(s => {
console.log('ID: %d => %s', s['_Id'], s['_Name'])
})
console.log(JSON.stringify(musicServiceList.Services.Service, null, 2))
}) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Folowing your form contents from https://michaeldick.me/sonos-nprone/ I used the SID 255 as given. I get a resonse Error 400 Bad Request. I double checked by entry of your data in the form and tried it 3 times. I did find the hint in one of your open issues that both Overcast and your NPR One service CAN be used. The issue is both can’t use the SID 255. You suggest 252. I tried 252 and my form submission succeeds. I couldn’t figure out how to get a list of SIDs in use or available.
Now, this isn't so much an issue for your code, but the Sonos service configuration.
The remove service process on your page needs us to remember this SID. Is there a place in the Sonos Settings dialogs to recover the SID?
The text was updated successfully, but these errors were encountered: