[Solved] Trouble following the Device configuration Options

[ovizii]

I isntalled your itnegration and rebooted HA. I then followed these instructions: https://github.com/thlucas1/homeassistantcomponent_spotifyplus/wiki/Device-Configuration-Options

Not sure where I might have made a msitake but after configuring the "Integration Options" I see a notification that SpotifyPlus was discovered?

So I click on configure, get sent here:

I agree and link my account again. Then I now see two SpotifyPlus services !?

I then deleted the second one but it gets discovered again :-(

If I delete the first one it looks like this:

I now decided to restart HA. Now I only see one service and everything seems fine.

[ovizii]

OK, I spoke too soon. I tried playing something with this media player and am getting this error:

Failed to perform the action media_player/play_media. Could not find librespot authorization credentials file (/config/.storage/SpotifyWebApiPython_librespot_credentials.json). This file is required in order to authenticate to a device or service that utilizes the librespot application.

And yet, the credentials are there and with the same name as shown in the configured service:

I then found this similar issue here: #45
So I might add more details, maybe somebody can help me figure it out.

On my HA instance I have installed the SpotifyPlus integration as you can read in this thread as well as the Spotify Connect (unofficial) add-on from here: https://github.com/giannello/addon-spotify-connect

SpotifyPlus is giving the above error when trying to play music via the media browser. HOWEVER, if I open spotify on my android phone, I can perfectly well connect to Spotify Connect (unofficial) on my HA instance and the mini media player card shows it as playing:

I can even control playback, skip, control volume, transfer playback to my phone but as soon as I try transferring playback back to my HA instance with the Spotify Connect (unofficial) add-on I get this error mentioned above. I manually checked via SSH and /config/.storage does not even contain any Spotify related folders.

[thlucas1]

The credentials that the error message is referring to are not your OAuth credentials, but rather your librespot credentials. The Spotify Connect add-on utilizes the librespot library under the covers to control the Spotify Player.

You will want to check out the librespot and spotifyd device support wiki document.

Note that I have not verified if this will work with the Spotify Connect add-on. I would think it would be able to, if it utilizes librespot, but not sure.

[ovizii]

Thanks for the pointer. I found this thread for the Spottify Conect add-on: hassio-addons/addon-spotify-connect#267 stating that
Spotify disabled the use of username/password access which librespot uses as an authentication method to for the API.

The Spottify Connect add-on also works without supplying the Spotify credentials.
Weirdly enough ,the plain Spotify Integration never had any issues with it.

But then I read your statement here: https://github.com/thlucas1/homeassistantcomponent_spotifyplus/wiki/Device-Configuration-Options#librespot-and-spotifyd-device-support

The integration does not support librespot applications that utilize the non-discovery mode of librespot.

Thansk for providing this itnegration and all your help here. I will keep an eye on the issue about the Spotify Connect add-on, I assume if that oen gets solved, this integration will also start workign for me.

[thlucas1]

You should be able to use the SpotifyPlus integration to control the player after starting play using the Spotify Mobile / Desktop app. Can you verify that?

The problem remains of how to initiate playback via HA SpotifyPlus without first starting it on the Spotify Mobile App. To overcome that, the SpotifyPlus integration needs a librespot credentials.json file. Once we figure that out, you should be able to add it to the SpotifyPlus cache and everything should work directly from HA.

The Spotify Connect add-on looks like it utilizes the spotifyd service to control the player, but it (Spotify Connect addon) does not allow you to configure the spotifyd service directly; e.g. there is no way to get to the credentials.json file, if one is even being generated.

I did find this link on GitHub that allows you to generate the credentials.json file. I think if we can get that to work, you should just be able to copy the credentials.json file to the SpotifyPlus cache location (e.g. /config/.storage/SpotifyWebApiPython_librespot_credentials.json) and it should start working.

Let me do some research on how to execute the librespot-auth process, and I will get back to you.

[thlucas1]

I normally do not use the "Discovered" way to configure the service; with that said, it should have worked the same way whether configuring via "Discovered" or via "Add Service". I can't really tell from your screen captures since you blurred the names, but the fact that it says 1 service and 1 entity means you should be good. I would chalk that one up to an HA browser caching issue. To be safe, I would restart HA, clear your browser cache, and view the SpotifyPlus integration configuration again.

You also want to verify that it created OAuth credentials for the SpotifyPlus integration. It will look something like this (I have both Premium and Free app credentials created):

[ovizii]

My apologies for starting a discussion instead of an issue :-( Should I open a new one?

Meanwhile, let me add the info you would need for an issue. I will supply the debug logs in a minute, need to ernable, gather and submit them ehre.

`## System Information

version	core-2024.10.0
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.12.4
os_name	Linux
os_version	6.6.31-haos-raspi
arch	aarch64
timezone	Europe/Berlin
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.1
Stage	running
Available Repositories	1428
Downloaded Repositories	14

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 13.1
update_channel	stable
supervisor_version	supervisor-2024.09.1
agent_version	1.6.0
docker_version	26.1.4
disk_total	116.5 GB
disk_used	14.5 GB
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	rpi5-64
supervisor_api	ok
version_api	ok
installed_addons	Mosquitto broker (6.4.1), Advanced SSH & Web Terminal (19.0.0), Zigbee2MQTT (1.40.2-1), Samba Backup (5.2.0), Tailscale (0.22.1), Nginx Proxy Manager (1.0.1), Studio Code Server (5.16.3), Spotify Connect (unofficial) (0.10.0-giannello), MPD (1.7.3), Assist Microphone (1.2.0), openWakeWord (1.10.0), Whisper (2.1.2), Piper (1.5.2)

Dashboards

dashboards	2
resources	17
views	3
mode	storage

Recorder

oldest_recorder_run	3 September 2024 at 04:46
current_recorder_run	3 October 2024 at 15:24
estimated_db_size	151.56 MiB
database_engine	sqlite
database_version	3.45.3

Spotify

api_endpoint_reachable	ok

SpotifyPlus

integration_version	v1.0.59
clients_configured	1: ovi (premium)
api_endpoint_reachable	ok

`

[ovizii]

I would like to give you logs but after I enabled debug logging, restarted HA, triggered the problem and downloaded the full logs, the ZIP file is 67MB should I really attach that here?

Btw. I can't figure out how/where to fidn the diagnostics you are asking for this integration, woudl you mind giving me a hint? This page didn't help: https://www.home-assistant.io/integrations/diagnostics/

[thlucas1]

@ovizii Thanks for your patience while I sort thru this issue. You are the first user to utilize the Spotify Connect AddOn. I have Spotify Connect AddOn installed, but I run it in "dummy mode" since I don't have a soundcard on my VM.

I put together some documentation on how to enable Spotify Connect devices with SpotifyPlus.

In summary, it utilizes the librespot-auth application to generate a librespot credentials.json file, which is then copied to the Home Assistant storage folder so that it can be accessed by SpotifyPlus. This will give you the ability to initiate the Spotify player with Home Assistant, versus relying on the Spotify App to initiate play.

It may sound a little complicated, but give the docs a read and let me know how it goes. I was able to follow the steps and create the credentials file - the hardest part was building the librespot-auth application (but I'm a Windows guy, so if you're used to Linux you should be ok).

[ovizii]

Thanks for doing all this research. It is much appreciated. Unfortunately I failed to succeed. I might try again some time soon but wanted to leave some feedback here in case anyone else faces the same issues.

I'm on Debian Bookworm and running cargo build --release I realized that the Debian rustc packages are too old for this project. so I had to install via the rustup install script after removeing the Debian rustc and cargo version.

error: package `clap v4.5.13` cannot be built because it requires rustc 1.74 or newer, while the currently active rustc version is 1.63.0
Either upgrade to rustc 1.74 or newer, or use
cargo update -p clap@4.5.13 --precise ver
where `ver` is the latest version of `clap` supporting rustc 1.63.0

Manually installing rustc: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

I then tried again with: ./target/release/librespot-auth --name "Librespot-Auth" --class=computer

and got this error:

 ./target/release/librespot-auth --name "Librespot-Auth" --class=computer
thread 'main' panicked at src/main.rs:59:10:
called `Result::unwrap()` on an `Err` value: Error { kind: Unknown, error: Os { code: 105, kind: Uncategorized, message: "No buffer space available" } }

I tried downloadign the precompiled binary from https://github.com/dspearson/librespot-auth but got the same error.

[thlucas1]

I am on Windows 11 WSL Debian:

cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian

rustup version information:

rustup --version
rustup 1.27.1 (54dd3d00f 2024-04-24)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.81.0 (eeb90cda1 2024-09-04)`

Per the source, it looks like the error occurred during the zeroconf discovery process.

    let mut server = Discovery::builder(device_id.clone(), SessionConfig::default().client_id)
        .name(name.clone())
        .device_type(device_type)
        .launch()
        .unwrap();

It sounds like something ran out of buffer space? A quick Google search revealed a similar problem and solution.

The solution in the article linked above was to increase various buffer size/multicast connection in /etc/sysctl.conf. I would make a backup of that config first, then maybe try tweaking various buffer sizes. I looked in my sysctl.conf, but everything was commented out.

# Bigger buffers (to make 40Gb more practical). These are maximums, but the default is unaffected.
net.core.wmem_max=268435456
net.core.rmem_max=268435456
net.core.netdev_max_backlog=10000

# Avoids problems with multicast traffic arriving on non-default interfaces
net.ipv4.conf.default.rp_filter=0
net.ipv4.conf.all.rp_filter=0

# Force IGMP v2 (required by CBF switch)
net.ipv4.conf.all.force_igmp_version=2
net.ipv4.conf.default.force_igmp_version=2

# Increase the ARP cache table
net.ipv4.neigh.default.gc_thresh3=4096
net.ipv4.neigh.default.gc_thresh2=2048
net.ipv4.neigh.default.gc_thresh1=1024

# Increase number of multicast groups permitted
net.ipv4.igmp_max_memberships=1024

Hope it helps!

[ovizii]

Thanks. Giving it a try right now.

cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

 rustup --version
rustup 1.27.1 (54dd3d00f 2024-04-24)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.81.0 (eeb90cda1 2024-09-04)`

in my /etc/sysctl.conf everything is commented out except these two lines I needed for tailscale:

## added for tailscale forwarding
net.ipv4.ip_forward=1
net.ipv6.conf.all.forwarding=1

adding this line to it:

###added for librespot-auth compiling
# Increase number of multicast groups permitted
net.ipv4.igmp_max_memberships=1024

and activating the changes with sysctl -p

BUT it turns out you have to have the device where you are doing this on the same network as an instance of spotify :-/
Will have to start from scratch on another device on the same network but it should work. I will update my thread here after doign that.

[ovizii]

I am busy installing wsl and retrying on anotehr laptop. I am wondering about this command:

./target/release/librespot-auth --name "Librespot-Auth" --class=computer

Will Librespot-Auth be the new name of the device created by Spotify Connect add-on? Seeing that the add-on already creates a device with a specific name so I can't use the same one. Or shall I turn off the add-on, then use this command with the same name?

[thlucas1]

You can use any value you want there, as long as it’s unique and does not contain spaces. I chose “Librespot-auth”, the authors original choice was “Second Laptop”. It is just the value that shows up in the device list of the Spotify desktop app.

you don’t need to change any values in your Spotify Connect Addon configuration. My Spotify Connect Addon name is “HAVM-SpotifyConnect”. I think I read somewhere that you don’t want to use device names with spaces in them.

For some reason for me, the Spotify Mobile App would not find the “Librespot-auth” device. I had to use the Spotify desktop app from my main Windows 11 image.

[thlucas1]

Also note that this whole process is a one time thing to generate a Librespot credentials.json file. Once you have the credentials.json file, you don’t need to run Librespot-auth again (unless your Spotify password changes).

[ovizii]

Thanks, I figured out, since its a one-time use, the selected name doesn't matter as it will not be saved with those credentials :-)
I get it now, the credentials will be saved in the .json file upon first connect and nothing else.

I have now copied the credentials file to where it belongs, restarted HA and tested. It seems I can now fulyl control spotify with teh Spotify Plus integration, switch to different sources, play, stop, skip, etc.

Now let see if I can set up autoamtions to wake up to music and stop playing music after a certain time when goign to bed.

I really appreciate all the help you have given me and making this awesome integration.

Btw. Thanks for the tip to use the windows spotify app. I was going nuts trying to use the mobile app, despite being on the same network as the edevice I was running librespot-auth on.

[thlucas1]

Awesome! I will update my wiki docs to reflect our findings as well.

Apologies for taking so long - not many people are using the integration with Spotify Connect AddOn, and I have never been able to really test it using the "dummy mode" of the output. Combine that with all of the authentication changes made by Spotify since August, and it's been a real "treat" figuring it out!

Also, I appreciate the "Buy Me a Coffee" slice.

Let me know if you have anymore issues with SpotifyPlus.

Also, I am gearing up to release a SpotifyPlus-Card within the next few weeks (hopefully). It will offer a media player interface, Spotify favorites (add / remove / list), as well as the ability to search Spotify real-time. If you would be interested in beta testing it let me know.

[ovizii]

Sure thing, sign me up for the beta please :-)

[thlucas1]

@ovizii
I put together a SpotifyPlus Card UI Beta Test announcement, if you're still interested in beta testing the new SpotifyPlus user-interface for Home Assistant? Just reply to the discussion link if you are, and feel free to download the card and give it a whirl.

Thanks - Todd

[ovizii]

Thanks for the heads-up. I will give it a test run :-)