[GH-ISSUE #131] Initial volume not working as soon as I configure volume_steps #79

Closed
opened 2026-02-28 14:25:11 +03:00 by kerem · 3 comments
Owner

Originally created by @l3d00m on GitHub (Oct 23, 2024).
Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/131

I am using the following config on my raspberry 3 on go-librespot version 0.1:

device_name: Küche
device_id: XXX
device_type: speaker
credentials:
  type: zeroconf
initial_volume: 60

Initial volume works as expected. As soon as I added the following line tho:

volume_steps: 20

Initial volume stops working, it's always set to 100%.

Maybe related to #32?

Logs, while it's not working:

INFO[0000] running go-librespot v0.1.0
DEBU[0000] no app state found
DEBU[0000] stored credentials not found
DEBU[0000] fetched new accesspoints: [ap-gew4.spotify.com:4070 ap-gew4.spotify.com:443 ap-gew4.spotify.com:80 ap-gue1.spotify.com:4070 ap-gew1.spotify.com:443 ap-gae2.spotify.com:80]
DEBU[0000] fetched new dealers: [gew4-dealer.spotify.com:443 gue1-dealer.spotify.com:443 gew1-dealer.spotify.com:443 gae2-dealer.spotify.com:443]
DEBU[0000] fetched new spclients: [gew4-spclient.spotify.com:443 gue1-spclient.spotify.com:443 gew1-spclient.spotify.com:443 gae2-spclient.spotify.com:443]
INFO[0000] zeroconf server listening on port 43517
DEBU[0011] obtained new client token: WHOOPS
DEBU[0011] connected to ap-gew4.spotify.com:4070
DEBU[0011] completed keyexchange
DEBU[0012] completed challenge
INFO[0012] authenticated AP as USERNAME
INFO[0012] authenticated Login5 as USERNAME
INFO[0012] accepted zeroconf user USERNAME from Unicorn
DEBU[0012] dealer connection opened
DEBU[0012] skipping packet PacketTypeSecretBlock, len: 336
DEBU[0012] skipping packet PacketTypeLicenseVersion, len: 2
DEBU[0012] skipping packet PacketTypeUnknown1f, len: 17
DEBU[0012] skipping packet PacketTypeLegacyWelcome, len: 0
DEBU[0012] skipping packet PacketTypeMercuryEvent, len: 493
DEBU[0012] autoplay enabled: false
DEBU[0012] received connection id: WHOOPS
DEBU[0012] put connect state because NEW_DEVICE
DEBU[0012] handling transfer player command from 4aa2bc2e26796d1e0cd4ee2baa014e891d336939
DEBU[0012] resolved context of track                     uri="spotify:playlist:37i9dQZF1DWTC99MCpbjP8"
DEBU[0012] loading track (paused: true, position: 6915ms)  uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9"
DEBU[0012] put connect state because PLAYER_STATE_CHANGED
DEBU[0012] selected format OGG_VORBIS_160 (50cc1f13273ecd52410ea869bdeba6ab9b923b0f)  uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9"
DEBU[0012] requested aes key for file 50cc1f13273ecd52410ea869bdeba6ab9b923b0f, gid: 5Si7lQfzTcOs55xiXgBxS9
DEBU[0013] fetched first chunk of 5, total size is 2503852 bytes  uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9"
DEBU[0013] created new output device
INFO[0013] loaded track "Fireside" (paused: true, position: 6915ms, duration: 133066ms, prefetched: false)  uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9"
DEBU[0013] put connect state because PLAYER_STATE_CHANGED
DEBU[0013] sending successful reply for dealer request
DEBU[0013] fetched chunk 2/4, size: 524288               uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9"
DEBU[0013] put connect state because PLAYER_STATE_CHANGED
DEBU[0013] fetched chunk 3/4, size: 524288               uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9"
DEBU[0013] fetched chunk 1/4, size: 524288               uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9
Originally created by @l3d00m on GitHub (Oct 23, 2024). Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/131 I am using the following config on my raspberry 3 on go-librespot version 0.1: ```yml device_name: Küche device_id: XXX device_type: speaker credentials: type: zeroconf initial_volume: 60 ``` Initial volume works as expected. As soon as I added the following line tho: ``` volume_steps: 20 ``` Initial volume stops working, it's always set to 100%. Maybe related to #32? Logs, while it's not working: ``` INFO[0000] running go-librespot v0.1.0 DEBU[0000] no app state found DEBU[0000] stored credentials not found DEBU[0000] fetched new accesspoints: [ap-gew4.spotify.com:4070 ap-gew4.spotify.com:443 ap-gew4.spotify.com:80 ap-gue1.spotify.com:4070 ap-gew1.spotify.com:443 ap-gae2.spotify.com:80] DEBU[0000] fetched new dealers: [gew4-dealer.spotify.com:443 gue1-dealer.spotify.com:443 gew1-dealer.spotify.com:443 gae2-dealer.spotify.com:443] DEBU[0000] fetched new spclients: [gew4-spclient.spotify.com:443 gue1-spclient.spotify.com:443 gew1-spclient.spotify.com:443 gae2-spclient.spotify.com:443] INFO[0000] zeroconf server listening on port 43517 DEBU[0011] obtained new client token: WHOOPS DEBU[0011] connected to ap-gew4.spotify.com:4070 DEBU[0011] completed keyexchange DEBU[0012] completed challenge INFO[0012] authenticated AP as USERNAME INFO[0012] authenticated Login5 as USERNAME INFO[0012] accepted zeroconf user USERNAME from Unicorn DEBU[0012] dealer connection opened DEBU[0012] skipping packet PacketTypeSecretBlock, len: 336 DEBU[0012] skipping packet PacketTypeLicenseVersion, len: 2 DEBU[0012] skipping packet PacketTypeUnknown1f, len: 17 DEBU[0012] skipping packet PacketTypeLegacyWelcome, len: 0 DEBU[0012] skipping packet PacketTypeMercuryEvent, len: 493 DEBU[0012] autoplay enabled: false DEBU[0012] received connection id: WHOOPS DEBU[0012] put connect state because NEW_DEVICE DEBU[0012] handling transfer player command from 4aa2bc2e26796d1e0cd4ee2baa014e891d336939 DEBU[0012] resolved context of track uri="spotify:playlist:37i9dQZF1DWTC99MCpbjP8" DEBU[0012] loading track (paused: true, position: 6915ms) uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9" DEBU[0012] put connect state because PLAYER_STATE_CHANGED DEBU[0012] selected format OGG_VORBIS_160 (50cc1f13273ecd52410ea869bdeba6ab9b923b0f) uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9" DEBU[0012] requested aes key for file 50cc1f13273ecd52410ea869bdeba6ab9b923b0f, gid: 5Si7lQfzTcOs55xiXgBxS9 DEBU[0013] fetched first chunk of 5, total size is 2503852 bytes uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9" DEBU[0013] created new output device INFO[0013] loaded track "Fireside" (paused: true, position: 6915ms, duration: 133066ms, prefetched: false) uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9" DEBU[0013] put connect state because PLAYER_STATE_CHANGED DEBU[0013] sending successful reply for dealer request DEBU[0013] fetched chunk 2/4, size: 524288 uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9" DEBU[0013] put connect state because PLAYER_STATE_CHANGED DEBU[0013] fetched chunk 3/4, size: 524288 uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9" DEBU[0013] fetched chunk 1/4, size: 524288 uri="spotify:track:5Si7lQfzTcOs55xiXgBxS9 ```
kerem closed this issue 2026-02-28 14:25:11 +03:00
Author
Owner

@l3d00m commented on GitHub (Oct 23, 2024):

Offtopic: is the client_token or the connection id sensitive? if so, could we not log it?

<!-- gh-comment-id:2432632377 --> @l3d00m commented on GitHub (Oct 23, 2024): Offtopic: is the client_token or the connection id sensitive? if so, could we not log it?
Author
Owner

@devgianlu commented on GitHub (Oct 24, 2024):

Initial volume stops working, it's always set to 100%.

The initial volume is espressed in steps. If you reduce the steps to 20 and set initial volume to 60 steps then you'll get 100%.

Offtopic: is the client_token or the connection id sensitive? if so, could we not log it?

None of them are sensibile, I think.

<!-- gh-comment-id:2435933053 --> @devgianlu commented on GitHub (Oct 24, 2024): > Initial volume stops working, it's always set to 100%. The initial volume is espressed in steps. If you reduce the steps to 20 and set initial volume to 60 steps then you'll get 100%. > Offtopic: is the client_token or the connection id sensitive? if so, could we not log it? None of them are sensibile, I think.
Author
Owner

@l3d00m commented on GitHub (Oct 25, 2024):

Whoops, sorry, I misunderstood that. It now works perfectly. I had assumed it would be percentage.

<!-- gh-comment-id:2437695228 --> @l3d00m commented on GitHub (Oct 25, 2024): Whoops, sorry, I misunderstood that. It now works perfectly. I had assumed it would be percentage.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/go-librespot#79
No description provided.