独立教程:ZoneFoundry 不是 Sonos 的产品。兼容性会随产品和软件变化，动手之前请以 Sonos 官方的兼容性检查为准。獨立教程:ZoneFoundry 不是 Sonos 的產品。相容性會隨產品和軟件變化，動手之前請以 Sonos 官方的相容性檢查為準。Independent guide: ZoneFoundry is not a Sonos product. Compatibility changes with products and software, so check Sonos' official compatibility tool before acting.
开始之前開始之前Before you start
- 列一份清单:每台 Sonos 的型号和购买年份。没有这份清单，后面每一步都是猜。列一份清單:每台 Sonos 的型號和購買年份。沒有這份清單，後面每一步都是猜。Write down every Sonos product you own with its model and rough purchase year. Without that list, every step below is guesswork.
- 先跑一次 Sonos 官方的兼容性检查,不要凭记忆或论坛帖判断。兼容名单会变。先跑一次 Sonos 官方的相容性檢查,不要憑記憶或論壇帖判斷。相容名單會變。Run Sonos' official compatibility check rather than relying on memory or a forum post. The compatibility list changes.
- ⚠️ 本文涉及的部分操作不可逆。降级回 S1 通常做不到,拆分之后也不一定能原样合回去。⚠️ 本文涉及的部分操作不可逆。降級回 S1 通常做不到,拆分之後也不一定能原樣合回去。⚠️ Some steps here are irreversible. Downgrading back to S1 is generally not possible, and a system you split may not recombine exactly as it was.
「两套系统」到底係咩意思？「兩套系統」到底係咩意思？What does having "two systems" actually mean?
这不是同一套系统上的两个模式，是两套彼此独立的 Sonos 系统:各自有自己的房间、自己的服务授权、自己的 App。它们同在一个 Wi-Fi 下，但在软件层面互不相认。理解这一点，下面所有限制都会变得理所当然——它们不是 bug，是两套系统本来就不通。這不是同一套系統上的兩個模式，是兩套彼此獨立的 Sonos 系統:各自有自己的房間、自己的服務授權、自己的 App。它們同在一個 Wi-Fi 下，但在軟件層面互不相認。理解這一點，下面所有限制都會變得理所當然——它們不是 bug，是兩套系統本來就不通。This is not two modes of one system. These are two independent Sonos systems, each with its own rooms, its own service authorizations, and its own app. They sit on the same Wi-Fi but do not recognise each other at the software level. Once that clicks, every limitation below stops being surprising — they are not bugs, they are two systems that were never connected.
点样知道每台喺边一套？點樣知道每台喺邊一套？How do I tell which system each product is on?
在做任何决定之前，你需要一份准确的清单。凭型号名猜通常会出错——同一个产品名可能横跨几代硬件，而决定兼容性的是内部硬件，不是名字。在做任何決定之前，你需要一份準確的清單。憑型號名猜通常會出錯——同一個產品名可能橫跨幾代硬件，而決定相容性的是內部硬件，不是名字。Before any decision you need an accurate inventory. Guessing from the product name usually goes wrong: one product name can span several hardware generations, and compatibility is decided by the internals, not the name.
用官方兼容性检查,不要靠记忆用官方相容性檢查,不要靠記憶Use the official compatibility check, not memory
Sonos 提供官方的系统兼容性检查,它会直接告诉你系统里哪些产品能进当前平台、哪些只能留在 S1。这是唯一权威的判据。论坛帖和几年前的对照表都会过时，因为 Sonos 的支持范围会随软件版本变化。跑一次，把结果记下来。Sonos 提供官方的系統相容性檢查,它會直接告訴你系統裡哪些產品能進當前平台、哪些只能留在 S1。這是唯一權威的判據。論壇帖和幾年前的對照表都會過時，因為 Sonos 的支援範圍會隨軟件版本變化。跑一次，把結果記下來。Sonos provides an official system compatibility check that tells you directly which products in your system can move to the current platform and which must stay on S1. That is the only authoritative answer. Forum posts and comparison tables from a few years ago go stale, because what Sonos supports shifts with software releases. Run it once and write the result down.
留意软件版本号不一致是正常的留意軟件版本號不一致是正常的Different software version numbers are normal
如果你手上是一套混合但仍然统一的系统——也就是新旧产品都还在当前平台上——你会看到不同产品显示不同的软件版本号。这不是系统裂开了，也不影响它们一起分组播放。Sonos 现在会分别给现代产品和较旧产品推送各自的版本。看到版本号不一样就急着重置，是常见的自伤操作。如果你手上是一套混合但仍然統一的系統——也就是新舊產品都還在當前平台上——你會看到不同產品顯示不同的軟件版本號。這不是系統裂開了，也不影響它們一起分組播放。Sonos 現在會分別給現代產品和較舊產品推送各自的版本。看到版本號不一樣就急著重設，是常見的自傷操作。If what you have is a mixed but still unified system — older and newer products all still on the current platform — you will see different software version numbers on different products. That is not a split system and does not stop them grouping and playing together. Sonos now ships separate builds to modern and older products. Rushing to reset because the version numbers differ is a common self-inflicted wound.
确认你面对的是不是真的两套確認你面對的是不是真的兩套Confirm you really do have two systems
真正的拆分系统有一个明确特征:你需要两个不同的 App 才能看到全部房间。如果一个 App 就能看到所有房间，那你只有一套系统，接下来那些跨系统限制都不适用于你——你遇到的分组或播放问题另有原因，应该去查网络和服务，不要在这里绕。真正的拆分系統有一個明確特徵:你需要兩個不同的 App 才能看到全部房間。如果一個 App 就能看到所有房間，那你只有一套系統，接下來那些跨系統限制都不適用於你——你遇到的分組或播放問題另有原因，應該去查網絡和服務，不要在這裡繞。A genuinely split system has one unmistakable sign: you need two different apps to see all your rooms. If a single app shows every room, you have one system and none of the cross-system limits below apply to you — whatever grouping or playback problem you are chasing has another cause, and you should be looking at the network and your services instead.
有边啲係永远做唔到？有邊啲係永遠做唔到？Which limitations are permanent?
- 跨系统分组。S1 的房间和当前系统的房间不能编进同一组，任何设置都改不了。跨系統分組。S1 的房間和當前系統的房間不能編進同一組，任何設定都改不了。Cross-system grouping. An S1 room and a current-system room cannot be placed in the same group, and no setting changes that.
- 跨系统立体声对。组成立体声对的两只必须在同一套系统、而且型号相容。跨系統立體聲對。組成立體聲對的兩隻必須在同一套系統、而且型號相容。Cross-system stereo pairs. Both halves of a pair must be on the same system and be compatible models.
- 跨系统家庭影院。环绕音箱和低音炮必须和主音箱在同一套系统上。跨系統家庭影院。環繞喇叭和低音炮必須和主喇叭在同一套系統上。Cross-system home theater. Surrounds and a Sub must be on the same system as the primary speaker.
- 一个 App 管两套。要装两个 App,分别管理。这是设计如此。一個 App 管兩套。要裝兩個 App,分別管理。這是設計如此。One app for both. You need two apps and manage each system separately. That is by design.
- 把当前系统降级回 S1。产品一旦升上当前平台,通常无法退回 S1 加入旧系统。所以升级前一定要先确定你不需要它留在 S1 那边配对。把當前系統降級回 S1。產品一旦升上當前平台,通常無法退回 S1 加入舊系統。所以升級前一定要先確定你不需要它留在 S1 那邊配對。Downgrading back to S1. Once a product has moved up to the current platform it generally cannot go back to join an S1 system. Decide before you upgrade whether you need that unit to stay paired on the S1 side.
这些是可以处理的這些是可以處理的These you can actually fix
音乐服务在两套之间互相打断音樂服務在兩套之間互相打斷Service accounts interrupting each other
两套系统各自持有自己的服务授权，但如果你用的是同一个音乐账号、而且套餐只允许一路播放，那么在 S1 那边开始播，当前系统那边的播放就会被顶掉,反之亦然。这不是系统冲突，是那个音乐服务的单流限制。解法有两个:升级到允许多路的套餐，或者给两套系统各用一个不同的服务账号。兩套系統各自持有自己的服務授權，但如果你用的是同一個音樂賬號、而且套餐只允許一路播放，那麼在 S1 那邊開始播，當前系統那邊的播放就會被頂走,反之亦然。這不是系統衝突，是那個音樂服務的單流限制。解法有兩個:升級到允許多路的套餐，或者給兩套系統各用一個不同的服務賬號。Each system holds its own service authorizations, but if you use the same music account and its plan allows only one stream, starting playback on the S1 side will cut off playback on the current side, and vice versa. That is not a system conflict — it is the music service's single-stream limit. Two ways out: move to a plan that permits multiple streams, or give each system a different service account.
语音助手要分别配置語音助手要分別配置Voice services need separate setup
语音配置是绑在系统上的，不会跨过去。你在当前系统上配好的语音助手，不会自动出现在 S1 的房间上;S1 支持哪些语音服务也和当前系统不同。要两边都能用语音，就要在两套系统里各配一次,而且要接受两边能力不一样。語音配置是綁在系統上的，不會跨過去。你在當前系統上配好的語音助手，不會自動出現在 S1 的房間上;S1 支援哪些語音服務也和當前系統不同。要兩邊都能用語音，就要在兩套系統裡各配一次,而且要接受兩邊能力不一樣。Voice configuration is bound to a system and does not carry across. An assistant you set up on the current system will not appear on S1 rooms, and S1 supports a different set of voice services anyway. To have voice on both, configure it separately in each system and accept that the capabilities differ.
直连列表会同时列出两套的房间直連清單會同時列出兩套的房間Direct-control lists show rooms from both
某些第三方 App 的直连播放列表是按局域网发现来的，不认系统边界，所以会把两套系统的房间混在一起列出来。看起来像「终于打通了」，其实只是列表混排:你仍然不能把两边的房间编成一组。给房间起名时带上系统标识(例如在 S1 房间名后加个后缀)，能省掉很多误会。某些第三方 App 的直連播放清單是按區域網絡發現來的，不認系統邊界，所以會把兩套系統的房間混在一起列出來。看起來像「終於打通了」，其實只是清單混排:你仍然不能把兩邊的房間編成一組。給房間起名時帶上系統標識(例如在 S1 房間名後加個後綴)，能省掉很多誤會。Some third-party apps build their direct-control device list from local network discovery, which does not respect system boundaries, so rooms from both systems appear in one list. It looks like the two finally connected — they have not. You still cannot group across them. Naming rooms with a system marker, such as a suffix on the S1 rooms, prevents a lot of confusion.
本地音乐库要配两次,而且要求不同本地音樂庫要配兩次,而且要求不同Configure the music library twice, with different requirements
两套系统都要各自添加一次本地音乐库。要注意的是它们对共享协议的要求不一样:当前平台用较新的 SMB，S1 需要旧版。很多 NAS 出于安全已经默认关掉旧版协议——这就是「新音箱能读音乐库、老音箱读不到」的常见原因。要两边都能读，NAS 上可能要同时开启两代协议，而这有安全代价,值不值得由你判断。兩套系統都要各自新增一次本地音樂庫。要注意的是它們對共享協議的要求不一樣:當前平台用較新的 SMB，S1 需要舊版。很多 NAS 出於安全已經預設關掉舊版協議——這就是「新喇叭能讀音樂庫、舊喇叭讀不到」的常見原因。要兩邊都能讀，NAS 上可能要同時開啟兩代協議，而這有安全代價,值不值得由你判斷。Both systems need the local music library added separately, and crucially they require different sharing protocol generations: the current platform uses newer SMB while S1 needs the legacy version. Many NAS units now disable the legacy protocol by default for security, which is the usual reason newer speakers can read the library and older ones cannot. Supporting both may mean enabling both protocol generations on the NAS — that carries a security cost, and whether it is worth paying is your call.
应该点决定？應該點決定？What are my options, and how do I decide?
三条路，代价各不相同。维持拆分:零成本，但你要长期接受两个 App、不能跨系统分组。老设备在次要房间(例如车房、露台)时，这通常是最理性的选择。把够格的升上来:能进当前系统的产品全部迁过去，只留真的迁不了的在 S1。屋里大部分设备够格时值得做。换掉老的:代价最高，但换来一套完整、可全屋分组的系统。如果老设备正好在客厅这种主力位置,长期折腾的成本可能比换机更高。三條路，代價各不相同。維持拆分:零成本，但你要長期接受兩個 App、不能跨系統分組。舊裝置在次要房間(例如車房、露台)時，這通常是最理性的選擇。把夠格的升上來:能進當前系統的產品全部遷過去，只留真的遷不了的在 S1。屋裡大部分裝置夠格時值得做。換掉舊的:代價最高，但換來一套完整、可全屋分組的系統。如果舊裝置正好在客廳這種主力位置,長期折騰的成本可能比換機更高。Three paths with very different costs. Stay split. Free, but you live with two apps and no cross-system grouping. When the older gear sits in secondary rooms such as a garage or balcony, this is usually the rational choice. Move everything eligible up. Migrate every product that qualifies for the current system and leave only what genuinely cannot move on S1. Worth doing when most of the house qualifies. Replace the old units. The most expensive path, but it buys one complete system that can group across the whole home. If the older gear happens to sit in a primary room like the living room, the long-run cost of working around it may exceed the cost of replacing it.
不要用恢复出厂设置去「合并」两套系统。它不会让不相容的硬件变得相容,只会清掉房间名、分组、立体声对、家庭影院绑定和全部服务授权,然后你还是两套系统——只是要从零再配一次。先跑官方兼容性检查,由它告诉你哪些真的能迁。不要用回復原廠設定去「合併」兩套系統。它不會令不相容的硬件變得相容,只會清掉房間名、分組、立體聲對、家庭影院綁定和全部服務授權,然後你還是兩套系統——只是要從零再配一次。先跑官方相容性檢查,由它告訴你哪些真的能遷。Do not use a factory reset to "merge" the two systems. It will not make incompatible hardware compatible. It will wipe room names, groups, stereo pairs, home theater bonds and every service authorization — and you will still have two systems, only now you have to configure both from scratch. Run the official compatibility check first and let it tell you what can genuinely move.
官方参考官方參考Official references
- Sonos App 版本兼容性Sonos App 版本相容性Sonos app version compatibility
- 设置两套独立系统設定兩套獨立系統Set up separate S1 and current Sonos systems
- 并存的已知限制並存的已知限制Known limitations with separate systems
- 由 S1 升级到当前 App由 S1 升級到當前 AppUpdate to the latest Sonos app from S1
- 配合 NAS 使用配合 NAS 使用Use a NAS drive with Sonos
排查完了，日常控制其实可以更省事排查完了，日常控制其實可以更省事Once the network is fixed, the daily part can get easier
网络问题解决之后，剩下的是每天都要做的事：分组、切歌、调音量。ZoneFoundry 是一个 iOS App，这些操作说一句话就完成。直接连你现在的 Sonos，Bridge 是可选增强，不是必需品。網絡問題解決之後，剩下的是每天都要做的事：分組、切歌、調音量。ZoneFoundry 是一個 iOS App，這些操作講一句話就完成。直接連你現在的 Sonos，Bridge 是可選增強，並非必需品。Grouping, skipping tracks, adjusting volume — that is the part you actually repeat every day. ZoneFoundry is an iOS app that handles those in one sentence. It works with your existing Sonos; the Bridge is an optional upgrade, not a requirement.
下一步下一步Next
S1 与当前系统的完整对比 →S1 與當前系統的完整對比 →The full S1 vs current comparison →
分组失败的其他原因 →分組失敗的其他原因 →Other reasons grouping fails →
音乐服务连不上或播不了 →音樂服務連不上或播不了 →Music service won't connect or play →
ZoneFoundry 面向当前 Sonos 系统的控制能力，不能把 S1 和当前系统合并成一套,也不会绕过上面那些平台边界。ZoneFoundry 面向當前 Sonos 系統的控制能力，不能把 S1 和當前系統合併成一套,也不會繞過上面那些平台邊界。ZoneFoundry targets current Sonos control capabilities. It cannot merge S1 with the current system and does not bypass any of the platform boundaries above.