Spotify Connect not able to start

Max2Play Home 2016 (en) Forums Max2Play as Squeezebox (Player / Server) Spotify Connect not able to start

This topic contains 6 replies, has 2 voices, and was last updated by  Heiner Moderator 3 years, 5 months ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • 25. Mai 2018 at 21:45 #35888

    Hi

    I am new to Max2Play and decided to use this Musicplayer as Spotify Connect was unstable on Volumio. Spotify Connect together with a Raspberry Pi and Hifiberry DAC+ is the solution I’d like to use.

    Unfortunately even after a fresh install the service doen’t start. Log output is as follows:

    Trying to launch ... NOT successful Click here to show detailed information
    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-mf2s.ap.spotify.com:4070"
    INFO:librespot_core::session: Authenticated as "itzekocke" !
    INFO:librespot_playback::audio_backend::alsa: Using alsa sink
    INFO:librespot_core::session: Country: "AT"
    thread 'main' panicked at 'called <code>Result::unwrap()</code> on an <code>Err</code> value: WireError(InvalidEnumValue(14))', libcore/result.rs:945:5
    stack backtrace:
    0: 0x961017 - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h4ef6490c84cef3d0
    at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
    1: 0x95ad73 - std::sys_common::backtrace::_print::hea150ee4f33bb5de
    at libstd/sys_common/backtrace.rs:71
    2: 0x95fa87 - std::panicking::default_hook::{{closure}}::h6c4396ff5bd61d89
    at libstd/sys_common/backtrace.rs:59
    at libstd/panicking.rs:380
    3: 0x95f66b - std::panicking::default_hook::h0f6cb16cf06a0198
    at libstd/panicking.rs:396
    4: 0x95ff2b - std::panicking::rust_panic_with_hook::h2207195920ffa55f
    at libstd/panicking.rs:576
    5: 0x95fd8f - std::panicking::begin_panic::h8d43a09cf6d6e5f1
    at libstd/panicking.rs:537
    6: 0x95fd13 - std::panicking::begin_panic_fmt::hd9afc94159ee9735
    at libstd/panicking.rs:521
    7: 0x95fcab - rust_begin_unwind
    at libstd/panicking.rs:497
    8: 0x9ae08b - core::panicking::panic_fmt::h0bd854df201d1baf
    at libcore/panicking.rs:71
    9: 0x4dbb23 - core::result::unwrap_failed::hddf59da180aa5028
    10: 0x4b3cef - core::ops::function::impls:: for &'a mut F>::call_once::he8949bb52588c02d
    11: 0x4e7293 - as futures::stream::Stream>::poll::h71adfc88d0d26074
    12: 0x4b6c17 - ::poll::hf6cd1264a1f3f55c
    13: 0x49b163 - ::poll::hf19596b54d747405
    14: 0x476693 - futures::task_impl::std::set::h37717c5fc1996b55
    15: 0x492827 - as futures::future::Future>::poll::h932e698bfa1f4f96
    16: 0x47683f - futures::task_impl::std::set::hbe0a3f27a98bd2cf
    17: 0x47d5bb - >::with::h8887c0bf6c258a13
    18: 0x481e43 - >::block_on::hce8d813fcf0f0ecd
    19: 0x47cfd3 - >::with::h4b562a8abd7a0522
    20: 0x47d427 - >::with::h7e520266b933ea30
    21: 0x47d277 - >::with::h6c7fa2726200d6fe
    22: 0x47ea2f - >::set::h1383930fc545927e
    23: 0x4790c3 - tokio_core::reactor::Core::run::h58cbc7617adfe774
    24: 0x49d007 - librespot::main::h01990349424f3ae5
    25: 0x490333 - std::rt::lang_start::{{closure}}::h1a708eb37359d32e
    26: 0x95fbe3 - std::panicking::try::do_call::h5f03c49f73b7300e
    at libstd/rt.rs:59
    at libstd/panicking.rs:479
    27: 0x96f32b - __rust_maybe_catch_panic
    at libpanic_unwind/lib.rs:102
    28: 0x960353 - std::rt::lang_start_internal::h907d77b40aa767dd
    at libstd/panicking.rs:458
    at libstd/panic.rs:358
    at libstd/rt.rs:58
    29: 0x49dbff - main
    30: 0x76cac677 - __libc_start_main

    Please let me know how to solve the issue.

    Best regards,
    Gerold

    28. Mai 2018 at 13:33 #35914

    Hi Gerold,

    Which Raspberry Pi are you using? Also, with new install do you reinstall in the web interface?

    28. Mai 2018 at 15:36 #35922

    Hi Heiner,

    it’s a RASPBERRY PI 3 with a completely new install. After the initial install I updated via the webinterface as requested / proposed.

    Servus,

    Gerold

    28. Mai 2018 at 16:48 #35926

    By updated, you mean clicking the „Reinstall“-Button in the web interface?

    In this case, your Spotify Connect should definitely work.

    Please make sure your other players are not interfering (remove autostart, stop the players).

    28. Mai 2018 at 17:16 #35928

    Yes, and just reinstalled again.

    This is the debug output:

    
    #### 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-hb95.ap.spotify.com:4070"
    INFO:librespot_core::session: Authenticated as "itzekocke" !
    INFO:librespot_playback::audio_backend::alsa: Using alsa sink
    INFO:librespot_core::session: Country: "AT"
    thread 'main' panicked at 'called <code>Result::unwrap()</code> on an <code>Err</code> value: WireError(InvalidEnumValue(14))', libcore/result.rs:945:5
    stack backtrace:
       0:   0x9ce017 - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h4ef6490c84cef3d0
                           at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
       1:   0x9c7d73 - std::sys_common::backtrace::_print::hea150ee4f33bb5de
                           at libstd/sys_common/backtrace.rs:71
       2:   0x9cca87 - std::panicking::default_hook::{{closure}}::h6c4396ff5bd61d89
                           at libstd/sys_common/backtrace.rs:59
                           at libstd/panicking.rs:380
       3:   0x9cc66b - std::panicking::default_hook::h0f6cb16cf06a0198
                           at libstd/panicking.rs:396
       4:   0x9ccf2b - std::panicking::rust_panic_with_hook::h2207195920ffa55f
                           at libstd/panicking.rs:576
       5:   0x9ccd8f - std::panicking::begin_panic::h8d43a09cf6d6e5f1
                           at libstd/panicking.rs:537
       6:   0x9ccd13 - std::panicking::begin_panic_fmt::hd9afc94159ee9735
                           at libstd/panicking.rs:521
       7:   0x9cccab - rust_begin_unwind
                           at libstd/panicking.rs:497
       8:   0xa1b08b - core::panicking::panic_fmt::h0bd854df201d1baf
                           at libcore/panicking.rs:71
       9:   0x548b23 - core::result::unwrap_failed::hddf59da180aa5028
      10:   0x520cef - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &'a mut F>::call_once::he8949bb52588c02d
      11:   0x554293 - <futures::stream::map::Map<S, F> as futures::stream::Stream>::poll::h71adfc88d0d26074
      12:   0x523c17 - <librespot_connect::spirc::SpircTask as futures::future::Future>::poll::hf6cd1264a1f3f55c
      13:   0x508163 - <librespot::Main as futures::future::Future>::poll::hf19596b54d747405
      14:   0x4e3693 - futures::task_impl::std::set::h37717c5fc1996b55
      15:   0x4ff827 - <futures::future::lazy::Lazy<F, R> as futures::future::Future>::poll::h932e698bfa1f4f96
      16:   0x4e383f - futures::task_impl::std::set::hbe0a3f27a98bd2cf
      17:   0x4ea5bb - <std::thread::local::LocalKey<T>>::with::h8887c0bf6c258a13
      18:   0x4eee43 - <tokio::executor::current_thread::Entered<'a, P>>::block_on::hce8d813fcf0f0ecd
      19:   0x4e9fd3 - <std::thread::local::LocalKey<T>>::with::h4b562a8abd7a0522
      20:   0x4ea427 - <std::thread::local::LocalKey<T>>::with::h7e520266b933ea30
      21:   0x4ea277 - <std::thread::local::LocalKey<T>>::with::h6c7fa2726200d6fe
      22:   0x4eba2f - <scoped_tls::ScopedKey<T>>::set::h1383930fc545927e
      23:   0x4e60c3 - tokio_core::reactor::Core::run::h58cbc7617adfe774
      24:   0x50a007 - librespot::main::h01990349424f3ae5
      25:   0x4fd333 - std::rt::lang_start::{{closure}}::h1a708eb37359d32e
      26:   0x9ccbe3 - std::panicking::try::do_call::h5f03c49f73b7300e
                           at libstd/rt.rs:59
                           at libstd/panicking.rs:479
      27:   0x9dc32b - __rust_maybe_catch_panic
                           at libpanic_unwind/lib.rs:102
      28:   0x9cd353 - std::rt::lang_start_internal::h907d77b40aa767dd
                           at libstd/panicking.rs:458
                           at libstd/panic.rs:358
                           at libstd/rt.rs:58
      29:   0x50abff - main
      30: 0x76d8b677 - __libc_start_main
     
    
    #### Librespot Command Line Options ####
    error: Required option 'name' missing
    Usage: /opt/spotifyconnect/librespot [options]
    
    Options:
        -c, --cache CACHE   Path to a directory where files will be cached.
            --disable-audio-cache 
                            Disable caching of the audio data.
        -n, --name NAME     Device name
            --device-type DEVICE_TYPE
                            Displayed device type
        -b, --bitrate BITRATE
                            Bitrate (96, 160 or 320). Defaults to 160
            --onevent PROGRAM
                            Run PROGRAM when playback is about to begin.
        -v, --verbose       Enable verbose output
        -u, --username USERNAME
                            Username to sign in with
        -p, --password PASSWORD
                            Password
            --proxy PROXY   HTTP proxy to use when connecting
            --disable-discovery 
                            Disable discovery mode
            --backend BACKEND
                            Audio backend to use. Use '?' to list options
            --device DEVICE Audio device to use. Use '?' to list options if using
                            portaudio
            --mixer MIXER   Mixer to use
            --initial-volume VOLUME
                            Initial volume in %, once connected (must be from 0 to
                            100)
            --zeroconf-port ZEROCONF_PORT
                            The port the internal server advertised over zeroconf
                            uses.
            --enable-volume-normalisation 
                            Play all tracks at the same volume
            --normalisation-pregain PREGAIN
                            Pregain (dB) applied by volume normalisation
            --linear-volume 
                            increase volume linear instead of logarithmic.
    
     

    Any ideas?

    PS: deactivated IP6 and all other players.

    • This reply was modified 3 years, 5 months ago by  itzekocke.
    28. Mai 2018 at 23:03 #35941

    Update: after some non-successful attempts I decided to apt-get update/upgrade the fresh install – again without luck in terms of Spotify Connect. Then I deactivated the Spotify Connect plugin via the webinterface and installed https://github.com/dtcooper/raspotify – now the device is visible via the Spotify Android app as raspotify (max2play) and music playback works fine.

    Don’t know how this install will influence max2play. However, Spotify Connect is the only reason so far to use max2play.

    Awaiting advice to replace this workaround.

    Gerold

    29. Mai 2018 at 16:21 #35957

    Hi Gerold,

    I just recognized the issue. Your version is listed as Built on 2018-05-03 while our current working version should display as 05-18 or newer.

    Please try reinstalling again and check if this changes in your plugin.

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.

Register here