A glitch again with the wired Connect Amp, and a strange one. I had disabled the WiFi on it, and this morning it was missing in the Matrix although the port LEDs were flashing as usual. I then turned on another wired unit and the Connect Amp reappeared on the Matrix with it. After some time I turned off the other unit, and Connect Amp is still on the Matrix, with WiFi now enabled to see how things fare in that status.

I shall also take a look at the 850 log and see what is there.

The 850 has not been turned off for over 24 hours now, and times are correctly set. The recent glitch happened some time in the last 12 hours, and for what its worth, this all that the 850 log shows:

The black mask shows the reserved IP address/subnet mask for 850, which has another question to ask per below.

I notice that the mods have deleted these IP addresses in the past in this thread as personal information - but is the reserved IP address disclosure - addresses that go 10.x.y.z - personal inasmuch as disclosing it will subject my device to be vulnerable to access from outside my network? I think not...

The /support/review request goes to one device, which polls the others before collating the results. It’s not unusual for it to run out of patience. If you want to see if a specific unit is responding try http://x.x.x.x:1400/status. This contains the raw data compiled by /support/review.

When it was missing in the Matrix, the Connect Amp was missing in the Sonos Controllers as well - both in the Mac and the Android. And when the other wired unit was powered on and it booted, both became visible in the Controllers.

If this happens again, I will see if the unit responds to the kind of request you suggest, but I suspect this wasn't just a matrix polling delay seeing the Controllers reflect it.

Also: I invoked the matrix only because I saw the unit missing in the controller.

All of today, there is nothing wrong in Sonos with the 850 having remained on all the time. So perhaps something else disturbed Sonos - these things can confuse by having more than one reason at times. 

I think these repeater/access point hybrids is often plagued with weird behaviors since they are cheap and are trying to solve problems that shouldn’t exist (think, backup DHCP server, wat?)

I had a Linksys RE2000 which is a repeater/bridge that had some weird problem where it would start blocking DNS queries from wired devices (when working as a bridge), which shouldn’t even occur. A correct access point shouldn’t even act on anything but layer 2 traffic.

I’m running my home network with 2 dedicated access points (TP-link Omada, EAP245) and a separate router, but even with a wireless router, I’ve had no problem running the EAP245 in addition to a wireless router. For bonus points, the EAP245v3 (not v1, but those are discontinued) also has 2 ethernet jacks, which means you could wire it in reverse (first EAP245, then your Sonos player) to get gigabit to the access point. 

The learning curve for these are higher though, and you need more experience setting them up. They are also a bit higher price point at around $80-$90. But, the basic principle for me stands, an access point should be as dumb as possible. The only reason they need an IP to begin with is for administrative purposes only, in all other aspects they should just transparently forward traffic between wifi and wire lan. Most consumer equipment fails on that part.

@jishi :As a networking layman, I had thought that WiFi access points will be simple things to do a simple job - and this was borne out by the AEX doing just that in access point mode - with router mode set to off -  without troubling Sonos.

Clearly this is not quite the case, but the WA850 has not troubled Sonos since my last post a day ago, so I am hoping that the one glitch after it replaced the RE205 was a one off caused by something else.

Finger crossed for now! 

Kumar,

Are you checking for duplicate IP addresses?

Yes. The tp links, in both cases had reserved IP addresses, also confirmed in their management apps, distinct to the ones assigned to Sonos units.

As of now, no more issues after the last solitary one 48 hours ago, after moving over to the wa850 unit.

A trouble free week with Sonos, with the WA850 working all the time; the one glitch must have been something else that troubled Sonos, seeing that it has not surfaced again.

I have bought and kept another 850 unit for the future seeing how well it works in its assigned role of WiFi access point wired back to the main router, also being excellent value for money. And obviously, for not troubling the wired Sonos system as the RE205 definitely did.

As far as I can tell, the trick here is the manual option offered in the 850 interface to turn off the DHCP server; an option missing in the 205. So, the obvious question: for anyone wanting to buy an access point to add to a home with a Sonos presence, how does one know in advance that such an option is offered for the device?

I guess reading the manual before purchase is your best bet. But not even then you could be sure what features they secretly implemented.

I will for sure be more awake when I have to replace the 850 units, hopefully years from now.

I expect my Apple Time Capsule base station to be a casualty soon as well, bought in 2011. The good thing now that I have run ethernet wires around the home for Sonos, and now leveraged these for better WiFi coverage via the AEX/850, is that any ordinary/cheap router with normal range will do - I don't need the expensive kinds with antennas sprouting all over or the mesh type.

Of course, Sonos compatibility is something to be alive to then as well.