Duplicates - "Adding to collection" and "marking as watched" #996
Comments
|
Your It is recommended to organize/name episodes files in folders according to tmdb order. Anyway, sometimes tvdb order is the only solution so I wrote this fix : You can try it. |
|
That will fix the duplicate "marked as watched" specifically? Id assume plextrakt would have recorded once it found the correct episode and added it to trakt/marked it as watched so that it didn't do it again. Edit: If this would solve the duplicate watches, where are the files in your PR located in the docker image for me to edit? I usually just pull. I haven't built a container myself before. |
yes
in |
|
Which version of plextraktsync should i apply your PR to? I applied it to the newest version and i get massive errors. Edit2: Seems to be working as far as syncs. I'll check and see if I get any duplicate watches recorded. Thanks! |
|
If it's working i'd be happy to see your logs. Warnings should disappear. |
|
I do have a lot of warnings still, but a lot of it seems to be s00e (specials). I'll give you a link to the logs once it's finished I'm also doing a mass "refresh all metadata" in plex since I haven't done it in many years. I'm guessing it may add some pointers for the script to refer to? I have a large collection, so this may take a bit. With the original script, it took about 2 hours to complete. I assume subsequent runs with this script may be faster since it doesn't have to keep rechecking the episodes it's already done? |
Good, did you switch to the new agent |
Yup, All of my TV libraries have been using Plex TV Series for a while now, but I probably didn't refresh all metadata after doing that which means there's a lot of old lingering shows.
Awesome. Thanks! |
|
I can confirm your PR prevents the additional watches from getting sent over to trakt. Hopefully it gets merged soon :) Looking over some warnings, i'm not sure why dbz kai isn't being found |
|
Some shows are split in different shows on tmdb (example: Whose line is it anyway tmdb vs tvdb) and Trakt often uses tmdb as source (sometimes tvdb). What you can do if some data is missing :
About About
Tvdb has all seasons (1986 to 2019) grouped in one show. And so on with other shows in you logs,... TL;DR recommended practice : use |
|
Does tmdb have a policy against tv specials or does it not know how to handle season 0? It doesn't seem to catch any of those. |
|
Seasons 0 are often a mess because not really official. Example with season 0 of |
Confirmation
The problem
It appears to happen with a lot of larger anime series, I'm seeing repeated messages in the log about the below image
When I check the entry on trakt, there's thousands of plays logged. It appears that with every sync, there's a new watch synced over.
Error trace / logs
Expected behavior
Only 1 instance of adding to collection or marking as watched
Steps to reproduce the behavior
Inspect of problematic items
No response
Workarounds
No response
Install method
docker-compose
Version
0.20.7
Python Version
not sure
Operating System and Version
debian
The text was updated successfully, but these errors were encountered: