![]() You could, if you choose, replace it with a BOOST, which can operate under either S1 or S2, or, you could just remove the BRIDGE completely by either wiring a cable to one of your other S2 capable devices, or change your connection method from wired (the BRIDGE or a speaker) to WiFi, by following the instructions in the wired and wireless modes FAQ. If you desire to update to S2, you need to power off and disconnect your BRIDGE. It will always fail in an attempt to update to S2. The BRIDGE, along with certain other devices, continues to be an S1 only device. This is a one way trap door, the system works with some version, one tries to install an updated version - that fails - yet it is no longer possible to run with the older version - even though it was working! This update is something I CHOSE to try (because the Roam was not working) so by definition the existing version did work - at least - with the non-roam devices. See? I cannot choose “Just continue running with current version” why? Now I have no system, can listen to no music and was planning on a restful Christmas alone this year to do some reading and studying, without Sonos this really messes up what would have been a restful period for me. I’m a very experienced software engineer so before people rush in to defend Sonos don’t bother, this is abysmal, with today’s technology the customer experience can be far far better than it is. I submitted a diagnostic and the code I got back was: 703555998 perhaps that can shed light. Now the system can’t find jack s**t, it cannot see even one of the devices. If these error codes mean something then why not pull down the message text and display it in the controller software?Įverything was working but I have a Roam that fully discharged, I recharged it yet it was not visible in either the PC controller or the iPhone controller, as I tried to get more insight it kept suggesting I update so I tried. “Error code 30: BRIDGE” or “Error code 1002: BRIDGE”. The PC software is not S2 yet that also fails and the error code I get varies each time.Į.g. The iPhone fails (I think) because the controller is “not S2 compatible” whatever that means. ![]() If I try the same update from my iPhone, again it fails. I tried to update because the PS controller software insists that I update, yet it always fails. Of course to complain means I’ll get asked lots of questions, I’ll be asked to unplug this and that, connect this or that to something else with a piece of cable and so on and so forth, all the burden is on the customer. The hoops we have to jump through to get something working is absurd. The Sonos software and update process is a piece of junk, there’s imply no way it should behave as it is, the lack of attention to detail is astonishing. Yet again the wonderfully robust and user friendly software messes up my day. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |