# No entries in "Spotify Browse"

**URL:** <https://discourse.mopidy.com/t/no-entries-in-spotify-browse/387>\
**Category:** Pi MusicBox (archive)\
**Created:** [December 3, 2014, 2:27pm UTC](https://discourse.mopidy.com/t/no-entries-in-spotify-browse/387 "2014-12-03T14:27:28Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![UOffermann](https://avatars.discourse-cdn.com/v4/letter/u/c68b51/32.png) [@UOffermann](https://discourse.mopidy.com/u/UOffermann)\
**Post date:** [December 3, 2014, 2:27pm UTC](https://discourse.mopidy.com/t/no-entries-in-spotify-browse/387/1 "2014-12-03T14:27:28Z")

</div>

I have installed musicbox 5.1RC2. Personal Playlists are now showing correctly. But when I go to “Spotify Browse” und choose e.g. “Genres & Moods” the directory is empty. Same occured with RC1. Browsing in “Spotify” Personal Top Tracks and so on works fine.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [December 3, 2014, 2:58pm UTC](https://discourse.mopidy.com/t/no-entries-in-spotify-browse/387/2 "2014-12-03T14:58:28Z")

</div>

Spotify recently changed part of their Tunigo API and this consequently broke the mopidy-spotify-tunigo extension that provides the functionality you are describing (the Personal Top Tracks functionality comes from mopidy-spotify). python-tunigo has been fixed in version 0.1.3 but the latest musicbox release probably has an older version. If you can run `mopidy deps` you can see what version of `tunigo` you are running. You should be able to update your tunigo version by running `pip install tunigo --upgrade` and then restarting Mopidy or just rebooting.

---

<div class="post-metadata">

**Author:** ![UOffermann](https://avatars.discourse-cdn.com/v4/letter/u/c68b51/32.png) [@UOffermann](https://discourse.mopidy.com/u/UOffermann)\
**Post date:** [December 3, 2014, 4:58pm UTC](https://discourse.mopidy.com/t/no-entries-in-spotify-browse/387/3 "2014-12-03T16:58:33Z")

</div>

Thanks for your help. Installed was python-tunigo 0.1.2. So I upgraded it with  
`pip install tunigo --upgrade`. All worked well and no errors were reported.  
But rebooting was not possible. The system crashed.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [December 3, 2014, 6:09pm UTC](https://discourse.mopidy.com/t/no-entries-in-spotify-browse/387/4 "2014-12-03T18:09:51Z")

</div>

Are you saying it now won’t boot? Or that it is now working?

---

<div class="post-metadata">

**Author:** ![UOffermann](https://avatars.discourse-cdn.com/v4/letter/u/c68b51/32.png) [@UOffermann](https://discourse.mopidy.com/u/UOffermann)\
**Post date:** [December 3, 2014, 6:57pm UTC](https://discourse.mopidy.com/t/no-entries-in-spotify-browse/387/5 "2014-12-03T18:57:08Z")

</div>

No, it doesn’t boot.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [December 3, 2014, 7:22pm UTC](https://discourse.mopidy.com/t/no-entries-in-spotify-browse/387/6 "2014-12-03T19:22:32Z")

</div>

Oh dear. I can only assume it's bad luck for it to crash and corrupt the image. Upgrading the package should obviously not have had any impact like this! Can you try again with a fresh image? A pain, I know.

---

<div class="post-metadata">

**Author:** ![UOffermann](https://avatars.discourse-cdn.com/v4/letter/u/c68b51/32.png) [@UOffermann](https://discourse.mopidy.com/u/UOffermann)\
**Post date:** [December 4, 2014, 8:46am UTC](https://discourse.mopidy.com/t/no-entries-in-spotify-browse/387/7 "2014-12-04T08:46:56Z")

</div>

It doesn’t really matter. I have (always?) a microSD-Card with PiMusicBox installed in stock. So I gave it a second try. I upgraded to tunigo 0.1.3 (and to requests 2.5.0 automatically). Then I didn’t reboot but switched off the power supply to the Pi. Power on again - waiting - wow: success.  
Now all is working fine. Many thanks for your help.

---

<div class="post-metadata">

**Author:** ![jodal](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/jodal/32/2564_2.png) [@jodal](https://discourse.mopidy.com/u/jodal)\
**Post date:** [February 19, 2026, 11:47am UTC](https://discourse.mopidy.com/t/no-entries-in-spotify-browse/387/8 "2026-02-19T11:47:53Z")

</div>