The limit for SONOS devices in a system is 32, regardless of connection mode(s).
You can run multiple systems on the same network, but they will not inter operate.
I read this online, not accurate? On Reddit haha. “You can create a different subnet with a proper routing table that should allow you to go past the 32 limit. You will need to get a managed switch. Even then, it gets tricky.”
What application or network layer component is restricting inter-device communications to 32 device? I had read that it might be multicast or UPNP being limited to 5 bits, therefore 32 devices, but on hardwired managed switch network can there be a way to bridge across multiple systems or such? Obviously there is massive bandwidth between all the devices with no latency or collisions, unlike with WiFi.
My understanding is that WiFi has to send the packets once per device as each device has its own cryptography key. Where on an Ethernet network, it makes sense that packets could be sent out to be received by a long list of devices, and maybe this list of recipients can only have 32 devices in it?
Sonos really needs to create an official way to support more devices. I myself and have talked to several professional installers who would blow past the device limit. Many of us enthusiasts would buy another 5-10 devices tomorrow if it was possible. Until then, we’re forced to have only one speaker in the garage or laundry room. How terrible 
Or maybe just a hardwired subwoofer to an Amp, not also a wireless Sub connected too.
Potentially, that might be possible with the changes being made to S2 devices, although they’d likely want to also support additional forms of IP addressing and WiFi, which requires modification of the kernel running on the speakers. I suppose, without looking in to it, this may be something they’re working on, with the recent updates to the firmware, but they’d likely probably would need to move extremely cautiously, since they’ve already caused a substantial furor recently. Time will tell, but I’m certainly not holding my breath, it would be a substantial rewrite of the current OS.
It certainly wouldn’t happen with S1 only devices, they don’t have enough space to run updated versions of SMB in their kernel.
It would be a huge effort, I’d expect. Not simply done.
Yeah, too bad they didn’t prioritize more than 32 before the app rewrite. And take more time to work on the app. I’m surprised that more people don’t complain about the 32-device limit. With a few home theaters in an average sized home, then speakers in all the bathrooms and such, that limit is just gone. I am trying to find efficiencies, like an Amp, but I still need a regular Sonos speaker to get voice control in every room. They should allow a Beam to be used as a surround speaker in an Amp room.
If they allowed past 32, I would add center speakers as well. Although there should be an amp with 3 channels. So many more things that are desired, but they are prioritizing simplicity. Ability to go larger would open them up to a whole new market. Although maybe even with hard wired, over 32 devices gets unstable?
The new Era 100 Pro with POE is a nice start/direction. Although I still prefer an outlet plus Ethernet port for every speaker installation (often mounted near the ceiling) because it provides unlimited power. The POE+ device looks to have some kind of power storing to get wattage for the bass hits. It’s not operating in a power surplus and I worry it wouldn’t handle the volume I demand in my areas when parties are ongoing.
The 32 device limit was, I believe, determined by the number of UPnP event subscriptions any device could have. The now-deleted advanced web pages on devices would show you the event tables, which was incredibly useful when trying to write apps for it.
UPnP is required? No other means of communicating? Obviously with all hard wired there is no need for anything other than directly accessing every node via IP and no latency or additional hops of relevance. All equipment is ultra fast with full duplex speed.
