Connect:AMP keeps cutting out...all components hardwired

Hi @Gerald Harmon 

The Service Pack released on the 24th Jan only contained security fixes, so I have no idea (well, one - see below) why you don’t hear any more interruptions on your Connect:AMP. I was thinking the same as @Kumar, however:

I looked at the diagnostics you sent and I see no evidence of the errors I was seeing before. I do rather suspect that they will come back though, but I will be happy (and a little confused) to be proved wrong.

I don’t see any commands for the Connect:AMP to play, however - did you test playback with it as part of a group? I don’t see it grouped in the diagnostic, but you may have disbanded the group before submission. Testing in a group may have made a positive difference if previous testing was done in “Deck And Garage” alone, or with “Deck And Garage” being the first listed in the group (and thus in charge of the entire group), as it will have been doing less “work” as a secondary member of a group.

Uh, by the way, the diagnostics contain all the system info you posted, and much more besides. We recommend that you do not share serial numbers on the community as they can be used as identifying information when calling in to our support team.

@Corry P yeah sorry was just trying to be helpful.  perfectly fine to remove all of that from my post if it streamlines.

with that said, i was trying before (as suggested) to never let the C:A devices “take the lead” on any playback.  both now and before, letting a newer device take the lead then adding a C:A device to the group.  working now….wasn’t then.  agree with the gift horse, but still seems very coincidental that an update applied and I have better functionality than before over quite a long test period.

FWIW, i use the desktop app (Windows) as well as iOS, and I used the desktop app to update.  I use the desktop app most mornings, as part of a routine, and when I see the “Update” option, I generally go ahead and apply.  The option wasn’t there last week….

PS can’t believe the Company hasn’t replied to my tweet yet.  I tried!

Hi @Gerald Harmon 

Hey - no problemo! I appreciate the attempt at assistance - it’s just that serial numbers are best kept private. Ironically, you censored your local IP addresses which don’t tell anyone a thing - the majority of all local IP addresses are very similar (my gateway address, for example, is 192.168.0.1 - likely the same as yours, which doesn’t really tell anyone anything). The other common range is 10.0.0.x.

I won’t argue that it’s weird, that’s for sure! I hate to be a naysayer, but I think further testing will produce the same errors again.

The Sonos app is like a remote control - it just sends your commands to speakers, and reports back what they want to tell you. It’s the speakers themselves that handle the update process (see the Associated Product at the top of your system info? - that’s the unit that will be relaying commands from the app to the system, and it can change each time you open the app as it’s just the first product to respond to the app asking “is there anybody there?”).

I believe the update availability is somewhat staggered so as to avoid flooding our servers with simultaneous updates from every system - that may be why you didn’t see the update until recently.

I hope this helps.

Hi Corry

its clear that this is now firmly on Sonos’s radar and that something is in the works.

you did hint elsewhere that each users mileage may vary.  This is a little worrying, and I’m just wondering if Sonos consider the C:Amps as viable products or end of life?  In short, will the fix — fix?  Or only for the lucky ones ? 
 

thanks

andrew 

Hi @Andrew-s 

I appreciate that you want to find out more, but I really don’t have that information, nor do I personally know enough about it to guess (not that I would share a guess publicly).

There is an update coming very soon - I recommend waiting for it and seeing how things go then.

Please remember that I did point out that you were probably off-topic for this thread - that means that whatever I say here doesn’t really apply to your situation.

I hope this helps.

Perhaps you should send a service update to owners or pop up in this website to let them know a fix is coming so people hold off dumping their faulty units that may be a fixed by a firmware update. 

Good suggestion if taken on board!

What? No love for the 172.16.0.0 /12 range?

It is really a good option as almost no (none I have seen) consumer devices default to the 172 range on reset so it reduces the chances of conflicting devices / networks.

Virgin Media an ISP in the U.K. do not allow a user to change the subnet range on their latest routers, it’s fixed to 192.168.0.XXX - users can change the last octet for DHCP allocation, but that’s about all - I just use their device as a modem and have my own router, but it seems like ISP’s here, do not want users to tinker too much with the settings - it’s all becoming quite restrictive. It probably reduces support training and calls into their support system, I guess?

Even DHCP reservation is limited to 16 devices only on their new WiFi 6AX router. 

T-Mobile’s 5G internet solution here in the states doesn’t allow reserved IP addresses, either. My guess is they think it is too dangerous to allow folks to muck around. My guess is there is a small number of folks who actually know what they are doing, and they don’t want to deal with the unwashed masses.