Jump to content

emby next gen and the json rpc api -----> problems over problems


Pimp1310

Recommended Posts

Pimp1310

hello,

 

i tried to request over the json api of kodi to get the fanart of a current playing media.

according to kodi rpc wiki the answer to the request should look like this

 

"tvshow.fanart": "image://nfs%3a%2f%2fCUBER%2fmedia%2fpreserved%2fTVShows%2fV%20(2009)%2ffanart.jpg/",

 

this is what i get with EXACT the same request


 

"tvshow.fanart": "image://http%3a%2f%2f127.0.0.1%3a57578%2f44706%2fImages%2fBackdrop%2f0%3fEnableImageEnhancers%3dTrue%26Tag%3d7273c77065e8d1761f9d9aae042e67e6/",

 

 

 

how can I access the fanart? I've been trying for hours

 

Thank You

 

 

 

Link to comment
Share on other sites

quickmic

The example with NFS is native mode.

the http is addon mode.

"image://http%3a%2f%2f127.0.0.1%3a57578%2f44706%2fImages%2fBackdrop%2f0%3fEnableImageEnhancers%3dTrue%26Tag%3d7273c77065e8d1761f9d9aae042e67e6/",

seems correct.

Here is an example from my Kodi DB:

http://127.0.0.1:57578/944665/Images/Backdrop/0?EnableImageEnhancers=True&Tag=d7b780f0ed288afcf1767b4ac5a28718

 

So decode %3a%2f%2f = "://" etc. and it should work. As a test, drop the actual (decoded link) into a browser WHEN Kodi is RUNNING

Edited by quickmic
Link to comment
Share on other sites

Pimp1310
17 minutes ago, quickmic said:

The example with NFS is native mode.

the http is addon mode.



"image://http%3a%2f%2f127.0.0.1%3a57578%2f44706%2fImages%2fBackdrop%2f0%3fEnableImageEnhancers%3dTrue%26Tag%3d7273c77065e8d1761f9d9aae042e67e6/",

seems correct.

Here is an example from my Kodi DB:



http://127.0.0.1:57578/944665/Images/Backdrop/0?EnableImageEnhancers=True&Tag=d7b780f0ed288afcf1767b4ac5a28718

 

So decode %3a%2f%2f = "://" etc. and it should work. As a test, drop the actual (decoded link) into a browser WHEN Kodi is RUNNING

i tried everything

 

my kodi IP = 192.168.0.164:8023

 

i tried 

 

http://192.168.0.164%3a57578%2f44706%2fImages%2fBackdrop%2f0%3fEnableImageEnhancers%3dTrue%26Tag%3d7273c77065e8d1761f9d9aae042e67e6/

or

http://192.168.0.164%3a8023%2f44706%2fImages%2fBackdrop%2f0%3fEnableImageEnhancers%3dTrue%26Tag%3d7273c77065e8d1761f9d9aae042e67e6/

or

 

http://192.168.0.164:57578/44712/Images/Backdrop/0?EnableImageEnhancers=True&Tag=a1bb61a46530de76b18b8b9e544f14b1

 

or

 

http://192.168.0.164:8023/44712/Images/Backdrop/0?EnableImageEnhancers=True&Tag=a1bb61a46530de76b18b8b9e544f14b1

but nothing

 

 

 

Edited by Pimp1310
Link to comment
Share on other sites

quickmic

Don't use 192.168.0.164

Use 127.0.0.1. It's piped threw a socket, that's why kodi must be started.

Link to comment
Share on other sites

quickmic

And decode ALL data. :// was just an example.

It should look like:

http://127.0.0.1:57578/44706/Images/Backdrop/0?EnableImageEnhancers=True&Tag=7273c77065e8d1761f9d9aae042e67e6

I hope I decode it correctly (manually)

 

Link to comment
Share on other sites

Pimp1310
2 minutes ago, quickmic said:

Don't use 192.168.0.164

Use 127.0.0.1. It's piped threw a socket, that's why kodi must be started.

 

okay, i tried

 

http://127.0.0.1:57578/44712/Images/Backdrop/0?EnableImageEnhancers=True&Tag=a1bb61a46530de76b18b8b9e544f14b1/

or

http://127.0.0.1:8023/44712/Images/Backdrop/0?EnableImageEnhancers=True&Tag=a1bb61a46530de76b18b8b9e544f14b1/

 

in my browser, kodi is running, but i get a "website is not reachable"

Link to comment
Share on other sites

quickmic

both are wrong.

Second is wrong port 8023

first is almost correct, but remove the "/" at the tail.

http://127.0.0.1:57578/44712/Images/Backdrop/0?EnableImageEnhancers=True&Tag=a1bb61a46530de76b18b8b9e544f14b1

 

 

Link to comment
Share on other sites

Pimp1310
1 minute ago, quickmic said:

here is the unconverted fanart url

 

image://http%3a%2f%2f127.0.0.1%3a57578%2f44712%2fImages%2fBackdrop%2f0%3fEnableImageEnhancers%3dTrue%26Tag%3da1bb61a46530de76b18b8b9e544f14b1/

and here my urldecoded

 

http://127.0.0.1:57578/44712/Images/Backdrop/0?EnableImageEnhancers=True&Tag=a1bb61a46530de76b18b8b9e544f14b1

 

 

but NO luck, the browser shows always a error

Link to comment
Share on other sites

Pimp1310
3 minutes ago, quickmic said:

Kodi running with installed emby-for kodi-next-gen plugin and connected?

of course, and i play a file.

 

 

Unbenannt.jpg

Edited by Pimp1310
Link to comment
Share on other sites

quickmic

hmm, than I don't know, sorry. It should work and works for me.

You can install sqlite browser, open the kodi myvideo.db (art) and read the actual links from there. Maybe you find the issue.

Edited by quickmic
Link to comment
Share on other sites

Pimp1310
3 minutes ago, quickmic said:

hmm, than I don't know, sorry. It should work and works for me.

You can install sqlite browser, open the kodi myvideo.db (art) and read the actual links from there. Maybe you find the issue.

This can not be....
I've been busy here for hours

do you also have kodi 19?
Link to comment
Share on other sites

quickmic

btw, I dropped: http://127.0.0.1:57578/944665/Images/Backdrop/0?EnableImageEnhancers=True&Tag=d7b780f0ed288afcf1767b4ac5a28718

It's just redirected to 192.168.0.207 and manually masked my token

Edited by quickmic
Link to comment
Share on other sites

Pimp1310
11 minutes ago, quickmic said:

btw, I dropped: http://127.0.0.1:57578/944665/Images/Backdrop/0?EnableImageEnhancers=True&Tag=d7b780f0ed288afcf1767b4ac5a28718

It's just redirected to 192.168.0.207 and manually masked my token

why in your adress is "emby"?

 

 

the path

http://127.0.0.1:57578/20497/Images/Backdrop/0?EnableImageEnhancers=True&Tag=4e139f02e3dd7ff5f84a48b922c020ff

 

 

and my browser

 

 

Unbenannt.jpg

Unb2enannt.jpg

Link to comment
Share on other sites

quickmic
Quote

why in your adress is "emby"?

Not sure I understand you questions. That's the Emby-server API.

 

Link to comment
Share on other sites

quickmic

127.0.0.1:57578 calls the Emby-next-gen socket which redirects to the actual Emby server URL and adds api keys etc.

Edited by quickmic
Link to comment
Share on other sites

Pimp1310
1 minute ago, quickmic said:

Not sure I understand you questions. That's the Emby-server API.

 

look at my path, my path is on kodi. your path on emby.

 

Just now, quickmic said:

127.0.0.1:57578 call the Emby-next-gen socket which redirects to the actual Emby server URL and adds api keys etc.

when i call 127.0.ß.1:57578, i get a no website reachable

Link to comment
Share on other sites

quickmic

Do you query that URL from the same device Kodi is running? Otherwise it cannot work.

If you use Windows desktop/laptop, install Kodi there with emby plugin.

 

 

Link to comment
Share on other sites

Pimp1310
1 minute ago, quickmic said:

Do you query that URL from the same device Kodi is running? Otherwise it cannot work.

If you use Windows desktop/laptop, install Kodi there with emby plugin.

 

 

no of course not.

kodi runs on my shield, emby on my server.

But it must be possible to open it from outside or from my windows pc or server, that's the point. that's why there is the Json RPC to access information from other devices
Link to comment
Share on other sites

quickmic

ok, then use the pattern of my (native) link, adapt it and try. Probably you need your API-Key/token, and NO it cannot help you with that. It's unique. Probably grab it from the Emby server UI when you play a video.

btw, I'm afk now,

based in Europe, and must work tomorrow 😉

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...