-
-
Notifications
You must be signed in to change notification settings - Fork 401
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
Plexrequest doesn't monitor Sonarr Episodes on the Sonarr develop branch #450
Comments
I have fixed the issue you are referring to in the dev branch. But the issue you have reported is with us not being able to work out the error that has come back from Sonarr. Can you change your Log level to Trace and then do the same thing and post the log? It should be something like "Api Content Response:" |
Wow fast reply :D, 2016/08/02 09:52:33.562 PlexRequests.Api.ApiRequest Trace: Api Content Response: |
Interesting. It seemed to work. I was expecting Sonarr to throw something up. I'll take a look at this a bit later (Currently at work). |
I was going through the Sonarr log file, and found it got a request but it didn't add to the list. Img of Sonarr log: https://gyazo.com/3bad4b698c435706b97ddb0e0bd2dbf2 |
Has it been physically added to Sonarr? |
It does not show up in the Sonarr list, there is also no map created. |
Wait, i'm not sure that log you sent me was correct, are you sure that was the Sonarr trace log? And that looks like a CouchPotato response to me. |
you were right, took the wrong trace response, here is de correct one: |
Ah found it. It's what I expected:
See this issue: #440 It's a Sonarr bug in one of their newer versions. I'm working on a workaround. |
@ShepherdDimaloun I have created a work around, would you like to try it? Here is the build: https://ci.appveyor.com/project/tidusjar/requestplex/build/1.8.680/artifacts |
I tested it, and it works, for auto and non auto. that was a really fast workaround! |
Excellent. Thanks! I suggest you change your logging level back to Debug (There seems to be a memory leak in the log provider we are using when using Tracing which I haven't got around to fixing yet). Regrading the workaround, I've added that into the dev branch ready for the next release so we don't have the issue there (Sonarr are also working on fixing this at their end). |
Will do, Works great now, added a few tv shows without any problem, there is only one thing. |
@ShepherdDimaloun The TV series and season selected should be monitored in Sonarr. I have raised a bug with the Sonarr guys as we are unable to actually add an unmonitored series (so currently everything added will be monitored), is this not what you are seeing in Sonarr? |
@tidusjar no, they are auto unmonitored, i have to change it manually. |
@ShepherdDimaloun what Sonarr version are you using? |
@tidusjar Version 2.0.0.4260 develop branch |
Ah ok that makes sense, they fixed the bug I reported, which has broken my part now. I need to update PlexRequests to work correctly now. I'll be working on this in a few hours. It's difficult to work with the develop branch when there are API changes as not everyone is on that branch. I usually suggest for you to run the master branch so that Plex Requests is 100% compatible. |
Will do, for now manually change it to monitored is ok. looking forward for the updates. |
Sorry about that. |
If this is a bug report please make sure you have filled the following in:
(If it's not a bug and a feature request then just remove the below)
Plex Requests.Net Version:
1.8.4
Operating System:
Windows Server 2012 R2
Mono Version:
Applicable Logs (from
/logs/
directory or the Admin page):Reproduction Steps:
I get this error when i do a TV show request, auto or non auto, both same error.
I have tried a fresh copy, but sadly that doesn't work either. CP works great, i have no problem with that!
This is my sonarr setup: https://gyazo.com/883fda1035a4b3ee12f6e9ebe532489f
The text was updated successfully, but these errors were encountered: