Bose IP-based systems (SoundTouch, Lifestyle 600 / 650)

These Bose systems are controlled directly over IP from MyURemote. No RS232/TTL wiring and no Global Caché serial controller are required.

Overview

MyURemote integrates Bose SoundTouch and Lifestyle 600/650 as IP devices. Commands are sent over your local network to the Bose unit using the MyURemote gateway layer (the same mechanism used for other TCP/HTTP based devices).

In most installations you only need: the Bose device on the same LAN/Wi-Fi, its IP address, and the correct device definition in your configuration.

Use the standard IP device workflow

Configure your Bose IP-based system the same way as other IP-controlled AV devices in MyURemote: add the device, set the IP/port, test a command, and then use it in Zones, Buttons, Macros and Activities.

→ Open: How to configure IP-controlled devices

SoundTouch specifics (important)

SoundTouch uses “press / release” commands

Many SoundTouch actions behave like a remote control button: MyURemote sends a press command and immediately follows with a release. This makes volume and navigation actions feel natural and prevents the device from thinking a button is “held down”.

MyURemote tracks the active SoundTouch device (IP + MAC)

The SoundTouch handler keeps track of the current and previous device identity using cookies (IP and MAC). This is used to keep sessions stable when switching between multiple SoundTouch units or when an IP address changes (for example via DHCP).

  • CurrentSoundTouchIPAdress / CurrentSoundTouchMACAdress: the device MyURemote is currently controlling
  • LastSoundTouchIPAdress / LastSoundTouchMACAdress: previous device identity, used as fallback in some requests

Templates: dynamic substitution in requests

SoundTouch commands are built from a method header + content template. Before sending, MyURemote replaces placeholders such as:

  • {CurrentSoundTouchIPAdress}, {CurrentSoundTouchMACAdress}
  • {targetSoundTouchIPAdress}, {targetSoundTouchMACAdress}
  • {RemoteClient} (client identity used by some integrations)

This allows one device definition to work across multiple SoundTouch devices without hardcoding identifiers.

Timeout and “keepOpen” behaviour

The SoundTouch handler sends commands through the gateway with a configurable timeout. If no timeout is provided, MyURemote uses a default value (typically 60 seconds). Some commands can optionally control whether the TCP connection is kept open.

Supported product families

  • Bose SoundTouch products
  • Bose Lifestyle 600
  • Bose Lifestyle 650

Setup notes

  • Make sure the Bose device and the MyURemote host are on the same network (LAN/Wi-Fi).
  • If you control multiple SoundTouch units, consider assigning a fixed IP (DHCP reservation) to avoid unexpected changes.
  • If commands work intermittently, verify the configured port and confirm the device is reachable from the MyURemote gateway machine.

Troubleshooting

Nothing happens

  • Verify the Bose IP address is correct and reachable (same subnet/VLAN).
  • Check the configured port and make sure it matches your SoundTouch/Lifestyle definition.
  • Test with a simple command first (e.g. volume up / mute) before building macros.

Volume / navigation feels “stuck”

  • SoundTouch relies on press + release. If you only send “press” and never “release”, the device may behave as if the button is held.
  • In MyURemote this is handled automatically: every press is followed by a release call.

Switching between multiple SoundTouch devices behaves oddly

  • MyURemote stores Current and Last SoundTouch identity (IP/MAC) in cookies. If a device changed IP recently, clear the related cookies or re-open the configuration panel and test again.
  • Prefer DHCP reservations so each SoundTouch keeps the same IP.