search

jumaka / triodeplugins

Automatically exported from code.google.com/p/triodeplugins
0 stars 1 forks source link

Trouble using CLI/JSON-RPC with Spotify Premium 2.2.2 #6

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.
Issue CLI command for spotify subitem:
00:04:20:16:0f:2d spotify items 0 100 item_id:1.3
or
00:04:20:16:0f:2d spotify items 0 100 item_id:2.0

What is the expected output? What do you see instead?
Expect to see results for that query, but instead either get no results or 
results for the item_id:1.1.

What version of the product are you using? On what operating system?
LMS 7.7.1, Spotify Premium Plugin 2.2.2, Linux-x86

Please provide any additional information below.
Suspect it may have to do with json-rpc/cli use instead of cometd protocol.  
Same queries seem to be working fine from iPeng which uses cometd.

Original issue reported on code.google.com by tbsan...@gmail.com on 6 Jan 2012 at 4:03

GoogleCodeExporter commented 8 years ago 
I have had Spotify and Squeezebox Duet about half year and current versions are 
Spotify 2.2.2 and Duet 7.7.1 r9557. I haven't been using these for few months 
but now when I tried it again it doesn't seem to work. After playing with 
installations for a while I noticed, that the problem was with first Spotify 
login from Duet. When adding username and password for Spotify in logitech 
media server web page it has following status

Helper App: Running
Current logged in to Spotify
Login Error: No error
Last Error: No error

However, after trying to open Spotify music track (I get in Spotify but when 
trying to get tracks it fails) in Duet remote control I get following error.

malformed JSON string neither array, object, number, string or atom at 
character offset 207(before"(end of string)") at 
var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotify/ParseBase.pm 
line 89

After that media server web page has status 

Helper App: Running

I'm not sure if this relates to the problem you have described above but I 
ended up here searching JSON and spotify. Any help would be appreciated. This 
seems funny as it worked earlier (about 2 months ago) so maybe it has something 
to do with version updates? However, I would assume that someone would have 
noticed it already?

Original comment by axhei...@cs.helsinki.fi on 1 Feb 2012 at 7:54