Should this be 2 separate issues?

The TMDB param is a no brainer; the comments is more complex so best as its own issue

I've been looking at requests that sonarr sends to Prowlarr and onto bitmagnet. i.e. tv-search

If capabilities specify tmdbid,imdbid sonarr will send a request parameter with imdbid=12345 when searching.

Looking at my database, there is no data to support this. imdb ID only exists against movies, not a single tv show.

select content_type, content_source, source, key, count(*) 
from content_attributes
group by content_type, content_source, source, key
order by content_type, content_source, source, key
limit 100

Hence sonarr then sends multiple additional search requests with q parameter set. Then this uses FTS.

I have trialed with a version that states q,tmdbid,season,ep as capabilities. In this case sonarr is not setting tmdbid request parameter. Will raise something on sonarr forums and dig through code base. It is clearly reacting to capabilities but not in way I would expect. Prowlarr code base looks to be correct.

I have trialed with a version that states q,tmdbid,season,ep as capabilities. In this case sonarr is not setting tmdbid request parameter. Will raise something on sonarr forums and dig through code base. It is clearly reacting to capabilities but not in way I would expect. Prowlarr code base looks to be correct.

Have confirmed this is a bug in prowlarr that should be fixed in todays nightly build (29-jan-2025)