Spotify Sources need redefining after 0.3.3 upgrade

Troubleshooting
1

Just leaving my recent experience.

After a long time I upgraded to the latest 0.3.3. (previously 0.1.9, so yeah…)

The upgrade went fine indeed, but left my existing spotify-sources not useable.
(not showing up or unable to effectively connect depending on the device trying)

The quick hack out of this was to just drop them and recreate – all is well now.
Just checking the export-config of both situations, and maybe that could be a clue towards what is causing this?

old config for spotify:

219     {
220       "id": 1003,
221       "name": "K79#M Spot",
222       "type": "spotify",
223       "user": null,
224       "password": null,
225       "station": null,
226       "url": null,
227       "logo": null,
228       "freq": null,
229       "client_id": null,
230       "token": null
231     },

new config:

243         {
244             "id": 1010,
245             "name": "K79 Spot M",
246             "type": "spotify",
247             "disabled": false
248         },

Only drawback is that ids have changed and I need to fix some of my presets but that is all doable.

Maybe this entry can:

  • help somebody else
  • influence a future upgrade procedure to fix or similarly re-create those channels during upgrade.
2

Thanks for the report, this is really useful since I don’t think we’ve ever seen a stream config serialize with null fields like that before. I wonder what could have caused this?

3

sorry for my late reply, was just enjoying my own fix

as for your remaining question:

I am guessing the output I dumped was actually as it was produced by the python cli package a loong time ago – so it might just be caused be how pydantic and / or specific json serialisation in that package is producing that output?

So nothing to worry about in core amplipi stack IMHO