starred/librespot
1
0
Fork 0
mirror of https://github.com/librespot-org/librespot.git synced 2026-04-27 08:15:50 +03:00
Code Issues 95 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #1551] session_disconnect event fails to fire with librespot 0.7.0 #702

New issue
Closed
opened 2026-02-27 19:32:02 +03:00 by kerem · 8 comments
kerem commented 2026-02-27 19:32:02 +03:00
Owner
Copy link

Originally created by @samcook on GitHub (Aug 24, 2025).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1551

Description

Thanks for the quick turnaround on #1547 / #1548.

I built a version of librespot from the current head of the dev branch (d073cb1), and the session_connected event is now firing when I establish a Spotify Connect session from my phone, but session_disconnected still fails to fire, and librespot continues to play music until the end of the track.

Version

librespot 0.7.0 d073cb1 (Built on 2025-08-24, Build ID: 2TzDyiBU, Profile: release)

How to reproduce

  1. Launch librespot with an event handler script configured.
  2. Connect with Spotify Connect.
  3. session_connected event fires, executing script which logs the event and turns on AV receiver. 🎉
  4. Disconnect Spotify Connect.
  5. Expect session_disconnected event to fire, executing script which logs the event and turns off AV receiver.

Log

Non-verbose log here. "Event fired" logs are output by my event handler script. Please let me know if you want a verbose log.

Aug 25 11:11:27 raspberrypi systemd[1]: Started Raspotify (Spotify Connect Client).

<establish Spotify Connect session from phone>

Aug 25 11:11:52 raspberrypi librespot[1152]: [2025-08-24T23:11:52Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 25 11:11:52 raspberrypi librespot[1164]: Event session_connected fired
Aug 25 11:11:52 raspberrypi librespot[1164]: Published session_connected to raspotify/event
Aug 25 11:11:52 raspberrypi librespot[1167]: Event session_client_changed fired
Aug 25 11:11:52 raspberrypi librespot[1168]: Event volume_changed fired
Aug 25 11:11:52 raspberrypi librespot[1169]: Event auto_play_changed fired
Aug 25 11:11:52 raspberrypi librespot[1170]: Event filter_explicit_content_changed fired
Aug 25 11:11:52 raspberrypi librespot[1171]: Event shuffle_changed fired
Aug 25 11:11:52 raspberrypi librespot[1172]: Event repeat_changed fired
Aug 25 11:11:52 raspberrypi librespot[1173]: Event play_request_id_changed fired
Aug 25 11:11:52 raspberrypi librespot[1174]: Event loading fired
Aug 25 11:11:54 raspberrypi librespot[1175]: Event track_changed fired
Aug 25 11:11:54 raspberrypi librespot[1152]: Failed to create secure directory (/root/.config/pulse): Permission denied
Aug 25 11:11:54 raspberrypi librespot[1176]: Event playing fired
Aug 25 11:11:54 raspberrypi librespot[1176]: Published playing to raspotify/event

<disconnect Spotify Connect session from phone>

Aug 25 11:12:10 raspberrypi librespot[1152]: [2025-08-24T23:12:10Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 25 11:12:10 raspberrypi librespot[1152]: [2025-08-24T23:12:10Z ERROR librespot_connect::spirc] could not dispatch connect state update: Client specified an invalid argument { Response status code: 411 Length Required }
Aug 25 11:13:48 raspberrypi librespot[1226]: Event preload_next fired
Aug 25 11:14:18 raspberrypi librespot[1152]: [2025-08-24T23:14:18Z WARN  librespot_connect::spirc] failed filling up next_track during stopping: Invalid state { context is not available. type: Default }
Aug 25 11:14:18 raspberrypi librespot[1241]: Event end_of_track fired
Aug 25 11:14:19 raspberrypi librespot[1243]: Event stopped fired
Aug 25 11:14:19 raspberrypi librespot[1243]: Published stopped to raspotify/event

Host (what you are running librespot on):

  • OS: Linux
  • Platform: Raspberry Pi 4
Originally created by @samcook on GitHub (Aug 24, 2025). Original GitHub issue: https://github.com/librespot-org/librespot/issues/1551 ### Description Thanks for the quick turnaround on #1547 / #1548. I built a version of librespot from the current head of the `dev` branch (d073cb1), and the `session_connected` event is now firing when I establish a Spotify Connect session from my phone, but `session_disconnected` still fails to fire, and librespot continues to play music until the end of the track. ### Version librespot 0.7.0 d073cb1 (Built on 2025-08-24, Build ID: 2TzDyiBU, Profile: release) ### How to reproduce 1. Launch `librespot` with an event handler script configured. 2. Connect with Spotify Connect. 3. `session_connected` event fires, executing script which logs the event and turns on AV receiver. 🎉 4. Disconnect Spotify Connect. 5. Expect `session_disconnected` event to fire, executing script which logs the event and turns off AV receiver. ### Log Non-verbose log here. "Event fired" logs are output by my event handler script. Please let me know if you want a verbose log. ``` Aug 25 11:11:27 raspberrypi systemd[1]: Started Raspotify (Spotify Connect Client). <establish Spotify Connect session from phone> Aug 25 11:11:52 raspberrypi librespot[1152]: [2025-08-24T23:11:52Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 25 11:11:52 raspberrypi librespot[1164]: Event session_connected fired Aug 25 11:11:52 raspberrypi librespot[1164]: Published session_connected to raspotify/event Aug 25 11:11:52 raspberrypi librespot[1167]: Event session_client_changed fired Aug 25 11:11:52 raspberrypi librespot[1168]: Event volume_changed fired Aug 25 11:11:52 raspberrypi librespot[1169]: Event auto_play_changed fired Aug 25 11:11:52 raspberrypi librespot[1170]: Event filter_explicit_content_changed fired Aug 25 11:11:52 raspberrypi librespot[1171]: Event shuffle_changed fired Aug 25 11:11:52 raspberrypi librespot[1172]: Event repeat_changed fired Aug 25 11:11:52 raspberrypi librespot[1173]: Event play_request_id_changed fired Aug 25 11:11:52 raspberrypi librespot[1174]: Event loading fired Aug 25 11:11:54 raspberrypi librespot[1175]: Event track_changed fired Aug 25 11:11:54 raspberrypi librespot[1152]: Failed to create secure directory (/root/.config/pulse): Permission denied Aug 25 11:11:54 raspberrypi librespot[1176]: Event playing fired Aug 25 11:11:54 raspberrypi librespot[1176]: Published playing to raspotify/event <disconnect Spotify Connect session from phone> Aug 25 11:12:10 raspberrypi librespot[1152]: [2025-08-24T23:12:10Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 25 11:12:10 raspberrypi librespot[1152]: [2025-08-24T23:12:10Z ERROR librespot_connect::spirc] could not dispatch connect state update: Client specified an invalid argument { Response status code: 411 Length Required } Aug 25 11:13:48 raspberrypi librespot[1226]: Event preload_next fired Aug 25 11:14:18 raspberrypi librespot[1152]: [2025-08-24T23:14:18Z WARN librespot_connect::spirc] failed filling up next_track during stopping: Invalid state { context is not available. type: Default } Aug 25 11:14:18 raspberrypi librespot[1241]: Event end_of_track fired Aug 25 11:14:19 raspberrypi librespot[1243]: Event stopped fired Aug 25 11:14:19 raspberrypi librespot[1243]: Published stopped to raspotify/event ``` ### Host (what you are running `librespot` on): - OS: Linux - Platform: Raspberry Pi 4
kerem 2026-02-27 19:32:02 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-27 19:32:03 +03:00
Author
Owner
Copy link

@photovoltex commented on GitHub (Aug 25, 2025):

I ran into that problem during development... And I had it fixed but seem to have broken it during cleaning up the code and forgot to test it again because I was in a hurry. Classic mistake while fixing bugs.

Ah, and it's because the headers are overwritten when headers are given as parameters, which they are for the disconnect method.

<!-- gh-comment-id:3218917711 --> @photovoltex commented on GitHub (Aug 25, 2025): I ran into that problem during development... And I had it fixed but seem to have broken it during cleaning up the code and forgot to test it again because I was in a hurry. Classic mistake while fixing bugs. Ah, and it's because the headers are overwritten when headers are given as parameters, which they are for the disconnect method.
kerem commented 2026-02-27 19:32:03 +03:00
Author
Owner
Copy link

@roderickvd commented on GitHub (Aug 25, 2025):

It happens 😆

We can roll out a v0.7.1 bug fix release in the weekend.

<!-- gh-comment-id:3218941701 --> @roderickvd commented on GitHub (Aug 25, 2025): It happens 😆 We can roll out a v0.7.1 bug fix release in the weekend.
kerem commented 2026-02-27 19:32:03 +03:00
Author
Owner
Copy link

@photovoltex commented on GitHub (Aug 25, 2025):

Good to here, what a silly mistake. I already have created the PR for it^^;

<!-- gh-comment-id:3218959816 --> @photovoltex commented on GitHub (Aug 25, 2025): Good to here, what a silly mistake. I already have created the PR for it^^;
kerem commented 2026-02-27 19:32:03 +03:00
Author
Owner
Copy link

@roderickvd commented on GitHub (Aug 25, 2025):

Please confirm that #1552 is working so we can schedule it for a quick v0.7.1 release.

<!-- gh-comment-id:3221698143 --> @roderickvd commented on GitHub (Aug 25, 2025): Please confirm that #1552 is working so we can schedule it for a quick v0.7.1 release.
kerem commented 2026-02-27 19:32:03 +03:00
Author
Owner
Copy link

@samcook commented on GitHub (Aug 25, 2025):

I've built and run that PR and I can confirm that disconnecting the session appears to be working for me now - music stops playing immediately, and the event fires as expected.

Aug 26 09:42:36 raspberrypi systemd[1]: Started Raspotify (Spotify Connect Client).

<establish Spotify Connect session from phone here>

Aug 26 09:45:47 raspberrypi librespot[1262]: [2025-08-25T21:45:47Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 26 09:45:47 raspberrypi librespot[1388]: Event session_connected fired
Aug 26 09:45:47 raspberrypi librespot[1388]: Published session_connected to raspotify/event
Aug 26 09:45:47 raspberrypi librespot[1396]: Event session_client_changed fired
Aug 26 09:45:47 raspberrypi librespot[1401]: Event volume_changed fired
Aug 26 09:45:47 raspberrypi librespot[1403]: Event auto_play_changed fired
Aug 26 09:45:47 raspberrypi librespot[1407]: Event filter_explicit_content_changed fired
Aug 26 09:45:47 raspberrypi librespot[1408]: Event shuffle_changed fired
Aug 26 09:45:47 raspberrypi librespot[1409]: Event repeat_changed fired
Aug 26 09:45:47 raspberrypi librespot[1410]: Event play_request_id_changed fired
Aug 26 09:45:47 raspberrypi librespot[1411]: Event loading fired
Aug 26 09:45:48 raspberrypi librespot[1423]: Event track_changed fired
Aug 26 09:45:48 raspberrypi librespot[1424]: Event paused fired
Aug 26 09:45:48 raspberrypi librespot[1424]: Published paused to raspotify/event

<disconnect Spotify Connect session from phone here>

Aug 26 09:46:02 raspberrypi librespot[1262]: [2025-08-25T21:46:02Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 26 09:46:02 raspberrypi librespot[1262]: [2025-08-25T21:46:02Z WARN  librespot_connect::spirc] failed filling up next_track during stopping: Invalid state { context is not available. type: Default }
Aug 26 09:46:02 raspberrypi librespot[1440]: Event session_disconnected fired
Aug 26 09:46:02 raspberrypi librespot[1440]: Published session_disconnected to raspotify/event
Aug 26 09:46:02 raspberrypi librespot[1442]: Event stopped fired
Aug 26 09:46:02 raspberrypi librespot[1442]: Published stopped to raspotify/event

There are still warnings about context not being available, not sure if they're anything to worry about or not?

<!-- gh-comment-id:3221843629 --> @samcook commented on GitHub (Aug 25, 2025): I've built and run that PR and I can confirm that disconnecting the session appears to be working for me now - music stops playing immediately, and the event fires as expected. ``` Aug 26 09:42:36 raspberrypi systemd[1]: Started Raspotify (Spotify Connect Client). <establish Spotify Connect session from phone here> Aug 26 09:45:47 raspberrypi librespot[1262]: [2025-08-25T21:45:47Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 26 09:45:47 raspberrypi librespot[1388]: Event session_connected fired Aug 26 09:45:47 raspberrypi librespot[1388]: Published session_connected to raspotify/event Aug 26 09:45:47 raspberrypi librespot[1396]: Event session_client_changed fired Aug 26 09:45:47 raspberrypi librespot[1401]: Event volume_changed fired Aug 26 09:45:47 raspberrypi librespot[1403]: Event auto_play_changed fired Aug 26 09:45:47 raspberrypi librespot[1407]: Event filter_explicit_content_changed fired Aug 26 09:45:47 raspberrypi librespot[1408]: Event shuffle_changed fired Aug 26 09:45:47 raspberrypi librespot[1409]: Event repeat_changed fired Aug 26 09:45:47 raspberrypi librespot[1410]: Event play_request_id_changed fired Aug 26 09:45:47 raspberrypi librespot[1411]: Event loading fired Aug 26 09:45:48 raspberrypi librespot[1423]: Event track_changed fired Aug 26 09:45:48 raspberrypi librespot[1424]: Event paused fired Aug 26 09:45:48 raspberrypi librespot[1424]: Published paused to raspotify/event <disconnect Spotify Connect session from phone here> Aug 26 09:46:02 raspberrypi librespot[1262]: [2025-08-25T21:46:02Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 26 09:46:02 raspberrypi librespot[1262]: [2025-08-25T21:46:02Z WARN librespot_connect::spirc] failed filling up next_track during stopping: Invalid state { context is not available. type: Default } Aug 26 09:46:02 raspberrypi librespot[1440]: Event session_disconnected fired Aug 26 09:46:02 raspberrypi librespot[1440]: Published session_disconnected to raspotify/event Aug 26 09:46:02 raspberrypi librespot[1442]: Event stopped fired Aug 26 09:46:02 raspberrypi librespot[1442]: Published stopped to raspotify/event ``` There are still warnings about context not being available, not sure if they're anything to worry about or not?
kerem commented 2026-02-27 19:32:03 +03:00
Author
Owner
Copy link

@samcook commented on GitHub (Aug 26, 2025):

Just as a follow up to this, I don't know if it's related or not...

A couple of hours after I disconnected the session from the previous comment I attempted to establish a new Spotify Connect session. On my Android phone, the session was sitting "connecting" for almost a minute (during which time I killed the Spotify app on the phone, reopened it, and tried to establish the Spotify Connect session again). Eventually after about a minute it connected, fired the event switching on my AV receiver, and started playing music.

Here are the logs from that (the first 4 lines below are the last 4 lines from the previous comment, so nothing else happened in between):

Aug 26 09:46:02 raspberrypi librespot[1440]: Event session_disconnected fired
Aug 26 09:46:02 raspberrypi librespot[1440]: Published session_disconnected to raspotify/event
Aug 26 09:46:02 raspberrypi librespot[1442]: Event stopped fired
Aug 26 09:46:02 raspberrypi librespot[1442]: Published stopped to raspotify/event

<tried to establish a Spotify Connect session from my phone>

Aug 26 12:21:20 raspberrypi librespot[1262]: [2025-08-26T00:21:20Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 26 12:21:20 raspberrypi librespot[5068]: Event session_disconnected fired
Aug 26 12:21:20 raspberrypi librespot[5068]: Published session_disconnected to raspotify/event
Aug 26 12:21:21 raspberrypi librespot[1262]: [2025-08-26T00:21:21Z WARN  librespot_core::dealer] Wasn't able to reply to dealer request: channel closed
Aug 26 12:21:26 raspberrypi librespot[1262]: [2025-08-26T00:21:26Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 26 12:21:27 raspberrypi librespot[5081]: Event session_disconnected fired
Aug 26 12:21:27 raspberrypi librespot[5081]: Published session_disconnected to raspotify/event
Aug 26 12:21:27 raspberrypi librespot[1262]: [2025-08-26T00:21:27Z WARN  librespot_core::dealer] Wasn't able to reply to dealer request: channel closed
Aug 26 12:21:33 raspberrypi librespot[1262]: [2025-08-26T00:21:33Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 26 12:21:33 raspberrypi librespot[5083]: Event session_disconnected fired
Aug 26 12:21:33 raspberrypi librespot[5083]: Published session_disconnected to raspotify/event
Aug 26 12:21:34 raspberrypi librespot[1262]: [2025-08-26T00:21:34Z WARN  librespot_core::dealer] Wasn't able to reply to dealer request: channel closed
Aug 26 12:21:40 raspberrypi librespot[1262]: [2025-08-26T00:21:40Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 26 12:21:40 raspberrypi librespot[5085]: Event session_disconnected fired
Aug 26 12:21:40 raspberrypi librespot[5085]: Published session_disconnected to raspotify/event
Aug 26 12:21:40 raspberrypi librespot[1262]: [2025-08-26T00:21:40Z WARN  librespot_core::dealer] Wasn't able to reply to dealer request: channel closed
Aug 26 12:21:46 raspberrypi librespot[1262]: [2025-08-26T00:21:46Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 26 12:21:47 raspberrypi librespot[5098]: Event session_disconnected fired
Aug 26 12:21:47 raspberrypi librespot[5098]: Published session_disconnected to raspotify/event
Aug 26 12:21:47 raspberrypi librespot[1262]: [2025-08-26T00:21:47Z WARN  librespot_core::dealer] Wasn't able to reply to dealer request: channel closed
Aug 26 12:21:57 raspberrypi librespot[1262]: [2025-08-26T00:21:57Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 26 12:21:57 raspberrypi librespot[5101]: Event session_disconnected fired
Aug 26 12:21:57 raspberrypi librespot[5101]: Published session_disconnected to raspotify/event
Aug 26 12:21:58 raspberrypi librespot[1262]: [2025-08-26T00:21:58Z WARN  librespot_core::dealer] Wasn't able to reply to dealer request: channel closed
Aug 26 12:22:03 raspberrypi librespot[1262]: [2025-08-26T00:22:03Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 26 12:22:04 raspberrypi librespot[5103]: Event session_disconnected fired
Aug 26 12:22:04 raspberrypi librespot[5103]: Published session_disconnected to raspotify/event
Aug 26 12:22:04 raspberrypi librespot[1262]: [2025-08-26T00:22:04Z WARN  librespot_core::dealer] Wasn't able to reply to dealer request: channel closed
Aug 26 12:22:10 raspberrypi librespot[1262]: [2025-08-26T00:22:10Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 26 12:22:10 raspberrypi librespot[5116]: Event session_disconnected fired
Aug 26 12:22:10 raspberrypi librespot[5116]: Published session_disconnected to raspotify/event
Aug 26 12:22:11 raspberrypi librespot[1262]: [2025-08-26T00:22:11Z WARN  librespot_core::dealer] Wasn't able to reply to dealer request: channel closed
Aug 26 12:22:17 raspberrypi librespot[1262]: [2025-08-26T00:22:17Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default
Aug 26 12:22:17 raspberrypi librespot[5118]: Event session_disconnected fired
Aug 26 12:22:17 raspberrypi librespot[5118]: Published session_disconnected to raspotify/event
Aug 26 12:22:18 raspberrypi librespot[1262]: [2025-08-26T00:22:18Z WARN  librespot_core::dealer] Wasn't able to reply to dealer request: channel closed
Aug 26 12:22:23 raspberrypi librespot[1262]: [2025-08-26T00:22:23Z WARN  librespot_connect::state::context] couldn't load context info because: context is not available. type: Default

<connection eventually established>

Aug 26 12:22:24 raspberrypi librespot[5120]: Event session_connected fired
Aug 26 12:22:24 raspberrypi librespot[5120]: Published session_connected to raspotify/event
Aug 26 12:22:24 raspberrypi librespot[5124]: Event session_client_changed fired
Aug 26 12:22:24 raspberrypi librespot[5125]: Event volume_changed fired
Aug 26 12:22:24 raspberrypi librespot[5126]: Event auto_play_changed fired
Aug 26 12:22:24 raspberrypi librespot[5127]: Event filter_explicit_content_changed fired
Aug 26 12:22:24 raspberrypi librespot[5128]: Event shuffle_changed fired
Aug 26 12:22:24 raspberrypi librespot[5129]: Event repeat_changed fired
Aug 26 12:22:24 raspberrypi librespot[5130]: Event play_request_id_changed fired
Aug 26 12:22:24 raspberrypi librespot[5131]: Event loading fired
Aug 26 12:22:25 raspberrypi librespot[5132]: Event track_changed fired
Aug 26 12:22:25 raspberrypi librespot[5133]: Event paused fired
Aug 26 12:22:25 raspberrypi librespot[5133]: Published paused to raspotify/event
<!-- gh-comment-id:3222266111 --> @samcook commented on GitHub (Aug 26, 2025): Just as a follow up to this, I don't know if it's related or not... A couple of hours after I disconnected the session from the previous comment I attempted to establish a new Spotify Connect session. On my Android phone, the session was sitting "connecting" for almost a minute (during which time I killed the Spotify app on the phone, reopened it, and tried to establish the Spotify Connect session again). Eventually after about a minute it connected, fired the event switching on my AV receiver, and started playing music. Here are the logs from that (the first 4 lines below are the last 4 lines from the previous comment, so nothing else happened in between): ``` Aug 26 09:46:02 raspberrypi librespot[1440]: Event session_disconnected fired Aug 26 09:46:02 raspberrypi librespot[1440]: Published session_disconnected to raspotify/event Aug 26 09:46:02 raspberrypi librespot[1442]: Event stopped fired Aug 26 09:46:02 raspberrypi librespot[1442]: Published stopped to raspotify/event <tried to establish a Spotify Connect session from my phone> Aug 26 12:21:20 raspberrypi librespot[1262]: [2025-08-26T00:21:20Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 26 12:21:20 raspberrypi librespot[5068]: Event session_disconnected fired Aug 26 12:21:20 raspberrypi librespot[5068]: Published session_disconnected to raspotify/event Aug 26 12:21:21 raspberrypi librespot[1262]: [2025-08-26T00:21:21Z WARN librespot_core::dealer] Wasn't able to reply to dealer request: channel closed Aug 26 12:21:26 raspberrypi librespot[1262]: [2025-08-26T00:21:26Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 26 12:21:27 raspberrypi librespot[5081]: Event session_disconnected fired Aug 26 12:21:27 raspberrypi librespot[5081]: Published session_disconnected to raspotify/event Aug 26 12:21:27 raspberrypi librespot[1262]: [2025-08-26T00:21:27Z WARN librespot_core::dealer] Wasn't able to reply to dealer request: channel closed Aug 26 12:21:33 raspberrypi librespot[1262]: [2025-08-26T00:21:33Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 26 12:21:33 raspberrypi librespot[5083]: Event session_disconnected fired Aug 26 12:21:33 raspberrypi librespot[5083]: Published session_disconnected to raspotify/event Aug 26 12:21:34 raspberrypi librespot[1262]: [2025-08-26T00:21:34Z WARN librespot_core::dealer] Wasn't able to reply to dealer request: channel closed Aug 26 12:21:40 raspberrypi librespot[1262]: [2025-08-26T00:21:40Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 26 12:21:40 raspberrypi librespot[5085]: Event session_disconnected fired Aug 26 12:21:40 raspberrypi librespot[5085]: Published session_disconnected to raspotify/event Aug 26 12:21:40 raspberrypi librespot[1262]: [2025-08-26T00:21:40Z WARN librespot_core::dealer] Wasn't able to reply to dealer request: channel closed Aug 26 12:21:46 raspberrypi librespot[1262]: [2025-08-26T00:21:46Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 26 12:21:47 raspberrypi librespot[5098]: Event session_disconnected fired Aug 26 12:21:47 raspberrypi librespot[5098]: Published session_disconnected to raspotify/event Aug 26 12:21:47 raspberrypi librespot[1262]: [2025-08-26T00:21:47Z WARN librespot_core::dealer] Wasn't able to reply to dealer request: channel closed Aug 26 12:21:57 raspberrypi librespot[1262]: [2025-08-26T00:21:57Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 26 12:21:57 raspberrypi librespot[5101]: Event session_disconnected fired Aug 26 12:21:57 raspberrypi librespot[5101]: Published session_disconnected to raspotify/event Aug 26 12:21:58 raspberrypi librespot[1262]: [2025-08-26T00:21:58Z WARN librespot_core::dealer] Wasn't able to reply to dealer request: channel closed Aug 26 12:22:03 raspberrypi librespot[1262]: [2025-08-26T00:22:03Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 26 12:22:04 raspberrypi librespot[5103]: Event session_disconnected fired Aug 26 12:22:04 raspberrypi librespot[5103]: Published session_disconnected to raspotify/event Aug 26 12:22:04 raspberrypi librespot[1262]: [2025-08-26T00:22:04Z WARN librespot_core::dealer] Wasn't able to reply to dealer request: channel closed Aug 26 12:22:10 raspberrypi librespot[1262]: [2025-08-26T00:22:10Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 26 12:22:10 raspberrypi librespot[5116]: Event session_disconnected fired Aug 26 12:22:10 raspberrypi librespot[5116]: Published session_disconnected to raspotify/event Aug 26 12:22:11 raspberrypi librespot[1262]: [2025-08-26T00:22:11Z WARN librespot_core::dealer] Wasn't able to reply to dealer request: channel closed Aug 26 12:22:17 raspberrypi librespot[1262]: [2025-08-26T00:22:17Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default Aug 26 12:22:17 raspberrypi librespot[5118]: Event session_disconnected fired Aug 26 12:22:17 raspberrypi librespot[5118]: Published session_disconnected to raspotify/event Aug 26 12:22:18 raspberrypi librespot[1262]: [2025-08-26T00:22:18Z WARN librespot_core::dealer] Wasn't able to reply to dealer request: channel closed Aug 26 12:22:23 raspberrypi librespot[1262]: [2025-08-26T00:22:23Z WARN librespot_connect::state::context] couldn't load context info because: context is not available. type: Default <connection eventually established> Aug 26 12:22:24 raspberrypi librespot[5120]: Event session_connected fired Aug 26 12:22:24 raspberrypi librespot[5120]: Published session_connected to raspotify/event Aug 26 12:22:24 raspberrypi librespot[5124]: Event session_client_changed fired Aug 26 12:22:24 raspberrypi librespot[5125]: Event volume_changed fired Aug 26 12:22:24 raspberrypi librespot[5126]: Event auto_play_changed fired Aug 26 12:22:24 raspberrypi librespot[5127]: Event filter_explicit_content_changed fired Aug 26 12:22:24 raspberrypi librespot[5128]: Event shuffle_changed fired Aug 26 12:22:24 raspberrypi librespot[5129]: Event repeat_changed fired Aug 26 12:22:24 raspberrypi librespot[5130]: Event play_request_id_changed fired Aug 26 12:22:24 raspberrypi librespot[5131]: Event loading fired Aug 26 12:22:25 raspberrypi librespot[5132]: Event track_changed fired Aug 26 12:22:25 raspberrypi librespot[5133]: Event paused fired Aug 26 12:22:25 raspberrypi librespot[5133]: Published paused to raspotify/event ```
kerem commented 2026-02-27 19:32:03 +03:00
Author
Owner
Copy link

@photovoltex commented on GitHub (Aug 26, 2025):

That's a very good hint. That you even have to option to reconnect is probably only because both devices are in the same network, otherwise the device will not appear anymore. That's because of a misplaced method invocation that removes the connect state on disconnect.

<!-- gh-comment-id:3224670525 --> @photovoltex commented on GitHub (Aug 26, 2025): That's a very good hint. That you even have to option to reconnect is probably only because both devices are in the same network, otherwise the device will not appear anymore. That's because of a misplaced method invocation that removes the connect state on disconnect.
kerem commented 2026-02-27 19:32:03 +03:00
Author
Owner
Copy link

@samcook commented on GitHub (Aug 26, 2025):

Made a build with #1552 and #1555 combined, and it appears to be behaving itself for me now 🙏

<!-- gh-comment-id:3225760181 --> @samcook commented on GitHub (Aug 26, 2025): Made a build with #1552 and #1555 combined, and it appears to be behaving itself for me now 🙏
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev
v0.8.0
v0.7.1
v0.7.0
v0.6.0
v0.5.0
v0.4.2
v0.4.1
v0.4.0
v0.3.1
v0.3.0
v0.2.0
v0.1.6
v0.1.5
v0.1.3
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels   
A-Alsa

   
SpotifyAPI

   
Tokio 1.0

   
audio

   
bug

   
can't reproduce

   
compilation

   
dependencies

   
duplicate

   
enhancement

   
good first issue

   
help wanted

   
high priority

   
imported

   
imported

   
invalid

   
new api

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
reverse engineering

   
wiki

   
wontfix
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/librespot#702
No description provided.