homeassistantcomponent_spotifyplus: spotifyplus.zeroconf_device_connect bluesound no longer working

System Health details

System Information

version core-2025.7.1
installation_type Home Assistant OS
dev false
hassio true
docker true
container_arch amd64
user root
virtualenv false
python_version 3.13.3
os_name Linux
os_version 6.12.35-haos
arch x86_64
timezone Europe/Amsterdam
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.5
Stage running
Available Repositories 2104
Downloaded Repositories 27
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 16.0
update_channel stable
supervisor_version supervisor-2025.07.1
agent_version 1.7.2
docker_version 28.3.0
disk_total 112.7 GB
disk_used 28.9 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board generic-x86-64
supervisor_api ok
version_api ok
installed_addons File editor (5.8.0), Terminal & SSH (9.18.0), ESPHome Device Builder (2025.6.3), Dynu DNS (1.0.1), Piper (1.6.2), Mosquitto broker (6.5.1), Network UPS Tools (0.14.1), Whisper (2.6.0), WireGuard (0.12.0)
Dashboards
dashboards 3
resources 12
views 17
mode storage
Network Configuration
adapters lo (disabled), enp1s0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth77fc25c (disabled), veth73b4917 (disabled), veth7735383 (disabled), vethd799b62 (disabled), vethd53a9c5 (disabled), veth6303170 (disabled), veth475e06d (disabled), vethee45ea2 (disabled), vethe3f7158 (disabled), veth1072a24 (disabled), veth5f95be2 (disabled), veth4d743d6 (disabled), veth3350936 (disabled), veth1dff643 (disabled)
ipv4_addresses lo (127.0.0.1/8), enp1s0 (192.168.1.10/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth77fc25c (), veth73b4917 (), veth7735383 (), vethd799b62 (), vethd53a9c5 (), veth6303170 (), veth475e06d (), vethee45ea2 (), vethe3f7158 (), veth1072a24 (), veth5f95be2 (), veth4d743d6 (), veth3350936 (), veth1dff643 ()
ipv6_addresses lo (::1/128), enp1s0 (fe80::6f92:cb9:b0c1:e789/64), docker0 (fe80::5843:20ff:fee8:3e3a/64), hassio (fe80::b88d:b7ff:fe6c:1c0f/64), veth77fc25c (fe80::c40c:92ff:fe16:5a57/64), veth73b4917 (fe80::34c7:adff:fe1d:23f0/64), veth7735383 (fe80::c023:7ff:fe49:c972/64), vethd799b62 (fe80::a864:c1ff:fe72:8df7/64), vethd53a9c5 (fe80::dc36:27ff:fe91:8853/64), veth6303170 (fe80::a07e:3bff:fe71:622b/64), veth475e06d (fe80::dca5:bff:fe24:ed2/64), vethee45ea2 (fe80::fcf1:36ff:feb8:2cc1/64), vethe3f7158 (fe80::d888:f4ff:fe37:d5c9/64), veth1072a24 (fe80::8c52:25ff:fe69:7877/64), veth5f95be2 (fe80::4887:faff:fe75:d8e6/64), veth4d743d6 (fe80::64f6:79ff:fe65:acff/64), veth3350936 (fe80::2c5b:72ff:fee7:9cf2/64), veth1dff643 (fe80::3406:2eff:fe90:3d48/64)
announce_addresses 192.168.1.10, fe80::6f92:cb9:b0c1:e789
Recorder
oldest_recorder_run 28 juni 2025 om 15:40
current_recorder_run 10 juli 2025 om 18:39
estimated_db_size 5578.73 MiB
database_engine sqlite
database_version 3.48.0
SpotifyPlus
integration_version v1.0.139
clients_configured 1: Ronald (premium)
api_endpoint_reachable ok

Checklist

  • I have enabled SmartInspect debug logging for my installation.
  • I have filled out the issue template to the best of my ability.
  • This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
  • This issue is not a duplicate issue of any previous issues…

Describe the issue

After updating my Bluesoud player, HA and Spotifyplus, SpotifyPlus can no longer connect to my Bluesound device via zeroconf_device_connect. Error message: ZeroconfGetInfo: SpotifyError=“8” Status=“202” StatusString=“ERROR-LOGIN-FAILED” ActiveUser=“” Aliases=[] Availability=“” DeviceId=“” SupportedDrmMediaFormats=[] Connecting to device using Spotify works OK. After that, spotifyplus can connect too, but after a while, Spo tify disappears from source list for device, and spotifyplus can no longer connect. This used to work, so updating must have caused this.

Reproduction steps

In developer tools:

action: spotifyplus.zeroconf_device_connect
data:
  entity_id: media_player.spotifyplus_ronald
  host_ipv4_address: 192.168.1.26
  host_ip_port: 11000
  cpath: /spotifyconnect
  username: ...
  loginid: ...
  password: ...
response_variable: device

Debug logs

HasTokenForKey
Checking if token exists in token storage file
Token storage key: "SpotifyWebPlayerCookieCredentials/Shared/<redacted>"
Token storage file path: "/config/.storage/spotifyplus_tokens.json"
Token was not found in token storage file for key: "SpotifyWebPlayerCookieCredentials/Shared/<redacted>"
HasTokenForKey
Spotify Web Player cookie credentials are no longer supported by Spotify as of 2025/05/12!
Spotify Connect LoginId "<redacted>" HasSpotifyWebPlayerCredentials flag: False
SpotifyClient is starting Spotify Connect Directory task
Spotify Connect Directory Task - Starting thread RUN / TASK method
Spotify Connect Directory Task - Thread information

Diagnostics dump

No response

About this issue

  • Original URL
  • State: open
  • Created a year ago
  • Comments: 24 (11 by maintainers)

Most upvoted comments

It could be the enabled SI Trace as well, if it’s still enabled. That will definitely slow things down, as it is logging all of the results to the trace file.

You can disable tracing by setting Enabled = False in the SmartInspect.cfg file.

That did the trick, thanks!

The extended time occurs due to shuffle detection. If you are not concerned about shuffling, then remove the shuffle argument from the service call.

Many users were complaining about the shuffle behavior (using Spotify Web API) not behaving the same way as the Spotify Web player (using Spotify Embedded Client). It’s because the Spotify Web API does not handle shuffling the same was as the Embedded Client. The v1.0.41 fixes that by first querying the playlist / album items (first 50) and choosing a random track to start with. So it takes a little bit longer to retrieve that context list. It should not be taking 10 seconds to retrieve it though. I will look into that. I know the Spotify Web API was very sluggish to respond over the last couple of days, so not sure if it’s a temporary response time thing.

How many items were in the playlist that you were trying to start?

I was not trying to play a playlist. I retrieve last item of a podcast and play that. No reference to shuffle in my code.

Tried SpotifyPlus 1.41, behaves differently: starting a playlist after first logging in with Spotify Desktop or Android app was immediately in 1.39, takes several (up to 10) seconds in 1.41.

@Ayuus I had a chance to take a quick look at this today, and noticed the the Spotify Connect zeroconf addUser request from SpotifyPlus was missing a couple of parameters (compared to the Spotify App using the Wireshark trace):

"deviceName" = "MS-SURFACE-8"
"deviceId" = "b65c4 ..."

I added some code to add these parameters to the addUser request. I don’t think it will fix the issue, but it might.

I was making some other changes for a shuffle play bug, and went ahead and added this to give it a try. I just released SpotifyPlus Integration v1.0.141 for the above.

It appears that Bluesound changed the way they are authenticating the device to Spotify, as of the latest Bluesound update. This is in support of a Spotify mandate that is forcing manufacturers to update their firmware prior to November 2025, which is when they (Spotify) are going to deprecate / disable older authentication methods.

I may not be able to fix this, as the addUser blob is encrypted and I can only guess what is in there. From the looks of the Wireshark trace, it appears that it is some sort of token value instead of the usual encrypted blob value. Again, just a guess.

Anyway, give it a try and see what happens. Generate another SI Trace file if you would, and email it to me. No need to send another Wireshark.

Thanks!

Sent log to you by e-mail. If you want more testing from my side, please let me know.

@Ayuus Questions:

  1. are you only using 1 Spotify account with the Bluesound device? I’m talking about when you use it from the Spotify Apps. Or are you using multiple Spotify accounts with it? Trying to see if any account switching is taking place.
  2. did this processing work before the update to the Bluesound device? If so, how long has it been working for you prior to these latest issues? In your initial post, you mentioned “ After updating my Bluesound player, HA and Spotifyplus, SpotifyPlus can no longer connect to my Bluesound device via zeroconf_device_connect.”. Just wondering if Bluesound changed something in their authentication process, or if something in the HA update is causing the issue.
  1. Yes, only 1 account
  2. That could very well be possible. Unfortunately, I did not test between the updates.

OK, will try Spotify Desktop app. For now everything works, when it no longer does, I will send you getInfo results. I sent you a message via HA Community, but I did not find a way to send you a logfile.

Checked communication with WireShark.Desktop app is able to login, after that, SpotifyPlus is able to login, too, but only for a few hours (do not know how long).

I have WireShark trace available for you.

Edit: actually SpotifyPlus is able to login for an hour or so after Spotify Desktop. Please note I do have spotify_tokens.json in folder homeassistant/.storage.

@Ayuus You mentioned that the getInfo call still works …

Can you share the results of the getInfo call? Just redact the public key value (if one exists) in your reply. The tokenType value (along with others) might provide some clues.

{
	"status": 101,
	"statusString": "OK",
	"spotifyError": 0,
	"version": "2.9.0",
	"deviceID": "99bd6e64ed57f44a784910d017092e4bada775b5",
	"publicKey": "<REDACTED>",
	"remoteName": "Bluesound Powernode 330",
	"brandDisplayName": "Bluesound",
	"modelDisplayName": "POWERNODE",
	"libraryVersion": "3.205.187-g0b65d3e0",
	"resolverVersion": 0,
	"groupStatus": "NONE",
	"tokenType": "accesstoken",
	"clientID": "3d1292a4f7bc4cbc853faa331d07348a",
	"productID": 101,
	"scope": "streaming",
	"availability": "",
	"deviceType": "AVR",
	"alias_count": 0
}

@Ayuus I did not see any notifications from HA Community Forums about a message to me. My username is thlucas, and here’s the SpotifyPlus forum thread: https://community.home-assistant.io/t/spotifyplus-integration/698651

Tried again, could you check?