soundtouch-api-expert

To construct Bose SoundTouch API XML payloads, you must format endpoint-specific schemas for HTTP port 8090, applying capability checks before sending volume, source selection, or zone management commands.

WebSocket messaging for Bose SoundTouch operates via the gabbo protocol on port 8080. It pushes real-time speaker state changes, allowing you to monitor now playing status and device updates without polling the HTTP API.

You can integrate Bose SoundTouch with Homebridge by adapting its plugin behavior to use the Web API. This involves mapping HTTP 8090 endpoints and WebSocket 8080 notifications to Homebridge accessory states for speaker management.

The best way to discover Bose SoundTouch devices is using SSDP and mDNS discovery protocols. These protocols broadcast and listen for device announcements on the local network, returning IP addresses and device capabilities for API control.

SoundTouch API requests fail when XML payloads do not match endpoint-specific schemas or when capability-gated endpoints are called without prior capability checks. Validate your XML structure and verify device support before sending control commands.

You need to check device capabilities before calling SoundTouch multi-room zone endpoints. Capability-gated endpoints require validation to ensure the speaker supports zone operations, preventing failed XML payload submissions and API errors.