SoundTouchPlus Integration

FYI - just released a new version of the SoundTouchPlus integration

Note - If you are using the SpotifyPlus integration, you will also need to update it as well since it uses the underlying Spotify Web API Python library.

[ 1.0.72 ] - 2024/11/20

  • Updated underlying spotifywebapiPython package requirement to version 1.0.121.

FYI - just released a new version of the SoundTouchPlus integration

Note - If you are using the SpotifyPlus integration, you will also need to update it as well since it uses the underlying Spotify Web API Python library.

[ 1.0.73 ] - 2024/12.02

  • Updated underlying spotifywebapiPython package requirement to version 1.0.122.
  • The above spotifywebapiPython package will now return an exception due to the functions being deprecated by the Spotify development team. More information can be found on the Spotify Developer Forum Blog post that was conveyed on November 27, 2024. The following methods will now raise a SpotifyApiError exception due to the Spotify development team changes: GetArtistRelatedArtists, GetTrackRecommendations, GetTrackAudioFeatures, GetFeaturedPlaylists, GetCategoryPlaylists, GetGenres. The following properties were also marked as deprecated for the same reason: TrackSimplified.PreviewUrl.
  • Due to the above chnages made by Spotify, any Algorithmic and Spotify-owned editorial playlists are no longer accessible or have more limited functionality. This means that you can no longer obtain details via the SpotifyClient.GetPlaylist and SpotifyClient.GetPlaylistItems methods for Spotify-owned / generated content (e.g. ā€œMade For Youā€, etc). A 404 - Not Found error will be returned when trying to retrieve information for these playlist types.

did you pull the update? Github and my Home assistant only detect 1.72 as the latest

@Diegocampy
Apologies - I forgot to create a new release on github. I just created it, so the update should now be available in HACS.

Thanks for letting me know, and apologies for the confusion.

1 Like

FYI - just released a new version of the SoundTouchPlus integration

Note - If you are using the SpotifyPlus integration, you will also need to update it as well since it uses the underlying Spotify Web API Python library.

[ 1.0.74 ] - 2024/12/06

  • Updated underlying spotifywebapiPython package requirement to version 1.0.123.

FYI - just released a new version of the SoundTouchPlus Integration

Be sure to check out the SoundTouchPlus Card Dashboard as well.

Note - If you are using the SpotifyPlus integration, you will also need to update it as well since it uses the underlying Spotify Web API Python library.

[ 1.0.101 ] - 2025/03/07

  • Added service get_audio_dsp_controls. Gets the current audio dsp controls configuration of the device.
  • Added service get_bass_level. Gets the current bass level configuration of the device.
  • Added service get_device_info. Gets basic device information.
  • Added service get_supported_urls. Gets the supported urls configuration of the device.
  • Added service set_audio_dsp_controls. Sets the current audio dsp controls configuration of the device.
  • Updated smartinspectPython package reference to smartinspectpython for PyPi.org requirements.
  • Updated spotifywebapiPython package reference to spotifywebapipython for PyPi.org requirements.
  • Updated underlying bosesoundtouchapi package requirement to version 1.0.74.
  • Updated underlying smartinspectpython package requirement to version 3.0.35.
  • Updated underlying spotifywebapipython package requirement to version 1.0.184.

FYI - just released a new version of the SoundTouchPlus Integration

Be sure to check out the SoundTouchPlus Card Dashboard as well.

Note - If you are using the SpotifyPlus integration, you will also need to update it as well since it uses the underlying Spotify Web API Python library.

[ 1.0.120 ] - 2025/06/06

  • Added service play_url_dlna. Play media from the given URL via the Bose DLNA API. This also allows you to set source-specific metadata (artist, album, track, and cover art url) for the playing UPNP content. Note that only HTTP URL’s are supported (HTTPS is not, due to Bose DLNA limitations).
  • Updated service play_url to update HA state after processing, as state changes were not updating in a timely manner (or at all in some instances) after the service completed.
  • Updated underlying bosesoundtouchapi package requirement to version 1.0.79.
1 Like

FYI - just released a new version of the SoundTouchPlus Integration

Be sure to check out the SoundTouchPlus Card Dashboard as well.

Note - This version will only work with HA 2025.7.0 and above, since HA updated the urllib3>=2.0 requirement.

[ 1.0.133 ] - 2025/07/02

  • Updated requirements: from urllib3>=1.21.1,<1.27 to urllib3>=2.0. Due to Home Assistant Core 2025.7.0 update requirements.
  • Updated underlying bosesoundtouchapi package requirement to version 1.0.81.
  • Updated underlying spotifywebapipython package requirement to version 1.0.222.
2 Likes

Thanks! I was just about ready to report this to you. I’ll update next time I’m on.

1 Like

Sorry to be the bearer of (potentially) bad news …

Just received a notification from Bose about ā€œSoundTouch support discontinuedā€ as of 02/18/2026. More Information can be found here on the Bose site.

I’m pretty sure this will break SoundTouch Spotify streaming / functionality. I’m not sure if the API control will be broken or not. The following line in their Q&A is concerning:

ā€œOther features like SoundTouch streaming and app control, will no longer function.ā€

Here’s an excerpt of the important stuff:

Bose SoundTouch support discontinued

On February 18, 2026, Bose will discontinue cloud support for all SoundTouch products. Until that date, your system will continue functioning as usual, including access to cloud-based features through the SoundTouch app.

After February 18, certain features — including access to integrated music services like Spotify and TuneIn, as well as multi-room playback — will no longer be available. However, if your SoundTouch product supports BluetoothĀ®, AUX, or HDMI, you’ll still be able to enjoy high-quality audio playback from connected devices.

First introduced in 2013, SoundTouch systems have delivered more than a decade of reliable, room-filling sound. As we continue to evolve our connected product platforms, changes like this may happen and we want to ensure you have a clear understanding of what to expect.

Hi Todd,
I just got that end of life notice. It really sucks!! It set me on a quest that led to you.
I’m hoping someone might be able to advise me on a simple workaround.

I’ve got Bose SA-5 amplifier. Without the SoundTouch app, I cannot change inputs. So, being a daring newbie, I asked AI for advice.

The port for 8090 and INFO responds well.
I’m trying to use TASKER to send an http request POST.
I can succeed in deselecting the aux input, but cannot seem to select an aux input to work.

Here’s what AI advised. Any insights??

http://192.168.86.22:8090/select
Content-Type:application/xml

And in BODY I have:

[Carat Symbol] ContentItem source=ā€œAUXā€ sourceAccount=ā€œAUX_LINE_IN3ā€ isPresetable=ā€œfalseā€/ [Carat symbol → I don’t know how to display when those symbols are included ;-/ ]

…
The above is based on AI instructions:

I don’t know anything about home integration and haven’t added any special apps. I just want something really simple: change input, maybe on/off or volume. I’m hoping that is doable… but I’m stuck. Any help???

Thanks a million!!!

p.s. actually, I just now added the Header: "Content-Type:application/xml "
With that addition, it turns off the SA-5 unit, rather than merely deselecting the Input port.

Again, I’m trying to do this using TASKER.

@bkaz88
Have a look at my SoundTouch WebServices API Guide; it lists examples for almost all of the supported SoundTouch web-services endpoints.

You might want to issue a command to list your available sources as well:

http://192.168.86.22:8090/sources

I have never worked with an SA-5 Amp before, so not sure if it will work. The port 8090 call with the INFO response bodes well though.

I think the Key Press / Release service is what you want. It simulates a remote control key press and release. Note that you have to make 2 calls (in quick succession) - one for press, and one for release.

For example:

  • This will send the AUX_INPUT key press value.
    http://192.168.86.22:8090/key
    use this POST body:
<key state="press" sender="Gabbo">AUX_INPUT</key>
  • This will send the AUX_INPUT key release value.
    http://192.168.86.22:8090/key
    use this POST body:
<key state="press" sender="Gabbo">AUX_INPUT</key>

Here’ some PostMan console log output if it helps. I am not familiar with Tasker, so can’t advise you there. This is for the PRESS command, using POWER (versus AUX_INPUT like you want).

POST /key HTTP/1.1
Content-Type: application/xml
User-Agent: PostmanRuntime/7.45.0
Accept: */*
Cache-Control: no-cache
Postman-Token: 5cbf77ad-4062-46f9-ab96-4096ee8c6d03
Host: 192.168.1.81:8090
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Content-Length: 322
 
<key state="press" sender="Gabbo">POWER</key>
 
HTTP/1.1 200 OK
Content-Type: text/xml
Date: Fri, 10 Oct 2025 19:52:38 GMT
Cache-Control: no-cache,must-revalidate
Expires: Thu, 26 Oct 1995 00:00:00 GMT
Transfer-Encoding: chunked
Server: Allegro-Software-RomPager/5.40b1
Access-Control-Allow-Origin: http://192.168.1.81
Access-Control-Allow-Headers: Content-Type
Connection: close
 
<?xml version="1.0" encoding="UTF-8" ?><status>/key</status>

Hope it helps!

1 Like

Thanks Todd. AI got me thru the basics (aux input, on/off, volume…) on a phone menu based in Tasker… so very happy about that. And your treasure chest of details will certainly help further, pairing new BlueTooth, etc. And if I need to get my Lifestyle going beyond what the Remote allows, I’ll definitely need your info.

Thanks a million!

1 Like

And the million dollar question, do you think the APIs will work after they yank SoundTouch? :crossed_fingers::crossed_fingers::crossed_fingers:

1 Like

@bkaz88
I know just as much as you at this point. Hopefully they will come out with something more detailed prior to the February 2026 date.

If I had to guess (based on my current knowledge of the SoundTouch technology), I would say this only affects streaming services that utilize their cloud services to communicate with outside players (Spotify, Pandora, Deezer, Sirius XM, etc), as well as their multi-room playback. I believe most of the other things happen locally on the device (DLNA streaming, device control / volume / input switching, etc). But that is just a guess.

The easy way to tell what would be affected is to unplug your router from the external internet, run through the various integration functions, and see what breaks. Simple as that.

Good idea on disconnecting the modem… I hadn’t thought of that. I’ll give that a try. The multiple room capability had concerned me, for my two rooms, but newer Bluetooth can connect to both devices at the same time, so that should be helpful.
As you had said, I too am hopeful that a lot will work without SoundTouch on the SA-5. Next I’ll start scratching my head about my Lifestyle 535. That has a remote control, so that helps quite a bit already. For one, I’ll be curious if you can pair a new Bluetooth device by simply selecting BT as a source.

Thanks again for your help!

1 Like

The enshitifcation from Bose sounds to be complete. According this article the app will also completely stop working :put_litter_in_its_place:

According to a Bose FAQ, the associated SoundTouch app will no longer work from 18 February 2026. This means the devices will lose their ā€œsmartā€ capabilities

https://www.heise.de/en/news/From-smart-to-dumb-Bose-no-longer-supports-the-SoundTouch-product-family-10750937.html

If you can control the app locally and set the presets accordingly it would be still kind of smart.

The question is if you can still configure the necessary settings (wifi, presets, etc) without the app in a local basis.

The question: Is it possible today to setup this devices without app? :thinking:

The app will be de-published next year and the back end services (ā€œcloudā€) turned off. Most users will probably be left with a dumb speaker at this point :man_dancing:

Happily I’ve successfully set up controls on my phone for the SA-5, using Tasker. And it works with the Internet disconnected.

But now the Lifestyle 535 Series 3. It has been a nightmare finding APIs that work.

Does anyone know if there are any resources to help with the old Lifestyle 535 Series 3?

Thanks in advance!
Bill