After firing the CEO due to the app rollout disaster, is there a new team in place or is this a dead company? The app is still basically a home hobbyist app -- 10s delay to select anything to play. Pretty much always broken when trying to manage a large multi-zone set-up.
Please just open source the stack and let someone else take over. I’d like to build and open source an alternative controller.
The app is still basically a home hobbyist app -- 10s delay to select anything to play. Pretty much always broken when trying to manage a large multi-zone set-up.
That’s not fair to the “home hobbyist” app like Phonos and SonoPhone as they have been much more reliable than the Sonos app ime.😀
There have been several updates since the original release of the 80.x version controller for S2. See release notes here.
S1 has received a lot of bug fixes as well.
While the updated App may not start as fast as the original, a 10 second struggle suggests that your network could be better optimized for SONOS.
You can build your own controller if you like. SONOS publishes the necessary details — check the Developer Portal.
+16There have been several updates since the original release of the 80.x version controller for S2. See release notes here.
S1 has received a lot of bug fixes as well.
Why even do any updates on the crappy Sonos app when one can use Clic, SonoPhone, or SonoPad and have zero issues and no lag.. works excellent.
+16While the updated App may not start as fast as the original, a 10 second struggle suggests that your network could be better optimized for SONOS.
You can build your own controller if you like. SONOS publishes the necessary details — check the Developer Portal.
No lag at all with the 3rd party apps many are using…
I’d like to know which part of your post is an answerable “question” and which is just your “opinion”. 🤔
+24You can build your own controller if you like. SONOS publishes the necessary details — check the Developer Portal.
Not really. You can’t publish a decent controller app with the public cloud API as, for one, you can’t enumerate music from anywhere. (Plus eventing is a nightmare). The APIs are there, somewhere (see the web app) but Sonos don’t document 90% of them.
You can build your own controller from the not-documented-any-more UPnP API, as many of us have done :-)
Thanks for the clarification. Do you think the UPnP capability will eventually be removed?
+24Thanks for the clarification. Do you think the UPnP capability will eventually be removed?
They can’t remove it until they disable the Desktop apps, and has been a stated goal for several years now. However, Desktop remains a common ‘solution’ to issues with the mobile app, and while that remains true they will have to keep them around.
From what I can tell, the cloud API sits on top of an encrypted version of the UPnP APIs (along with a bunch of management stuff) so ‘removing’ UPnP might actually be a high-risk engineering task for the Devices folks - given the tragic affects of rewriting the mobile apps there may not be a great appetite for a similar brain-swap of the Device software.
Obviously S1 will always use UPnP so those systems are safe from such possibilities.
I suggest updating to 85.0-64200 from May
It fixed all of those pesky issues I still had with grouping speakers, delays, volume changes at times etc.
Starting a new song: it loads instantly and snappy.
Speakers now load instantly when I open the app (currently playing song, volume eq/sub settings etc.)
Spotify Connect also has gotten a lot better on my network.
Feels like finally found solutions to many of the issues I've had. I'm curious if yours were fixed, too?
This update is listed as a precursor to future updates and a required prestep. I assume it's the mentioned prestep to removing the upnp api but I could be dead wrong.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
