HiFiBerry OS Spotify Connect

Diederik

December 29, 2020 19:02

None

Hi,

I was given a premium account (Duo) on Spotify earlier this week. I wanted to connect to Spotify Connect on my HiFiBerry AMP2 but couldn't.

I am on the same WiFi (wasn't sure if being on cable but in the same network would make a difference) and have Spotify active. Version HiFiBerryOS is 20201213.

My equaliser is off.

I can see the spotify connect option in my Spotify Windows application (or via the Spotify Android app), when I select my HiFiBerry, it tries to connect but then stops and keeps on playing on my device (laptop/cell phone respectively).

I checked the spotify config file under /etc but that was empty (which I though is strange but hey who am I to judge...)

So the question is: how can I connect to the HiFiBerry from within Spotify app

Date Votes

3 comments

0

HiFiBerry team December 30, 2020 05:46

When it stops, the spotify player on the Pi might have a problem. Try checking the logs

journalctl -u spotify

Comment actions Permalink

Diederik December 30, 2020 09:13

Hi, thanks for the quick reply.

I got:

Sep 12 12:16:52 hifiberry-ena systemd[1]: Starting Vollibrespot...
Sep 12 12:16:52 hifiberry-ena vollibrespot[685]: vollibrespot v0.2.2 UNKNOWN UNKNOWN (librespot 1a224a3 2020-10-25) -- Built On 2020-12-13
Sep 12 12:16:52 hifiberry-ena vollibrespot[685]: Reading Config from "/etc/vollibrespot.conf"
Sep 12 12:16:52 hifiberry-ena vollibrespot[685]: [Vollibrespot] : Using Alsa backend with device: default
Sep 12 12:16:53 hifiberry-ena restore-volume[754]: Simple mixer control 'Softvol',0
Sep 12 12:16:53 hifiberry-ena restore-volume[754]:   Capabilities: volume
Sep 12 12:16:53 hifiberry-ena restore-volume[754]:   Playback channels: Front Left - Front Right
Sep 12 12:16:53 hifiberry-ena restore-volume[754]:   Capture channels: Front Left - Front Right
Sep 12 12:16:53 hifiberry-ena restore-volume[754]:   Limits: 0 - 255
Sep 12 12:16:53 hifiberry-ena restore-volume[754]:   Front Left: 255 [100%]
Sep 12 12:16:53 hifiberry-ena restore-volume[754]:   Front Right: 255 [100%]
Sep 12 12:16:53 hifiberry-ena systemd[1]: Started Vollibrespot.
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]: [Vollibrespot] : Failed to resolve Access Point: HTTP error
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]: [Vollibrespot] : Using fallback "ap.spotify.com:443"
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]: [Vollibrespot] : Connecting to AP "ap.spotify.com:443"
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: "failed to lookup address informationSep 12 12:27:19 hifiberry-ena vollibrespot[685]: stack backtrace:
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:    0:   0xaac4dc - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:    1:   0xad4698 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:    2:   0xaa553c - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:    3:   0xaaebcc - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:    4:   0xaae880 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:    5:   0xaaf284 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:    6:   0xaaeea0 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:    7:   0xad1d70 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:    8:   0xad1bc8 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:    9:   0x7e0760 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   10:   0x778400 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   11:   0x78ac7c - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   12:   0x5b0630 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   13:   0x577d24 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   14:   0x58cac0 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   15:   0x56a93c - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   16:   0x58d7a8 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   17:   0x5a0940 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   18:   0x568b6c - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   19:   0x5b2578 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   20:   0x5a1870 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   21:   0xaaf648 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   22:   0x5b3030 - <unknown>
Sep 12 12:27:19 hifiberry-ena vollibrespot[685]:   23: 0x76c926c4 - __libc_start_main
Sep 12 12:27:19 hifiberry-ena systemd[1]: spotify.service: Main process exited, code=exited, status=101/n/a
Sep 12 12:27:19 hifiberry-ena systemd[1]: spotify.service: Failed with result 'exit-code'.
Sep 12 12:27:24 hifiberry-ena systemd[1]: spotify.service: Scheduled restart job, restart counter is at 1.
Sep 12 12:27:24 hifiberry-ena systemd[1]: Stopped Vollibrespot.
Sep 12 12:27:24 hifiberry-ena systemd[1]: Starting Vollibrespot...
Sep 12 12:27:24 hifiberry-ena vollibrespot[1122]: vollibrespot v0.2.2 UNKNOWN UNKNOWN (librespot 1a224a3 2020-10-25) -- Built On 2020-12-13
Sep 12 12:27:24 hifiberry-ena vollibrespot[1122]: Reading Config from "/etc/vollibrespot.conf"

Regarding the date:

I am a bit confused why the date is set to Sep 12 and 12:27 though. I installed HiFiBerry from scratch yesterday (Dec 29 2020) so it should have read Dec 30 09:xy:za or something and I set my Country as well so I thought it would have been configured in the correct timezone as well.

Regarding the AP:

I have no clue, why it would not detect an access point, I am SSH'ing into it and my other devices on the same network have no problem connecting with it. I'll note that my wifi and network is behind one of my ISP. E.g. ISP 192.168.1.0 and my own network is 10.0.90.00. All internet traffic on 10.0.90.00 works fine (for Plex I use port forwarding though)

Anyway, to continue

Regarding the date

Running the date command gives:

Sat Sep 12 12:48:03 UTC 2020

Running the timedatectl command gives:

timedatectl
               Local time: Sat 2020-09-12 12:55:53 UTC
           Universal time: Sat 2020-09-12 12:55:53 UTC
                 RTC time: n/a
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: no
              NTP service: active
          RTC in local TZ: no

Regarding the AP

I noticed my router on my network for HifiBerry and cellphone mentioning issues

[DHCP IP: (10.0.90.01)] to MAC address MY:MA:CA:DD:RE:SS, Wednesday, Dec 30,2020 09:21:51
[WLAN access rejected: incorrect security] from MAC MY:MA:CA:DD:RE:SS, Wednesday, Dec 30,2020 09:21:50

I am not sure, but perhaps it is annoyed with having to handle information for a device that is communicating from the past?

Resolution needed...

I am thinking to set my timezone and let it synchronize.

timedatectl set-timezone 'mytimezone'
timedatectl set-ntp yes // in case this isn't done yet, haven't checked

Would that help? Shouldn't that have been configured on installation?

Should I look for something else, e.g. port forwarding - not sure why though -

Thanks!

0
Diederik December 30, 2020 13:08
Hi it works now.

The commands I mentioned above did not do the trick. Might be that syncing is not possible if the time is months off.

What did work in the end:

EDIT: I installed the OS on another HiFiBerry and could again not connect with Spotify and the time/date/timezone were off + the sync that should sync with the actual time could not do it's job. So here is the complete list of commands that worked for me.
```
timedatectl set-ntp false
timedatectl set-timezone 'yourtimezone'
timedatectl set-time YYYY-MM-DD
timedatectl set-time HH:MM:SS
timedatectl set-ntp true
```
Where:
- 'yourtimezone' is the one that matches yours based on the options in timedatectl list-timezones
- YYYY-MM-DD is the current date
- HH:MM:SS is the time in close range of the current time. I was half a minute off and that was corrected when it got synced
After these commands, I was able to use Spotify connect. Good luck!
Edited by Diederik December 30, 2020 13:30

Comment actions Permalink

Please sign in to leave a comment.