When manually searching for a missing episode, Sonarr now brings back other episodes for the same show.
For example, if I search for episode 3 of a show, I may get episode 1, 2 and 4.
I’m sure this has only started happening recently.
Im on the DEVELOP branch.
Same show or different show?
Different shows: Develop- Torznab searching
Sonarr shows whatever the indexer returns, need debug logs.
I was searching for SuperGirl 1x01, which technically hasn’t aired yet, but rather than just returning it, I was getting lots of other results returned:
As you can see, the episode was returned, along with the film from 1984 plus SmallVille.
In this case Sonarr searched by title, which your indexers returned various results for, this is the indexers fault, but Sonarr shows all results to you so you can pick the right one.
So doesn’t Sonarr give the indexers the episode name/number as well to search for ??
Just searched manually for Scorpions 2x04 and got the following returned:
Lots of episodes, but the latest is well down the list.
Does the Automatic search work in exactly the same way, but Sonarr picks the correct one ??
If so, why doesn’t it show only the relevant ones in the Manual search results ??
It seems to have started doing this since I added a Torrent client to Sonarr, but that could be pure coincidence.
Yes, but if you indexer chose to ignore that it would send back extraneous releases.
Yes, the same search method, then it chooses one.
It shows everything so you know what was returned and can pick the correct release.
Are all the wrong releases coming from torrent indexers?
No, NZB indexers as well.
I don’t have SMALLVILLE in Sonarr.
Do you want me to add it and test ??
Sorry, I meant Scorpion - used a release name instead of the modal title.
I’m having this same problem. I have 2 indexers (nzbndx and oznzb), one I have been using for over a year and the other for just a month or 2. They never had this problem before, but both started getting results showing up for other episodes when doing a manual search. It seems to have started happening after sonarr installed a recent update, but I’m not 100% sure if the timing is exact, I just know it was close to the time of the update (so that may be a red herring).
Here are some log files at the trace level when searching for Limitless s01e05 and
http://nobled.com/sonarr-logs/nzbdrone.txt
http://nobled.com/sonarr-logs/nzbdrone.0.txt
http://nobled.com/sonarr-logs/nzbdrone.1.txt
and here is a screenshot
As you can see here, your indexer is returning to much stuff.
15-10-20 21:08:26.3|Trace|HttpClient|Res: [GET] https://nzbndx.com/api?t=tvsearch&cat=5030,5040&extended=1&apikey=&offset=0&limit=100&q=Limitless&season=1&ep=5 : 200.OK (370 ms)
15-10-20 21:08:26.3|Trace|NewznabRssParser|Parsed: Limitless.S01E04.720p.HDTV.DD5.1.x264-NTb
Although your search string specifies “ep=5” it’s also giving you other episodes. Try tweaking the search URL manually to determine why this is happening.
The indexer is also indicating that they do support episode searching:
> <searching><search available="yes" supportedParams="q"/>
> <tv-search available="yes" supportedParams="q,rid,tvdbid,tvmazeid,season,ep"/>
> <movie-search available="no" supportedParams="q"/>Thanks for the help. I’ll talk to the indexers. Is there a config file I can edit to override the way it searches? Was there something in the way this works that changed recently in sonarr that could explain why this stopped working?
There are a couple issues here:
Your indexer doesn’t properly handle query + season/episode searches - I believe this issue was fixed some time ago, but it might depend how their service is setup.
TVRage went down, in response to that NN+ (Newznab) was updated to support additional parameters, which gives Sonarr a way to request which parameters the indexer supports for searching, if that request is handled by the indexer Sonarr could use (if supported) another ID to search (TVDB or TVMaze) and not rely on title searches which aren’t as reliable.
If q= isn’t the preferred option, why would Sonarr utilize that in the search. The indexer is also indicating that it supports other items, and the first line in the log is:
15-10-20 21:07:52.7|Trace|HttpClient|Res: [GET] https://nzbndx.com/api?t=tvsearch&cat=5030,5040&extended=1&apikey=&offset=0&limit=100&tvdbid=295743&tvmazeid=2473&season=1&ep=5 : 200.OK (5,670 ms)
Which are the correct tvmaze & tvdbid’s. Isn’t that returning any results ? (my free api calls are used up 
)
It then seems to fall back to q=:
15-10-20 21:08:26.0|Debug|Newznab|Downloading Feed https://nzbndx.com/api?t=tvsearch&cat=5030,5040&extended=1&apikey=&offset=0&limit=100&q=Limitless&season=1&ep=5
15-10-20 21:08:26.0|Trace|HttpClient|Req: [GET] https://nzbndx.com/api?t=tvsearch&cat=5030,5040&extended=1&apikey=&offset=0&limit=100&q=Limitless&season=1&ep=5
With nzbndx, it appears that if the show isn’t available on the indexer then I see a bunch of results for other episodes, but if the indexer has the episode then only it shows up. It also appears that searches with the q parameter ignore the season and episode parameters. Does sonarr fall back to using the q parameter if the tvdbid and tvmazeid search don’t find anything?
I chose another TV show (Experimental, episode 6) I was looking for and got similar results.
Sonarr log here.
Same as above, there are several indexers that do a standard query and one or more does not process the additional parameters correctly. As a result, results aren’t filtered on season & episode match.
So is this an indexer issue or a Sonarr issue, as I’m sure searches used to work correctly.
