-
-
Notifications
You must be signed in to change notification settings - Fork 977
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sonarr and Radarr both say 0 wanted #43
Comments
Alright, I'll take a look. What versions of Sonarr and Radarr are you running, and is there anything special or otherwise non-standard with your installs? |
Radarr: 4.1.0.6175 Nothing unusual about the install, just bare metal debian |
Radarr uses the Sonarr uses the I'm not sure what could be the issue, other than some custom availability rules or other such thing. I'm running nearly the same versions of both as you are. |
If I go to api/v3/wanted/missing on sonarr it says
|
It says I have 178 movies but I actually have 150 and 28 wanted so it seems to be combining wanted into total movies |
Fixed movies count in e72efe7. If you can go to |
I actually think Sonarr has none missing as all the shows are current ones so the episodes aren't released |
So it seems it's including wanted movies in "movies" count and not wanted in wanted. I have 172 total which includes wanted but it should show 26 for wanted and 146 under "movies" |
The check is simply done on the I'm not sure what could cause the differences you're seeing, but this is all of the information I get from the API for building the stats. |
I am having this issue but only in Radarr. Sonarr is working correctly. I am using Radarr v4.1.0.6175 |
Same here issue only on radarr. Version |
Same as C8opmBM here as well. Version |
Can you try again on the latest release? Ben and I did some work to both clean this up as well as improve performance. |
Mine still say 0 wanted |
Forgot to mention, it seems on sonarr v4 also there's a bug as well. |
Just to make sure we can narrow this down, which version of which software is presenting display issues:
Sonarr:
|
In my case: Sonarr v3 works ok (3.0.9.1549) Radarr v4 NOT ok (4.1.0.6175) - I don't use radarr v3, since v4 is in the :latest tag. |
For me v3 and v4 of Sonarr seems to work fine.
I only use v4 of Radarr (same reason) which does not work.
…On Mon, 19 Sept 2022, 16:05 C8opmBM, ***@***.***> wrote:
In my case:
Sonarr v3 works ok (3.0.9.1549)
Sonarr v4 NOT ok (4.0.0.115)
Radarr v4 NOT ok (4.1.0.6175) - I don't use radarr v3, since v4 is in the
:latest tag.
—
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMYW2ZNDAME6YYSW7T3MTV7B6NLANCNFSM577GDUDQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I'm on Radarr 4.1.0.6175 Sonarr 3.0.9.1555 And both say 0 wanted |
I think it says "Queued" while downloading. Wanted is for missing. |
Well yeah, the whole point of this issue is that it doesn't show wanted. And I'm saying it shows wanted when it's downloading something which is obviously not meant to happen |
Well, the values being shown are the values given back from Sonarr and Radarr. The wanted count, comes from the endpoint |
This is still happening |
I’m on version 4.1.0.6175 of radarr and version 3.0.9.1555 of sonarr
Nothing unusual about the install, just bare metal Debian no docker or any virtualisation
…On 30 Aug 2022, 04:34 +0100, Ben Phelps ***@***.***>, wrote:
Alright, I'll take a look. What versions of Sonarr and Radarr are you running, and is there anything special or otherwise non-standard with your installs?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
There isn't anything that we can do about this, these are the values given directly from the Sonarr and Radarr APIs. If you think the values are incorrect, you need to open an issue with the Sonarr and Radarr projects. |
For Sonarr: We use the We use the For Radarr: We use the We use the |
Sonarr for me seems to work, so I am just interested in Radarr. You are using the I'm therefore confused. From the sounds of it, the way you are counting the missing movies would seem to work, but the value of 0 is wrong and I don't understand how it is getting 0. |
For radarr, @benphelps, I think you are misinterpreting the value "isAvailable: false"... It mean it's not in local Radarr library and not yet available, it simply mean it is not available at all, it's a futur movie not available period. So counting "isAvailable: false" will result in a partial Wanted/Missing totalRecords... You should count "sizeOnDisk": 0 to determined Wanted/Missing movies in a local Radarr Library. |
I have mixted result. Depending on certain combination with "Min availability" and "Status", the movie will be "isAvailable: false" or "isAvailable: true"... Adding "Hancock 2" with min availability "Announced" status will be "Missing" and "isAvailable: true". For Radarr widget, Wanted should be counted with "sizeOnDisk = 0" and Have (Movies) counted with "sizeOnDisk > 0". Queued is working properly. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. |
There's 25 wanted for Radarr and less for Sonarr but both show 0
The text was updated successfully, but these errors were encountered: