pymedusa / Medusa

Automatic Video Library Manager for TV Shows. It watches for new episodes of your favorite shows, and when they are posted it does its magic.
https://pymedusa.com
GNU General Public License v3.0
1.77k stars 275 forks source link

Jackett integration - search not working #10427

Open brainstormi opened 2 years ago

brainstormi commented 2 years ago

Hi... When launched a manual search from Medusa using Jackett as service provider (Torznab) no results are given although manual search in Jackett works properly. The same search executed from Sonarr works properly, the only difference in the http request launched is that Sonarr pass as query URL parameter: q=SerieName&season=1&ep=1 Meanswhile Medusa for the same query: q=SerieName+S01E01 Modifying the Medusa query for using the same query format than Sonarr works properly with Jackett. Also it works if Season and Episode reference is passed in the URL with '&' instead of '+' symbol. Example that works too: q=SerieName&S01E01 Regards,

brainstormi commented 2 years ago

The last format q='SerieName&S01E01' is not totally correct, because search outputs all the episidos for that serie instead only the one searched. It seems than the only correct format that Jackett accepts when using Torznab is writing explicitly season an episode numbers: q=SerieName&season=1&ep=1

brainstormi commented 2 years ago

I already tested creating a Newznab for Jackett with the same outcome. Integrating Jackett in Medusa as Torrent RSS feed doesn't work at all, so I suppose that search with Jackett is not possible for now.

p0psicles commented 2 years ago

Is this a format that can safely be applied to all torznab providers. Does this also works with prowlarr? Btw we recommend the usage of prowlarr above jackett.

brainstormi commented 2 years ago

Not sure how the rest of the ZNAB providers should work, but Sonarr does it in the same way than Jackett for these kind of providers. Unfortunately prowlarr is not an option due to the lack of indexers in my language.

brainstormi commented 2 years ago

I tried to setup prowlarr, creating a generic torznab provider pointing to jacket one. Unfortunately when doing a search from Medusa, prowler doesn't process the query received and it simply forwards it to Jackett, so no working neither.

p0psicles commented 2 years ago

The issue here is that medusa doesn't have a specific type provider for jackett or prowlarr. It uses the newznab and torznab specs. So any change I make here to Torznab, would then change the search queries towards jackett and prowlarr.

I'll inquire with sonarr and radarr guys, to see if this is the prefered search query format.

p0psicles commented 2 years ago

@brainstormi you said the only difference is this: q=SerieName&season=1&ep=1. But if i'm going through the docs this is part of the t=tvsearch api. Opposed to the t=search api, we use by default. https://newznab.readthedocs.io/en/latest/misc/api/#tv-search

brainstormi commented 2 years ago

@p0psicles When I said "the only difference", I mean comparing the query Sonarr launched against Jackett vs what Medusa does. As said not sure which is the correct one and if any of them adheres to API guidelines, but Sonarr "way" works for me. Maybe the issue it's not only API related and could be around the indexer implementation too, in this case Dontorrent indexer was used from Jackett side. But in my experience, that could be limited, Sonarr query format seems to be more compatible across diferent providers in Jackett.

rafi-d commented 2 years ago

@brainstormi : The search with Jacket is working here fine... What is the exact/full URL you are using for your Jackett as "provider" ?

BTW, I am not able to edit/change the URL and some other edit fields, so I needed to add and remove the whole provider, @p0psicles - can this be fixed [added to #10549]?

p0psicles commented 2 years ago

Newznab and torznab works with capabilities. So a torznab could show the capability of being able to handle the tvsearch API. And in that case we could use that in stead of the search API. I'll take a look at that.

p0psicles commented 2 years ago

@rafi-d yes you'll have to remove and add

rafi-d commented 2 years ago

@p0psicles why? The "key" field seems to be editable, so the rest should be too...

p0psicles commented 2 years ago

@brainstormi i've been looking into this. But i really need to know which provider your testing this with?

brainstormi commented 2 years ago

@brainstormi i've been looking into this. But i really need to know which provider your testing this with? I was using Dontorrent indexer, configured as torznab provider with the URL string given by Jackett.

Urkov commented 1 year ago

@brainstormi i've been looking into this. But i really need to know which provider your testing this with? I was using Dontorrent indexer, configured as torznab provider with the URL string given by Jackett.

I have the same problem with dontorrent and mejortorrent. If we would have spanish trackers in prowlarr maybe it will not be a problem to change but not our choice. Any solution to this?

p0psicles commented 1 year ago

Have you tried requesting it at prowlarr?

Urkov commented 1 year ago

Have you tried requesting it at prowlarr?

How can I do it? You mean connect jackett with prowlarr and viceversa?

p0psicles commented 1 year ago

No i mean. Have you asked the prowlarr devs to add the provider/indexer you need?

Urkov commented 1 year ago

No, but i will do it. Thanks