SoundTouch Without Bose Cloud – Local Solution on Raspberry Pi 5

[pat-nm]

Bose SoundTouch Hybrid 2026 – Complete Installation Guide

SoundTouch Without Bose Cloud – Local Solution on Raspberry Pi 5

---

Background

On May 6, 2026, Bose shut down the cloud service for the entire SoundTouch product line. This means preset buttons, app control, and internet radio no longer work through the official channel.

This guide describes how to bring your SoundTouch speakers fully back to life using a Raspberry Pi 5, Music Assistant, and the open-source project Bose SoundTouch Hybrid 2026 – locally, without cloud, without subscription.

---

Supported Devices

Device | Support | Physical Presets -- | -- | -- SoundTouch 10 | ✅ Full | ✅ SoundTouch 20 | ✅ Full | ✅ SoundTouch 30 | ✅ Full | ✅ SoundTouch Portable | ✅ Full | ✅ Wireless Link Adapter | ✅ Via WLA Bypass | ➖ (no physical buttons) SoundTouch 300 / Soundbars | ⚠️ Limited | —

Tip: Starter kits at berrybase.de or thepihut.com often bundle all components cheaper than buying individually.

Not suitable: Raspberry Pi 4 with 1GB RAM, UGREEN NASync DH2300, Synology BeeStation – these do not support Docker with network_mode: host.

---

Part 2: Prepare the SD Card (on Mac/PC)

Install Raspberry Pi Imager

👉 Download and install from raspberrypi.com/software

Flash the SD Card

1. Insert the SD card into your computer

2. Open Imager and configure:

   • Device: Raspberry Pi 5
   • Operating System: "Raspberry Pi OS (other)" → "Raspberry Pi OS Lite (64-bit)"
   • Storage: your SD card

3. Before flashing, click "Edit Settings":

   • Hostname: soundtouch
   • Enable SSH ✅
   • Username: pi
   • Password: choose a secure password
   • Enter Wi-Fi credentials (if not using a LAN cable)

4. Start flashing (~2–3 minutes)

---

Part 3: Set Up the Raspberry Pi

Boot and Connect

1. Insert the SD card into the Pi
2. Mount the cooler and case
3. Connect the LAN cable (recommended)
4. Connect the power supply → wait ~60 seconds
5. Connect via SSH from your computer:

ssh pi@soundtouch.local

Type yes on first login, then enter your password.

Update the System

sudo apt update && sudo apt upgrade -y

Install Docker

curl -fsSL https://get.docker.com | sh
sudo usermod -aG docker pi
exit

Log back in:

ssh pi@soundtouch.local

Test Docker:

docker run hello-world

→ "Hello from Docker!" confirms successful installation.

---

Part 4: Install Music Assistant

Music Assistant (MASS) is the audio engine that manages streaming services and DLNA output.

Create the Docker Compose File

mkdir -p ~/music-assistant && cd ~/music-assistant
nano docker-compose.yml

Paste the following content:

services:
  music-assistant:
    image: ghcr.io/music-assistant/server:latest
    container_name: music-assistant
    restart: unless-stopped
    network_mode: host
    volumes:
      - ./data:/data
    cap_add:
      - SYS_ADMIN
      - DAC_READ_SEARCH
    security_opt:
      - apparmor:unconfined
    environment:
      - LOG_LEVEL=info

Save: Ctrl+O → Enter → Ctrl+X

Start Music Assistant

docker compose up -d

Music Assistant is now accessible at:

http://soundtouch.local:8095

Configure Music Assistant

Open in your browser and configure:

1. Music Sources → "+" → Add "TuneIn Radio"

   • Username: guest (no real account needed)
   • Free, no login required

2. Playback Provider → Enable DLNA/UPnP

Note: "Flow Mode" in newer MASS versions is configurable per device, no longer globally.

---

Part 5: Install SoundTouch Hybrid 2026

Install Node.js

Since the Docker image is only available for amd64, the app is run directly from source on the Pi:

curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt install -y nodejs
node --version  # should show v20.x.x

Download the Project

mkdir -p ~/soundtouch-hybrid && cd ~/soundtouch-hybrid
wget https://github.com/TJGigs/Bose-SoundTouch-Hybrid-2026/archive/refs/heads/main.zip
unzip main.zip
mv Bose-SoundTouch-Hybrid-2026-main soundtouch-hybrid-app
cd soundtouch-hybrid-app
npm install

Find the Pi's IP Address

hostname -I

→ Note the first IP, e.g. 192.168.0.168

Create Configuration

Step 1: Configure .env

On first start, the app automatically generates a config/.env:

npm start
# Wait until [Boot] Generated default .env appears, then Ctrl+C

nano config/.env

Adjust the following values:

APP_IP=192.168.0.168          ← Pi's IP address
MASS_IP=192.168.0.168         ← same IP
MASS_USERNAME=pi              ← Music Assistant username
MASS_PASSWORD=yourPassword    ← Music Assistant password
MASS_CONTAINER_NAME=music-assistant
WLA_PRESET_BYPASS=true        ← important for Wireless Link Adapter
AUTO_RESUME_PRESET=true       ← resume last station on power-on

Leave all other values (APP_PORT=3000, BOSE_PORT=8090, MASS_PORT=8095) unchanged.

Step 2: Configure speakers.json

nano config/speakers.json

Enter your speakers:

[
  { "name": "Living Room", "ip": "192.168.0.101" },
  { "name": "Kitchen", "ip": "192.168.0.102" },
  { "name": "Bedroom", "ip": "192.168.0.103" },
  { "name": "Wireless Link", "ip": "192.168.0.104" }
]

Important: Assign a fixed IP to each speaker in your router first (DHCP reservation by MAC address). MAC addresses are printed on the underside of each device.

Tip: Find speaker IPs with:

sudo apt install -y arp-scan
sudo arp-scan --localnet

Bose devices have MACs starting with 08:df:1f.

Set Up the App as a System Service

sudo nano /etc/systemd/system/soundtouch-hybrid.service

Content:

[Unit]
Description=Bose SoundTouch Hybrid 2026
After=network.target docker.service
[Service]

Type=simple

User=pi

WorkingDirectory=/home/pi/soundtouch-hybrid/soundtouch-hybrid-app

ExecStart=/usr/bin/node server.js

Restart=always

RestartSec=5
[Install]

WantedBy=multi-user.target

Enable and start the service:

sudo systemctl daemon-reload

sudo systemctl enable soundtouch-hybrid

sudo systemctl start soundtouch-hybrid

sudo systemctl status soundtouch-hybrid

→ active (running) confirms successful startup.

Open the Web Interface

http://192.168.0.168:3000/control.html

---

Part 6: Redirect Speakers to Local Server (USB Hijack)

This is the crucial step. Each speaker must be redirected once from the Bose cloud server to your local Pi.

Prerequisite: Speaker firmware must be up to date. If needed, update using the official Bose app beforehand.

Prepare the USB Stick (on Mac/PC)

1. Insert a USB stick into your computer

2. Format it using Disk Utility (Mac) or Disk Management (Windows):

   • Format: FAT32
   • Scheme: MBR (Master Boot Record)
   • Do not use exFAT or NTFS!

3. Create an empty file called remote_services (no file extension!) on the stick:

Mac:

touch /Volumes/YOUR_STICK_NAME/remote_services

Windows (PowerShell):

New-Item E:\remote_services -ItemType File

4. Safely eject the USB stick

Inject Configuration

For each speaker individually:

1. Insert the USB stick into the speaker
2. Restart the speaker (unplug and replug power)
3. Wait ~60 seconds
4. In the Hybrid web interface:
   • http://192.168.0.168:3000/control.html
   • Tab "Speaker Admin"
   • "Bose Cloud Emulation Setup"
   • Select the speaker from the dropdown
   • Click "⚡ Inject Configuration"
5. Success message: "Success! The script was injected and the speaker is rebooting."
6. The USB stick can be removed afterwards

Wireless Link Adapter: Does not support USB hijack via Telnet. The WLA_PRESET_BYPASS=true in .envhandles this automatically – no manual step required.

---

Part 7: Configure Presets

Add a Radio Station in Music Assistant

1. Open Music Assistant: http://soundtouch.local:8095
2. Radio → search for a station
3. Three dots (⋮) → "Add to Library"

Assign Preset in Hybrid App

1. Open Hybrid app: http://192.168.0.168:3000/control.html
2. Library Manager → "Search" tab
3. Search for the station → click "Save"
4. In "My Library" → assign the station to the desired slot (1–6)

Add a Station via Direct Stream URL

If a station is not available in TuneIn:

1. Library Manager → "Custom" tab
2. Enter the stream URL and name
3. Assign a preset slot

---

Part 8: Notes and Troubleshooting

Speaker Takes Longer on Cold Start

After powering on, the speaker needs some time to:

• Connect to Wi-Fi
• Reach the local Pi server
• Load presets and trigger AUTO_RESUME_PRESET

This is normal – once fully booted, it runs stably.

Preset Buttons Not Working After Power Cut

The speaker needs to reach the local server after booting. Wait ~60 seconds – the buttons will work again afterwards.

Station Not Found in Hybrid Search

Stations must first be added to the Music Assistant library. Only then will they appear in the Hybrid search (Strict Filter is ON by default).

Speaker Shown as OFFLINE

• Check fixed IP in router (DHCP reservation)
• Is the speaker powered on and connected to Wi-Fi?
• Restart the service: sudo systemctl restart soundtouch-hybrid

@ Symbol in Terminal (Mac) - my endboss ;-)

If ⌥ Option + L doesn't work:

• Terminal → Preferences → Profiles → Keyboard → Uncheck "Use Option as Meta key"
• Then: ⌥ Option + L for @

View Service Logs

sudo journalctl -u soundtouch-hybrid -n 50

sudo journalctl -u soundtouch-hybrid -f  # live log

Restart the Service

sudo systemctl restart soundtouch-hybrid

---

Architecture Overview

Press preset button

↓

Speaker queries local Pi server

↓

SoundTouch Hybrid 2026 recognizes preset request

↓

Music Assistant starts stream via DLNA/UPnP

↓

Music plays – no Bose Cloud, no app, no subscription

Raspberry Pi 5

├── Music Assistant (Port 8095)       ← Streaming engine

└── SoundTouch Hybrid 2026 (Port 3000) ← Bose Cloud emulation

├── Living Room (SoundTouch 30)

├── Kitchen (SoundTouch 20)

├── Bedroom (SoundTouch Portable)

└── Home Cinema (Wireless Link / Lifestyle)

---

Useful Links

• SoundTouch Hybrid 2026: https://github.com/TJGigs/Bose-SoundTouch-Hybrid-2026
• Music Assistant: https://music-assistant.io
• Raspberry Pi Imager: https://raspberrypi.com/software
• Berrybase (Pi Shop DE): https://berrybase.de
• The Pi Hut (Pi Shop UK): https://thepihut.com
• Radio Browser: https://www.radio-browser.info

---

Created May 2026 – based on hands-on installation with Raspberry Pi 5, Music Assistant v2.8.7 and SoundTouch Hybrid 2026 v3

Bose SoundTouch Hybrid 2026 – Complete Installation Guide

SoundTouch Without Bose Cloud – Local Solution on Raspberry Pi 5

Background

On May 6, 2026, Bose shut down the cloud service for the entire SoundTouch product line. This means preset buttons, app control, and internet radio no longer work through the official channel.

This guide describes how to bring your SoundTouch speakers fully back to life using a Raspberry Pi 5, Music Assistant, and the open-source project Bose SoundTouch Hybrid 2026 – locally, without cloud, without subscription.

Supported Devices

Device Support Physical Presets
SoundTouch 10 ✅ Full ✅
SoundTouch 20 ✅ Full ✅
SoundTouch 30 ✅ Full ✅
SoundTouch Portable ✅ Full ✅
Wireless Link Adapter ✅ Via WLA Bypass ➖ (no physical buttons)
SoundTouch 300 / Soundbars ⚠️ Limited —
Part 1: Hardware

Raspberry Pi 5 – Shopping List

Component Recommendation Approx. Price
Raspberry Pi 5 (4GB) Official Pi Foundation ~$90
27W USB-C Power Supply Official Raspberry Pi PSU ~$15
32GB microSD Card SanDisk Extreme A2 or Samsung Endurance ~$20
Case + Active Cooler Official Pi 5 Case + Active Cooler ~$15
LAN Cable (recommended) Any, Cat5e or better ~$5
Total ~$145
Tip: Starter kits at berrybase.de or thepihut.com often bundle all components cheaper than buying individually.

Not suitable: Raspberry Pi 4 with 1GB RAM, UGREEN NASync DH2300, Synology BeeStation – these do not support Docker with network_mode: host.

Part 2: Prepare the SD Card (on Mac/PC)

Install Raspberry Pi Imager

👉 Download and install from raspberrypi.com/software

Flash the SD Card

Insert the SD card into your computer

Open Imager and configure:

Device: Raspberry Pi 5
Operating System: "Raspberry Pi OS (other)" → "Raspberry Pi OS Lite (64-bit)"
Storage: your SD card
Before flashing, click "Edit Settings":

Hostname: soundtouch
Enable SSH ✅
Username: pi
Password: choose a secure password
Enter Wi-Fi credentials (if not using a LAN cable)
Start flashing (~2–3 minutes)

Part 3: Set Up the Raspberry Pi

Boot and Connect

Insert the SD card into the Pi
Mount the cooler and case
Connect the LAN cable (recommended)
Connect the power supply → wait ~60 seconds
Connect via SSH from your computer:
ssh pi@soundtouch.local
Type yes on first login, then enter your password.

Update the System

sudo apt update && sudo apt upgrade -y
Install Docker

curl -fsSL https://get.docker.com/ | sh
sudo usermod -aG docker pi
exit
Log back in:

ssh pi@soundtouch.local
Test Docker:

docker run hello-world
→ "Hello from Docker!" confirms successful installation.

Part 4: Install Music Assistant

Music Assistant (MASS) is the audio engine that manages streaming services and DLNA output.

Create the Docker Compose File

mkdir -p ~/music-assistant && cd ~/music-assistant
nano docker-compose.yml
Paste the following content:

services:
music-assistant:
image: ghcr.io/music-assistant/server:latest
container_name: music-assistant
restart: unless-stopped
network_mode: host
volumes:
- ./data:/data
cap_add:
- SYS_ADMIN
- DAC_READ_SEARCH
security_opt:
- apparmor:unconfined
environment:
- LOG_LEVEL=info
Save: Ctrl+O → Enter → Ctrl+X

Start Music Assistant

docker compose up -d
Music Assistant is now accessible at:

http://soundtouch.local:8095/
Configure Music Assistant

Open in your browser and configure:

Music Sources → "+" → Add "TuneIn Radio"

Username: guest (no real account needed)
Free, no login required
Playback Provider → Enable DLNA/UPnP

Note: "Flow Mode" in newer MASS versions is configurable per device, no longer globally.

Part 5: Install SoundTouch Hybrid 2026

Install Node.js

Since the Docker image is only available for amd64, the app is run directly from source on the Pi:

curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt install -y nodejs
node --version # should show v20.x.x
Download the Project

mkdir -p ~/soundtouch-hybrid && cd ~/soundtouch-hybrid
wget https://github.com/TJGigs/Bose-SoundTouch-Hybrid-2026/archive/refs/heads/main.zip
unzip main.zip
mv Bose-SoundTouch-Hybrid-2026-main soundtouch-hybrid-app
cd soundtouch-hybrid-app
npm install
Find the Pi's IP Address

hostname -I
→ Note the first IP, e.g. 192.168.0.168

Create Configuration

Step 1: Configure .env

On first start, the app automatically generates a config/.env:

npm start

Wait until [Boot] Generated default .env appears, then Ctrl+C

nano config/.env
Adjust the following values:

APP_IP=192.168.0.168 ← Pi's IP address
MASS_IP=192.168.0.168 ← same IP
MASS_USERNAME=pi ← Music Assistant username
MASS_PASSWORD=yourPassword ← Music Assistant password
MASS_CONTAINER_NAME=music-assistant
WLA_PRESET_BYPASS=true ← important for Wireless Link Adapter
AUTO_RESUME_PRESET=true ← resume last station on power-on
Leave all other values (APP_PORT=3000, BOSE_PORT=8090, MASS_PORT=8095) unchanged.

Step 2: Configure speakers.json

nano config/speakers.json
Enter your speakers:

[
{ "name": "Living Room", "ip": "192.168.0.101" },
{ "name": "Kitchen", "ip": "192.168.0.102" },
{ "name": "Bedroom", "ip": "192.168.0.103" },
{ "name": "Wireless Link", "ip": "192.168.0.104" }
]
Important: Assign a fixed IP to each speaker in your router first (DHCP reservation by MAC address). MAC addresses are printed on the underside of each device.

Tip: Find speaker IPs with:

sudo apt install -y arp-scan
sudo arp-scan --localnet
Bose devices have MACs starting with 08:df:1f.

Set Up the App as a System Service

sudo nano /etc/systemd/system/soundtouch-hybrid.service
Content:

[Unit]
Description=Bose SoundTouch Hybrid 2026
After=network.target docker.service

[Service]
Type=simple
User=pi
WorkingDirectory=/home/pi/soundtouch-hybrid/soundtouch-hybrid-app
ExecStart=/usr/bin/node server.js
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target
Enable and start the service:

sudo systemctl daemon-reload
sudo systemctl enable soundtouch-hybrid
sudo systemctl start soundtouch-hybrid
sudo systemctl status soundtouch-hybrid
→ active (running) confirms successful startup.

Open the Web Interface

http://192.168.0.168:3000/control.html
Part 6: Redirect Speakers to Local Server (USB Hijack)

This is the crucial step. Each speaker must be redirected once from the Bose cloud server to your local Pi.

Prerequisite: Speaker firmware must be up to date. If needed, update using the official Bose app beforehand.

Prepare the USB Stick (on Mac/PC)

Insert a USB stick into your computer

Format it using Disk Utility (Mac) or Disk Management (Windows):

Format: FAT32
Scheme: MBR (Master Boot Record)
Do not use exFAT or NTFS!
Create an empty file called remote_services (no file extension!) on the stick:

Mac:

touch /Volumes/YOUR_STICK_NAME/remote_services
Windows (PowerShell):

New-Item E:\remote_services -ItemType File
Safely eject the USB stick
Inject Configuration

For each speaker individually:

Insert the USB stick into the speaker
Restart the speaker (unplug and replug power)
Wait ~60 seconds
In the Hybrid web interface:
http://192.168.0.168:3000/control.html
Tab "Speaker Admin"
"Bose Cloud Emulation Setup"
Select the speaker from the dropdown
Click "⚡ Inject Configuration"
Success message: "Success! The script was injected and the speaker is rebooting."
The USB stick can be removed afterwards
Wireless Link Adapter: Does not support USB hijack via Telnet. The WLA_PRESET_BYPASS=true in .envhandles this automatically – no manual step required.

Part 7: Configure Presets

Add a Radio Station in Music Assistant

Open Music Assistant: http://soundtouch.local:8095/
Radio → search for a station
Three dots (⋮) → "Add to Library"
Assign Preset in Hybrid App

Open Hybrid app: http://192.168.0.168:3000/control.html
Library Manager → "Search" tab
Search for the station → click "Save"
In "My Library" → assign the station to the desired slot (1–6)
Add a Station via Direct Stream URL

If a station is not available in TuneIn:

Library Manager → "Custom" tab
Enter the stream URL and name
Assign a preset slot

Part 8: Notes and Troubleshooting

Speaker Takes Longer on Cold Start

After powering on, the speaker needs some time to:

Connect to Wi-Fi
Reach the local Pi server
Load presets and trigger AUTO_RESUME_PRESET
This is normal – once fully booted, it runs stably.

Preset Buttons Not Working After Power Cut

The speaker needs to reach the local server after booting. Wait ~60 seconds – the buttons will work again afterwards.

Station Not Found in Hybrid Search

Stations must first be added to the Music Assistant library. Only then will they appear in the Hybrid search (Strict Filter is ON by default).

Speaker Shown as OFFLINE

Check fixed IP in router (DHCP reservation)
Is the speaker powered on and connected to Wi-Fi?
Restart the service: sudo systemctl restart soundtouch-hybrid
@ Symbol in Terminal (Mac) - my endboss ;-)

If ⌥ Option + L doesn't work:

Terminal → Preferences → Profiles → Keyboard → Uncheck "Use Option as Meta key"
Then: ⌥ Option + L for @
View Service Logs

sudo journalctl -u soundtouch-hybrid -n 50
sudo journalctl -u soundtouch-hybrid -f # live log
Restart the Service

sudo systemctl restart soundtouch-hybrid
Architecture Overview

Press preset button
↓
Speaker queries local Pi server
↓
SoundTouch Hybrid 2026 recognizes preset request
↓
Music Assistant starts stream via DLNA/UPnP
↓
Music plays – no Bose Cloud, no app, no subscription
Raspberry Pi 5
├── Music Assistant (Port 8095) ← Streaming engine
└── SoundTouch Hybrid 2026 (Port 3000) ← Bose Cloud emulation
├── Living Room (SoundTouch 30)
├── Kitchen (SoundTouch 20)
├── Bedroom (SoundTouch Portable)
└── Home Cinema (Wireless Link / Lifestyle)
Useful Links

SoundTouch Hybrid 2026: https://github.com/TJGigs/Bose-SoundTouch-Hybrid-2026
Music Assistant: https://music-assistant.io/
Raspberry Pi Imager: https://raspberrypi.com/software
Berrybase (Pi Shop DE): https://berrybase.de/
The Pi Hut (Pi Shop UK): https://thepihut.com/
Radio Browser: https://www.radio-browser.info/
Created May 2026 – based on hands-on installation with Raspberry Pi 5, Music Assistant v2.8.7 and SoundTouch Hybrid 2026 v3

[Olivier7110]

Thanks for taking the time to write this step by step guide !

As newbie with containers, I've used "Portainer" which centralize and abstract some complexity related to command line usage to fetch and run the containers. It also includes a web interface with direct access to logs, resources usages, ... definitely something worth exploring.
As the step which comes right after is about monitoring Raspberry PI health.

[FranzStein]

Great work. Thanks for the details described.

I’ve also installed Music Assistant, and the open-source project Bose SoundTouch Hybrid 2026 on a Raspberry Pi. However, I used a Raspberry Pi 4B 4GB and made some additions to get access to my local NAS system, consisting of a Fritz!Box with a connected USB stick holding the music data to play. It works fine but let me explain the changes I made.

I installed Debian GNU Linux 13 (trixie) on the Raspberry Pi and installed Docker thereafter, as described in Parts 2 and 3.

Following Part 4, I additionally created a Fritz User that has access to the Firtz!Box NAS content only and then integrated FRITZ!Box NAS in Music Assistant.
To do this, I installed the cifs-utils package to mount and manage SMB (Server Message Block) network shares:

sudo apt update && sudo apt install cifs-utils

Create directory:

sudo mkdir -p /mnt/fritznas

Temporarily mount:

sudo mount -t cifs -o username='myFritzUserName’, password='myFritzUserPassword',vers=3.0 //fritz.box/FRITZ.NAS /mnt/fritznas

Mount Permanentely by adding the following lines to /etc/fstab:

# FRITZ!Box NAS MORE_MEDIA Musik Release
//192.168.178.1/fritz.nas /mnt/fritznas cifs credentials=/etc/nas-credentials,iocharset=utf8,vers=3.0,file_mode=0777,dir_mode=0777,noserverino,nofail,x-systemd.automount,x-systemd.mount-timeout=30,_netdev 0 0

The SMB Mount option ‘noserverino’ avoids a samba mount giving a stale file handle. My fritz!Box NAS Username and password are stored in /etc/nas-credentials.

My Docker Compose file looks as follows:

services:
  music_assistant:
  # Define desired release version here (or use beta to get the latest betacd etc version)
  # Locally compiled and stored image to allow for Raspberry Pi ARM Architecture
    image: ghcr.io/music-assistant/server:latest
    container_name: bose-mass
    restart: unless-stopped
    # Network mode must be set to host for MA to work correctly
    network_mode: host   # <--- Host Mode (Fixes the IP Address)
    # Limit log file size and amount of log files
    logging:
      options:
         max-size: "10m"
         max-file: "3"
    volumes:
      - ./data:/data    # <--- Keeps your Data safe
      - /mnt/fritznas/MORE_MEDIA/Music:/music:ro    # <--- Mounts Fritz!Box NAS in Music Assistant
    # privileged caps (and security-opt) needed to mount smb folders within the container
    cap_add:
      - SYS_ADMIN
      - DAC_READ_SEARCH
    # Solve Raspberry Pi / AppArmor conflict by #ing security_opt: und - apparmor:unconfined
    # security_opt:
    #  - apparmor:unconfined
    environment:
      - TZ=Europe/Berlin
      # Provide logging level as environment variable.
      # default=info, possible=(critical, error, warning, info, debug)
      - LOG_LEVEL=info

Again, there have been modifications necessary to avoid a Raspberry Pi / AppArmor conflict.

Following Part 5, I cloned the SoundTouch Hybrid 2026 files to local Bose directory:

git clone https://github.com/TJGigs/Bose-SoundTouch-Hybrid-2026.git bose

and build the corresponding Docker file within this directory:

docker build -t bose-soundtouch-hybrid:local .

I also changed the Docker Compose File to use this local arm64 installation and started the SoundTouch Hybrid 2026 in the Docker container.

.
.
.

services:
  bose-hybrid:
    # Default is normally 'latest' for fresh installs. However, to force
    # an update on your NAS changes it to the aspecific version (e.g., :v4)
    # Current version tag below is correct for this release: v3
    image: bose-soundtouch-hybrid:local
    platform: linux/arm64
    container_name: bose-soundtouch-hybrid
    network_mode: "host"

That’s it. Part 6, 7 and 8 are handled as described.

There is still a small issue in not fully playing the first song of an album, switching to the second song for whatever reason? But this seems to be Music Assistant related and as I already said, the Bose SoundTouch Hybrid 2026 works fine for me.

[TJGigs]

Thx for the info when I get back and after release the v3.4 to fix the most critical issues. 20 etc. I'd love to work with u raspberry guys to make sure I document and create the correct yml etc to make a raspberry install as turnkey as possible for raspberry users. Thx so much for documenting your setup and issues encountered.

[pczyk]

I can confirm that with v3.4, I did not need to build the image myself on a Raspberry Pi 4 anymore but could just take the official one.

[TJGigs]

Ok thx..so you are good to go then?

[pczyk]

Yes, it's working like a charm here!

[FranzStein]

Version 3.4 works perfectly for me as well. Updating the Raspberry Pi 4 was easy since I didn't have to build the image myself. I just downloaded the bose-soundtouch-hybrid.yml file and used it as is. After making the necessary updates to the .env file, I changed auto_resume_preset=true so the speaker starts with the last played preset when turned on. It’s also great that the USB hijack procedure is now automated. This made it incredibly easy to add a Bose SoundTouch 20 speaker to my home setup.
Thanks for the great work!

[TJGigs]

Thx...I’m still working other issues and then will start on the remaining/new bugs for v3.5 then enhancement request v4.. I want to get the app as turnkey and bullet proof as possible

BUT yes I’m going to get at least 1 more ST30 for sure (maybe more!) and probably another st10 that I really don’t want but need in order to build/test the enhancement request for st10 stereo pairing function

I imagine the used price of soundtouch speakers are really going to start dropping. There is already some on eBay. But hopefully I'll find ones local here (craigslist etc) in LA that I can go pick-up

[pczyk]

Man, thank you for your commitment! Please let us know how to support you :)

[Beijinghans]

Great work, saves hundreds of dollars to keep alive a basically fine sound system.

Having lots of ST10's in my home which used to run in stereo mode: Do you have an idea when stereo pairing will be available?

Thanks for info :-)

[CozadJeff]

This great. It's much better than the notes I took and sent to TJ. The only thing I'd add is to create a backup of the SD card either periodically or at the end of the installation. I'm using HDD Raw Copy Tool v2.6 on my Windows 11 machine.

I would also include a step to make the IP address of the Raspberry Pi and the Soundtouch devices static.

[TJGigs]

I would also include a step to make the IP address of the Raspberry Pi and the Soundtouch devices static.

I think i wrote that somewhere about the speakers in my setup and MA recommends that too... never thought about the server. Also some one in all these thread gave me a link to code to dynamically scan network for the speakers and grab their IP's as possibly a way for users to not have to have static speaker IDs...Ill play around with that at some point... WOrking on Bugs v3.5 and then v4 first

[CozadJeff]

Yeah… the reason I suggested this is that if the IP changes, it breaks the pseudo app since it has the original IP hard coded.

[jero-maerlant]

First of all also from my side a special thanks to you @TJGigs for all the effort and to @pat-nm for creating the Raspberry pi installation guide!

My installation wasn't a walk in the park till I reconfigured everything on a single Raspberry pi.
Therefore I want to give you following feedback as I believe that most of my issues were related because of the use of Windows dockers (and an altered SoundTouchSdkPrivateCfg.xml file?).

Windows dockers
For ease of testing I installed everything on a Windows machine, MA and the bose-soundtouch-hybrid-2026.
Therefore I needed to alter 'network_mode: host' → 'network_mode: bridge' in the yml files as Windows doesn't allow host mode.

Issue → the used multicast techniques in MA broke because of 'network_mode: bridge'. My players were not discoverable.
Resolution → I (initially solely) moved MA from Windows to HAOS (on a Raspberry pi) as I already had an HAOS installation running.

But... my presets were still not working. Diving into discussion #16 and looking at the screenshots I saw that my system was lacking a proper '/bmx/registry/v1/services' response but also 'GET /streaming/acount/.../full' didn't return anything (if I remember correctly).

Then I saw that you mentioned in that same thread that MA and bose-soundtouch-hybrid-2026 should be on the same machine. So, I reconfigured everything on a single Raspberry pi following the above installation guide.

This solution resolved all my of issues.

Restore SoundTouchSdkPrivateCfg.xml
Don't know if this one was actually needed to resolve my issues but prior to your installation I tried SoundCork where I manually needed to alter the '/opt/Bose/etc/SoundTouchSdkPrivateCfg.xml file' on the SoundTouch device.
When I ran into the problem of the improper BMX response I restored this file to its original state as yours was using the OverrideSdkPrivateCfg.xml.

I should mention that I performed that action when I still had the bose-soundtouch-hybrid-2026 in a Windows docker; I'm not sure if that action was really needed but wanted to share it anyway.

[TJGigs]

My solution no longer use the soundcork inject process modifing SoundTouchSdkPrivateCfg.xml or the OverrideSdkPrivateCfg.xml. (in fact the preflight Janitor function will remove that file)
everything is done now directy to the NVRAM (does not need USB sitck or anything)
You can do a force on your speakers and it will also trigger the Janitor cleanup