System Health details
System Information
| version |
core-2025.2.4 |
| installation_type |
Home Assistant OS |
| dev |
false |
| hassio |
true |
| docker |
true |
| user |
root |
| virtualenv |
false |
| python_version |
3.13.1 |
| os_name |
Linux |
| os_version |
6.6.73-haos |
| arch |
aarch64 |
| timezone |
America/New_York |
| config_dir |
/config |
Home Assistant Community Store
| GitHub API |
ok |
| GitHub Content |
ok |
| GitHub Web |
ok |
| GitHub API Calls Remaining |
4554 |
| Installed Version |
1.34.0 |
| Stage |
running |
| Available Repositories |
1533 |
| Downloaded Repositories |
42 |
Home Assistant Cloud
| logged_in |
true |
| subscription_expiration |
December 29, 2025 at 7:00 PM |
| relayer_connected |
true |
| relayer_region |
us-east-1 |
| remote_enabled |
true |
| remote_connected |
true |
| alexa_enabled |
true |
| google_enabled |
true |
| cloud_ice_servers_enabled |
true |
| remote_server |
us-east-1-10.ui.nabu.casa |
| certificate_status |
ready |
| instance_id |
fe429148320d4237973c17af35426da8 |
| can_reach_cert_server |
ok |
| can_reach_cloud_auth |
ok |
| can_reach_cloud |
ok |
Home Assistant Supervisor
| host_os |
Home Assistant OS 14.2 |
| update_channel |
stable |
| supervisor_version |
supervisor-2025.02.1 |
| agent_version |
1.6.0 |
| docker_version |
27.2.0 |
| disk_total |
28.0 GB |
| disk_used |
13.4 GB |
| healthy |
true |
| supported |
true |
| host_connectivity |
true |
| supervisor_connectivity |
true |
| ntp_synchronized |
true |
| virtualization |
|
| board |
green |
| supervisor_api |
ok |
| version_api |
ok |
| installed_addons |
Node-RED (18.1.1), Mosquitto broker (6.4.1), Advanced SSH & Web Terminal (19.0.0), File editor (5.8.0), AdGuard Home (5.2.3), Samba share (12.4.0), ESPHome Device Builder (2024.12.4), openWakeWord (1.10.0), Home Assistant Google Drive Backup (0.112.1), Music Assistant Server (2.3.6) |
Dashboards
| dashboards |
3 |
| resources |
38 |
| views |
12 |
| mode |
storage |
Network Configuration
| adapters |
lo (disabled), end0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth72d837f (disabled), veth5c3d31b (disabled), veth5e2cabe (disabled), veth90f9269 (disabled), veth90214ea (disabled), veth8f31982 (disabled), veth7c013a8 (disabled), veth1e7c382 (disabled), veth0ff31c2 (disabled), vethfab0114 (disabled) |
| ipv4_addresses |
lo (127.0.0.1/8), end0 (192.168.0.140/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth72d837f (), veth5c3d31b (), veth5e2cabe (), veth90f9269 (), veth90214ea (), veth8f31982 (), veth7c013a8 (), veth1e7c382 (), veth0ff31c2 (), vethfab0114 () |
| ipv6_addresses |
lo (::1/128), end0 (fe80::8b36:76c2:97f7:26b7/64), docker0 (fe80::42:aeff:fe79:32ce/64), hassio (fe80::42:67ff:fede:e476/64), veth72d837f (fe80::d0d4:57ff:fe11:8dca/64), veth5c3d31b (fe80::cce0:3dff:fe0c:c156/64), veth5e2cabe (fe80::cce8:bcff:fe88:6522/64), veth90f9269 (fe80::b4f6:24ff:fec1:993d/64), veth90214ea (fe80::d4fa:55ff:feca:79be/64), veth8f31982 (fe80::f8bb:3cff:fec5:d91/64), veth7c013a8 (fe80::c0ae:a1ff:fe70:4bdd/64), veth1e7c382 (fe80::bc1e:a4ff:fe7e:7c34/64), veth0ff31c2 (fe80::7c4d:fdff:feac:8ce5/64), vethfab0114 (fe80::549c:f1ff:fe48:68ec/64) |
| announce_addresses |
192.168.0.140, fe80::8b36:76c2:97f7:26b7 |
Recorder
| oldest_recorder_run |
February 4, 2025 at 6:58 PM |
| current_recorder_run |
February 15, 2025 at 10:35 AM |
| estimated_db_size |
283.41 MiB |
| database_engine |
sqlite |
| database_version |
3.47.1 |
Spotify
| api_endpoint_reachable |
ok |
SpotifyPlus
| error |
failed to load: unknown |
Checklist
Describe the issue
Getting the following error messages:
Failed Setup, will retry: SpotifyApiError: Authorization token must be set and a user profile established before starting the Spotify Connect Directory Task
Per Spotify Web API, there are currently no Spotify Connect devices active. Please close the configuration options, play a track on any Spotify Connect player for a minute or two, and then open the configuration options again
I tired playing music on all of my devices through Spotify for at least a full song on all of them. Tired restarting HA. Error will not go away. Tried readding the services. Was working just before I updated HA
Reproduction steps
- go to spotifyplus integration
- both accounts are failing to setup

Debug logs
N/A private info in logs
Diagnostics dump
No response
@thlucas1 Amazing! Thanks a lot for this integration, it is the one I used the most on my dashboard now, and thanks to all the available customization, it’s matching all my needs 😃 (I am a heavy Spotify user on MANY Google mini devices)
Now on version 1.0.102 that was just submitted. I moved the credential keys to the UI, as per your recommendation.
@Peskinator
FYI - just released a new version of the SpotifyPlus integration
The big takeaway with this release the the ability to set the Spotify Web Player Credentials in UI configuration options, instead of in the Token Cache File.
Be sure to check out the SpotifyPlus Card Dashboard as well.
[ 1.0.101 ] - 2025/03/08
spotifyplus_tokens.jsonToken Cache File. The configuration options take precedence if the credentials are found in both places. If you have these options configured in the Token Cache File, it is suggested that you move them to the UI configuration, as the Token Cache File support will be removed in a future release.spotifywebapipythonpackage requirement to version 1.0.187.I’m sorry that I missed to use SmartInspect to trace it.
I used the same Dev App for NodeRED authentication. You could be right with your assumption.
I think I see what’s going on … it appears the authentication token could not be refreshed, but the exception details are probably omitted from the HA log since it’s failing at the spotifywebapiPython package level. I would need a SmartInspect trace to get the underlying reason for the exception. I will need to add some code to pass the underlying exception reason back up the call chain so that it is logged with the exception in the HA log.
I’m just glad you are back up and running. Thanks for your patience, and for not giving up.
I’m wondering if the root cause is that both Spotify and SpotifyPlus share the same Spotify Developer App id maybe? I didn’t think that would make a difference, but maybe it does?
I managed to repair SpotifyPlus. It was necessary to create a new app (new clientID!) in the Spotify dev environment.
Thanks @thlucas1 I tried your suggestion with the same outcome, unfortunately. This week end I’ll do it again and will document/screenshots of each steps, so I can provide you with more info than just “I tried and it didn’t work”.