[FIXED] Problem with Spotify connect

[jhujube premium]

jhujube premium

26. Mai 2018 at 1:11 #35894

Hello,

I have a problem with the plugin Spotify Connect…
My config is : PiZeroW with justboom, license Premium with the last version of Max2play (i even tried the Version Beta-180517 with no success). Squeezelite & Airplay are stopped.
it starts correctly (It’s what he says and gives me an Id), but when i try to send music via my smartphone, Max2play doesn’t appear in the list, and if i do a refresh on my max2play page, it tells me that the service is not working.
In fact, the service is stopped exactly when Spotify starts on my smartphone or my computer.
If i click on the Debug information, i have the following message:

#### Librespot Output ####
INFO:librespot: librespot deb240c (2018-05-01). Built on 2018-05-03. Build ID: 33XHsEPm
INFO:librespot_core::session: Connecting to AP „gew1-accesspoint-b-vdsm.ap.spotify.com:4070“
INFO:librespot_core::session: Authenticated as „*******“ !
INFO:librespot_core::session: Country: „FR“
INFO:librespot_playback::audio_backend::alsa: Using alsa sink
thread ‚main‘ panicked at ‚called Result::unwrap() on an Err value: WireError(InvalidEnumValue(14))‘, libcore/result.rs:945:5
stack backtrace:
0: 0x9a5017 – std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h4ef6490c84cef3d0
at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
1: 0x99ed73 – std::sys_common::backtrace::_print::hea150ee4f33bb5de
at libstd/sys_common/backtrace.rs:71
2: 0x9a3a87 – std::panicking::default_hook::{{closure}}::h6c4396ff5bd61d89
at libstd/sys_common/backtrace.rs:59
at libstd/panicking.rs:380
3: 0x9a366b – std::panicking::default_hook::h0f6cb16cf06a0198
at libstd/panicking.rs:396
4: 0x9a3f2b – std::panicking::rust_panic_with_hook::h2207195920ffa55f
at libstd/panicking.rs:576
5: 0x9a3d8f – std::panicking::begin_panic::h8d43a09cf6d6e5f1
at libstd/panicking.rs:537
6: 0x9a3d13 – std::panicking::begin_panic_fmt::hd9afc94159ee9735
at libstd/panicking.rs:521
7: 0x9a3cab – rust_begin_unwind
at libstd/panicking.rs:497
8: 0x9f208b – core::panicking::panic_fmt::h0bd854df201d1baf
at libcore/panicking.rs:71
9: 0x51fb23 – core::result::unwrap_failed::hddf59da180aa5028
10: 0x4f7cef – core::ops::function::impls::<impl core::ops::function::FnOnce for &’a mut F>::call_once::he8949bb52588c02d
11: 0x52b293 – <futures::stream::map::Map<S, F> as futures::stream::Stream>::poll::h71adfc88d0d26074
12: 0x4fac17 – <librespot_connect::spirc::SpircTask as futures::future::Future>::poll::hf6cd1264a1f3f55c
13: 0x4df163 – <librespot::Main as futures::future::Future>::poll::hf19596b54d747405
14: 0x4ba693 – futures::task_impl::std::set::h37717c5fc1996b55
15: 0x4d6827 – <futures::future::lazy::Lazy<F, R> as futures::future::Future>::poll::h932e698bfa1f4f96
16: 0x4ba83f – futures::task_impl::std::set::hbe0a3f27a98bd2cf
17: 0x4c15bb – <std::thread::local::LocalKey<T>>::with::h8887c0bf6c258a13
18: 0x4c5e43 – <tokio::executor::current_thread::Entered<‚a, P>>::block_on::hce8d813fcf0f0ecd
19: 0x4c0fd3 – <std::thread::local::LocalKey<T>>::with::h4b562a8abd7a0522
20: 0x4c1427 – <std::thread::local::LocalKey<T>>::with::h7e520266b933ea30
21: 0x4c1277 – <std::thread::local::LocalKey<T>>::with::h6c7fa2726200d6fe
22: 0x4c2a2f – <scoped_tls::ScopedKey<T>>::set::h1383930fc545927e
23: 0x4bd0c3 – tokio_core::reactor::Core::run::h58cbc7617adfe774
24: 0x4e1007 – librespot::main::h01990349424f3ae5
25: 0x4d4333 – std::rt::lang_start::{{closure}}::h1a708eb37359d32e
26: 0x9a3be3 – std::panicking::try::do_call::h5f03c49f73b7300e
at libstd/rt.rs:59
at libstd/panicking.rs:479
27: 0x9b332b – __rust_maybe_catch_panic
at libpanic_unwind/lib.rs:102
28: 0x9a4353 – std::rt::lang_start_internal::h907d77b40aa767dd
at libstd/panicking.rs:458
at libstd/panic.rs:358
at libstd/rt.rs:58
29: 0x4e1bff – main
30: 0xb6d62677 – __libc_start_main

Am’I doing something wrong?
Thanks in advance,

Jhujube

[rodrigo.silva]

rodrigo.silva

27. Mai 2018 at 21:06 #35905

Hi !
Great job btw !!

I´m having the same problem but with a RPI model B (just B, not B+)
Here´s the debug info:

#### Librespot Output ####
INFO:librespot: librespot deb240c (2018-05-01). Built on 2018-05-03. Build ID: 33XHsEPm
INFO:librespot_core::session: Connecting to AP „guc3-accesspoint-b-qffh.ap.spotify.com:4070“
INFO:librespot_core::session: Authenticated as „rodrigo.silva“ !
INFO:librespot_core::session: Country: „UY“
INFO:librespot_playback::audio_backend::alsa: Using alsa sink
thread ‚main‘ panicked at ‚called Result::unwrap() on an Err value: WireError(InvalidEnumValue(14))‘, libcore/result.rs:945:5
stack backtrace:
0: 0x91e017 – std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h4ef6490c84cef3d0
at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
1: 0x917d73 – std::sys_common::backtrace::_print::hea150ee4f33bb5de
at libstd/sys_common/backtrace.rs:71
2: 0x91ca87 – std::panicking::default_hook::{{closure}}::h6c4396ff5bd61d89
at libstd/sys_common/backtrace.rs:59
at libstd/panicking.rs:380
3: 0x91c66b – std::panicking::default_hook::h0f6cb16cf06a0198
at libstd/panicking.rs:396
4: 0x91cf2b – std::panicking::rust_panic_with_hook::h2207195920ffa55f
at libstd/panicking.rs:576
5: 0x91cd8f – std::panicking::begin_panic::h8d43a09cf6d6e5f1
at libstd/panicking.rs:537
6: 0x91cd13 – std::panicking::begin_panic_fmt::hd9afc94159ee9735
at libstd/panicking.rs:521
7: 0x91ccab – rust_begin_unwind
at libstd/panicking.rs:497
8: 0x96b08b – core::panicking::panic_fmt::h0bd854df201d1baf
at libcore/panicking.rs:71
9: 0x498b23 – core::result::unwrap_failed::hddf59da180aa5028
10: 0x470cef – core::ops::function::impls::<impl core::ops::function::FnOnce for &’a mut F>::call_once::he8949bb52588c02d
11: 0x4a4293 – <futures::stream::map::Map<S, F> as futures::stream::Stream>::poll::h71adfc88d0d26074
12: 0x473c17 – <librespot_connect::spirc::SpircTask as futures::future::Future>::poll::hf6cd1264a1f3f55c
13: 0x458163 – <librespot::Main as futures::future::Future>::poll::hf19596b54d747405
14: 0x433693 – futures::task_impl::std::set::h37717c5fc1996b55
15: 0x44f827 – <futures::future::lazy::Lazy<F, R> as futures::future::Future>::poll::h932e698bfa1f4f96
16: 0x43383f – futures::task_impl::std::set::hbe0a3f27a98bd2cf
17: 0x43a5bb – <std::thread::local::LocalKey<T>>::with::h8887c0bf6c258a13
18: 0x43ee43 – <tokio::executor::current_thread::Entered<‚a, P>>::block_on::hce8d813fcf0f0ecd
19: 0x439fd3 – <std::thread::local::LocalKey<T>>::with::h4b562a8abd7a0522
20: 0x43a427 – <std::thread::local::LocalKey<T>>::with::h7e520266b933ea30
21: 0x43a277 – <std::thread::local::LocalKey<T>>::with::h6c7fa2726200d6fe
22: 0x43ba2f – <scoped_tls::ScopedKey<T>>::set::h1383930fc545927e
23: 0x4360c3 – tokio_core::reactor::Core::run::h58cbc7617adfe774
24: 0x45a007 – librespot::main::h01990349424f3ae5
25: 0x44d333 – std::rt::lang_start::{{closure}}::h1a708eb37359d32e
26: 0x91cbe3 – std::panicking::try::do_call::h5f03c49f73b7300e
at libstd/rt.rs:59
at libstd/panicking.rs:479
27: 0x92c32b – __rust_maybe_catch_panic
at libpanic_unwind/lib.rs:102
28: 0x91d353 – std::rt::lang_start_internal::h907d77b40aa767dd
at libstd/panicking.rs:458
at libstd/panic.rs:358
at libstd/rt.rs:58
29: 0x45abff – main
30: 0xb6ce4677 – __libc_start_main

Thanks again !

RS

[Heiner premium]

Heiner premium

28. Mai 2018 at 16:44 #35925

Hi guys,

The older models still seem to have an issue with our update. For now, you can try using the old Jessie image or installing the Squeezebox Server and adding the Spotty plugin (HowTo)

[rodrigo.silva]

rodrigo.silva

28. Mai 2018 at 20:39 #35935

Hi Heiner !

Tks for your quick reply and all the hard work !!
I´ll try with the Jessie image and i´ll let you know.

Tks again !
RS

[jhujube premium]

jhujube premium

29. Mai 2018 at 0:51 #35942

Hi,

I tried Jessie, but with no success.
On the other hand, installing the Squeezebox Server and adding the Spotty plugin worked for me!
I’ll try spotify connect later when it will be modified for the Zero.

Thank you for your impressive work,

Jhujube

[rodrigo.silva]

rodrigo.silva

31. Mai 2018 at 0:16 #35986

Hi !!
Same here with the RPI model B, no luck.
I´ll try the Spotty plugin for LMS.

Thanks again.

RS

[Heiner premium]

Heiner premium

31. Mai 2018 at 10:08 #35992

Hi guys,

Sorry about the inconvenience, we fixed the bug for older models. Just reinstall the Spotify Connect Player and it should work again 🙂

[jhujube premium]

jhujube premium

3. Juni 2018 at 0:50 #36027

Hi,

I confirm that Spotify Connect Player now work on my Zero W !
Thank you very much,

Jhujube

[Heiner premium]

Heiner premium

4. Juni 2018 at 13:58 #36058

Hi Jhujube,

Thanks for the update! Glad to hear it’s working for you 🙂

[rodrigo.silva]

rodrigo.silva

5. Juni 2018 at 4:37 #36083

Hi !!

After last update it’s working flawlessly on rpi b.

Impressive work !!
Thank you so much !!

RS

PS: i Will do a reinstall with the stretch image to see if its working too.