Not compatible with Sonos S2 (just tested, see results) #763
Comments
|
It's definitely compatible with S2. I have also updated to S2 (and have been using the beta for a few months) and the API has and continues to work fine for me. All six of my zones on S2 are visible and work. I think you probably need to create a settings.json and include a "household" option to specify that the API should talk to your S2 system rather than your S1. There are instructions in the readme.md |
|
Thanks! I am trying it now. Did you fill in the full "household":"Sonos_xxxxxxxxxxxxxxxxxxxxxxxxxx", or only: "household":"Hwq03L0Xx3Sn5fcPE91ZKq2mxN.AGejB3sBSr_G1byFUvJR", ? |
|
I didn't need to add the household option to mine as mine defaulted to the S2 (probably because I set up my S2 first and only my S1 later). The docs seem to suggest that it should be in the format "Sonos_xxxx" One point to note: it does need to be a new file called "settings.json" you create to put this in. Don't get confused with the existing "settings.js". |
|
I can confirm that it does work with S2 too. Tried this morning. Quick question, is there a way now to play things on Sono's new "saved groups?" instead of using the http server join & leave commands to manually ungroup and group? |
|
Got another confirmation that S2 works with the API.. |
Playing around with this feature it seems like you select rooms upon choosing the |
|
I can confirm it works with S2. First it would want to discover... So I changed my settings.json with the "household": "" without any luck... later I removed it and suddenly it worked.. :( |
|
Worked for me too :) I didn't change any settings after the update to see if it worked as it is, and it did 👍 |
|
Works for me as well. |
|
Thank you everyone that has reported about S2. I'm kind of surprised that they didn't take the opportunity to move on from the UPnP protocol, makes me also wonder why the fuck they couldn't keep compatibility with older devices then... if they both use the same control mechanism. |
Hallo, I have read there is not enough system power or memory in the older devices. |
|
Does it mean, that i can do the update? On my Sonos ONE, the speak data point is not working right now. |
mit dem Datenpunkt im Adapter hat die Sonos API nix zu tun. |
|
Das weiß ich - die Frage war eigentlich ob ein Update "bedenkenlos" möglich ist. |
|
it works ! |
|
Looking forward to see more positive confirmations over time. |
I can confirm everything works. I tested Spotify, Text-To-Speech, presets,.. all working. |
|
For the folks that are still working, by any chance have you rebooted your rPi or router since the Sonos update? My setup broke after I temporarily lost power and curious if after the update everything continues to work until a reboot. Sorry in advance if this is not the right place to post this. I tried adding the household option into settings.json but it didnt help. Logs seem to show the program is terminating unexpectedly. 0 info it worked if it ends with ok |
|
@vkoi81 mine also broke after rebooting rPi (it wasn't able to discover the system) but was able to fix it after restarting just the npm server (restarting just this service) |
Thanks. I’ll give that a shot. You simply did an npm stop followed by npm start? |
|
Haven't tried, I did lose power for a second this afternoon but luckily my Pi's are connected to a UPS. |
Sorry about the delay. Yes! I'm using pm2 (and Ngnix) to run it in the background so I just restarted that |
I have a large Sonos system containing: mutliple One, Play 5 Gen1, Play 3, Beam, SUB, etc..
I just updated the compatible products to Sonos S2 (which means I did not upgrade the Play 5 Gen1, I migrated that one to a separate Sonos S1 system).
After the update:
http://192.168.5.5:5005/reindex gives
{"status":"success"}
http://192.168.5.5:5005/zones gives
[{"uuid":"RINCON_000************","coordinator":{"uuid":"RINCON_000*******************","state":{"volume":25,"mute":false,"equalizer":{"bass":0,"treble":0,"loudness":true},"currentTrack":{"artist":"","title":"","album":"","albumArtUri":"","duration":0,"uri":"","trackUri":"","type":"track","stationName":""},"nextTrack":{"artist":"","title":"","album":"","albumArtUri":"","duration":0,"uri":""},"trackNo":0,"elapsedTime":0,"elapsedTimeFormatted":"00:00:00","playbackState":"STOPPED","playMode":{"repeat":"none","shuffle":false,"crossfade":false}},"roomName":"Unnamed Room","coordinator":"RINCON_000*****************","groupState":{"volume":25,"mute":false}},"members":[{"uuid":"RINCON_000***************","state":{"volume":25,"mute":false,"equalizer":{"bass":0,"treble":0,"loudness":true},"currentTrack":{"artist":"","title":"","album":"","albumArtUri":"","duration":0,"uri":"","trackUri":"","type":"track","stationName":""},"nextTrack":{"artist":"","title":"","album":"","albumArtUri":"","duration":0,"uri":""},"trackNo":0,"elapsedTime":0,"elapsedTimeFormatted":"00:00:00","playbackState":"STOPPED","playMode":{"repeat":"none","shuffle":false,"crossfade":false}},"roomName":"Unnamed Room","coordinator":"RINCON_000************","groupState":{"volume":25,"mute":false}}]}]
(I masked private information using ******** )
Which means: I think I see a zone, maybe my 1x Play5 Gen1 ?
The other 20x speakers I can not see... I did not found any specifig information for the new S2 API, besided the: https://developer.sonos.com -> Reference. Which was updated in April 2020, that gives me the idea that only Cloud connection is possible... ?
The text was updated successfully, but these errors were encountered: