-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ en
Nothing. OpenCloudTouch is free and open source (Apache License 2.0). You just need a Raspberry Pi or other device to run it.
For initial setup: Yes (to download the Docker image).
During operation: Yes, for internet radio. Radio stations are streamed via the internet. However, controls (switching presets, volume, etc.) work without internet on the local network.
Yes — all Bose SoundTouch models use the same API. Primary testing was done with the SoundTouch 10, but SoundTouch 20, 30, 300, Portable, and Wave SoundTouch should all work.
Yes! A single OCT installation can manage any number of SoundTouch speakers. Swipe between devices in the web UI.
The SoundTouch series has been discontinued for years and the cloud service has been shut down. Warranty has likely already expired in most cases. Additionally, the changes are reversible — the setup process creates a backup.
Recommended: Raspberry Pi 4 or Raspberry Pi 5 with at least 2 GB RAM. A Raspberry Pi 3 also works but is slower.
Yes! Any device that supports Docker can run OCT: Synology NAS, TrueNAS, QNAP, Unraid, an old laptop — even a cloud server (though without automatic device discovery).
Recommended: Yes. Your SoundTouch speakers regularly try to communicate with the OCT server. If the Pi is off, presets won't work. Power consumption of an RPi 4 is about 3-5 watts — that's less than $1 per month.
Yes, with Docker Desktop. However, automatic device discovery (SSDP) doesn't work on Windows — you'll need to enter speaker IP addresses manually. For permanent operation, we recommend a Raspberry Pi or NAS.
The setup modifies your SoundTouch speaker’s configuration so it communicates with your local OCT server instead of the (discontinued) Bose Cloud. Specifically:
- The server URL is redirected (from Bose servers to your OCT server)
- Some DNS entries are locally redirected
Yes. The setup process creates a backup of the original configuration. This backup can be used to restore the speaker to its original state at any time. If Bose ever reactivates the cloud service, you can switch back.
No. The USB stick is only needed once per device to enable SSH. After setup, you can remove the stick and use it for other purposes.
Yes, the setup must be run for each device individually. It takes about 5-10 minutes per speaker.
OpenCloudTouch uses RadioBrowser.info — a free community directory with over 30,000 stations worldwide. You'll find virtually all well-known stations: BBC, NPR, Classic FM, and many more.
Yes! The hardware buttons (1-6) on your SoundTouch speaker work exactly as before. Press the button — the programmed station plays.
Currently only internet radio (via RadioBrowser) is supported. Spotify, Apple Music, Deezer, and other services are planned for the future.
Yes, it may take 1-3 seconds for a station to start playing after switching presets. This is due to the connection setup with the radio stream and is normal.
Yes. OCT communicates with the speakers over the local network. Both must be on the same network (or at least the same subnet).
- Check that OCT and the speaker are on the same network
- Check that the speaker is powered on
- Restart the speaker (unplug, wait 10 seconds, plug back in)
- Try manual IP entry under Settings
- More tips: Troubleshooting
Docker can handle networking in two ways: in an isolated network or in the host network. For automatic device discovery (SSDP/UPnP), OCT must run in the host network. This means the container shares the network with the host system (e.g. the Raspberry Pi). This is safe and the recommended configuration.
No. OCT communicates exclusively locally with your speakers. The only exception: radio stations are streamed via the internet (this happens directly between the speaker and the radio server, without routing through OCT). The radio search uses the public RadioBrowser.info API.
OCT runs exclusively on your local network and is not reachable from the outside (unless you actively open ports in your router — which is not recommended). There is no login because access to your local network already serves as authentication.
- Troubleshooting — Technical problem solving
- GitHub Issues — Report bugs or request features
- GitHub Discussions — Ask the community
🇩🇪 Benutzerhandbuch
🇬🇧 User Guide
Development
API & Architecture
- REST API
- ADR 001 Clean Architecture
- ADR 002 FastAPI App State
- ADR 003 SSDP Discovery
- ADR 004 React/TS/Vite
Technical Reference
Legal