Feature request: check for duplicates before marking as watched #1847
Comments
rala72
changed the title
|
if entry is submitted by watch, then that's intended behavior to have rewatches recorded. if sync also submits a play that sounds like a bug. try runinng sync with |
|
based on logs it looks like
How can I disable it? Also wondering why I sometimes have multiple entries at the same (wrong) time of different episodes.
|
you have to ask their support then. |
|
I created an issue in their side.
I would assume, that the attempt to log the watch state fails. Can you please have a look at the |
|
I guess the duplicated entry of the second one comes from the sync threshold: like it passed the percentage (like 80%) of the episode and is counted as watched, even though it's still running. This is not necessarily wrong, but in my opinion the next sync should then check the previous created entries and check for created duplicates around the last entry. |
this is not true. while both plex and trakt.tv check this threshold, they don't mark things played when the threshold has passed. they also require scrobbling to be stopped. and this app doesn't mark played when you stop media in watch mode, it's trakt.tv that does it, it only sends stop play or pause play:
|
this is new info. can you provide full details of the error and preceding entries, and is there debug trace? enable debug logging first. any in any case, figure out what makes unwanted mark as played. enable debug logging and find related trakt.tv requests from the log. |
|
as for linuxserver-labs images, why not just use official image form this project? |
|
Good to know, then I'll enable DEBUG logging as you suggested and see what I get.
I used an older version once, but therefore it didn't keep running after the sync was done / didn't handle the cron job stuff itself, I stopped. I think I tried the new version yet with the scheduler once, but I wasn't able to get it to work yet. Edits: |
|
Log entry from similar error as above (excepert incl. surroundings): Regarding the duplicate entry... |
This comment was marked as spam.
This comment was marked as spam.
this might be your problem. this was fixed in #1882 |
|
Thank you for the notice, that there is a new version which fixed this issue. |
Is there any way to get around this? |
|
one issue one problem please. seems the original bug reported is solved. closing however, |
The original topic was a feature request, where I'm not sure if it has been implemented yet, but fine.
I don't think this is possible on my NAS, but I'll check it out later if there is any hacky way to do it. |
|
You requested check for duplicates (it won't be implemented like you ask), but apparently it was just a bug that 409 errors were retried and some of them actually succeeded: |
|
It's not possible to start it with a terminal in the UI and if I try it via shell it stops automatically as well. |
can't help you here, don't have any synology and you haven't shared any details either what you've done. did you even add volume to share the config files? no idea. |
Feature description
For recently watched episodes and movies check if Trakt has a entry already recently added (via scrobbler for example).
If yes, don't report it as watched to avoid duplicates.
Use case
I have the scrobbler and sync enabled for two way sync & as fall back.
But therefore both report an entry as watched, my history always has duplication.
Workarounds
Check the history regularly and delete an entry.
Have to figure out which is the correct one though if you care about it.
Plan to implement
Not yet. :(
The text was updated successfully, but these errors were encountered: