-
|
I updated Crosswatch to version 0.2.2 and enabled watch history synchronization from Plex to Trakt. In the View Details section, slightly different numbers are also displayed. |
Beta Was this translation helpful? Give feedback.
Answered by
verdel
Oct 13, 2025
Replies: 15 comments 13 replies
-
|
I don’t think this is a Statistics issue as v0.2.2 largely addressed that (still a bit buggy, but usable). What stands out is your Plex snapshot: only has ~30 items.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I can provide any debugging information if needed, including responses to any REST requests made to Plex or Trakt. The Trakt history wasn’t empty before synchronization. I had marked items as watched either manually or through PlexTraktSync before I started using CrossWatch. Also, CrossWatch had already been running in Scrobbler mode for some time, since the History Synchronization option was disabled in previous versions. As for the Authentication Providers settings, here they are: Plex Trakt Also, in the Main section, the status of both Plex and Trakt is shown as connected: |
Beta Was this translation helpful? Give feedback.
0 replies
-
Before you start (important)
debug
other stuff you can try
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I updated CrossWatch to version 0.2.3 and disabled Watcher. I enabled the Debug option (including MOD Debug) in the CrossWatch settings and started the synchronization. And here’s the output from the Docker container logs: Here’s the Sync Output after performing Clear State and Clear Statistics. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I haven’t tested on NVIDIA Shield yet, so behavior might differ. Right now the Plex API only hands back ~40 items, so that’s all we read. I just released 0.2.4 - grab it. There’s a tiny Plex History patch in there, but it probably won’t fix this specific case. Do this: Run the sync again. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I updated to version 0.2.4, performed a Reset State and Reset Statistics. Unfortunately, the result is still the same. Maybe I can make a REST request to Plex similar to the one CrossWatch uses to fetch the watch history and attach the result here? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Yes,
replace with the account token as shown in your /config/config.json for example http://192.168.1.1:32400/status/sessions/history/all?X-Plex-Token=LeJDeNxeSXxj_11fSU- Look at the first line: MediaContainer size="xxxx"
|
Beta Was this translation helpful? Give feedback.
-
|
I completely deleted the CrossWatch data directory, reconfigured the Authentication Providers, and didn’t select anything in the Plex Whitelist Libraries. If I run a curl request using the Plex token that’s currently configured in CrossWatch, I get 767 items in the Plex History: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The only thing i can think of is that you have history items with different ID's. We are filtering index on account_ID (and 1 is owner) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I don’t have any additional accounts with access to Plex. Maybe I can enable additional debug output in CrossWatch to understand why it only sees 40 items, or modify the code inside the container, or build a separate docker image with such debug mode? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Regarding additional debugging. We use the open-source PlexAPI to talk to your Plex Media Server. It handles auth, requests, pagination, and models. We just call it for history, ratings, and lookups. As you can understand, i really dont want to debug PlexAPI itself. Perhaps your NVIDIA Shield might behave a bit differently. I’ve forced PlexAPI to keep paging until it hits the result cap. Let me know if you see any difference when syncing. |
Beta Was this translation helpful? Give feedback.
-
|
I found the problem. Most of the time, after watching something, I delete items from my libraries, so in the response to the I apologize for wasting your time. It turns out that in my particular case, syncing history outside of |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
That makes sense. I might add a fallback to Plex’s Discovery service later, but for now the items must exist so we can fetch the GUIDs, without them we can’t match reliably. Glad you got it sorted. No worries; I mainly needed to confirm it wasn’t NVIDIA-related. Thanks for the update. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, now I understand what the problem was — the absence of additional metadata (guid) after removing items from the libraries makes it impossible to synchronize with Trakt. Thank you very much for your work and this project. |
Beta Was this translation helpful? Give feedback.
Answer selected by
verdel
-
|
New option in version 0.2.5 that you can try. Read the WIKI cause it comes with a trade-off. To Enable:
what it does:
Or it might do nothing at all if Plex’s History doesn’t contain useful info, but it’s still worth a try. the risks:
|
Beta Was this translation helpful? Give feedback.
9 replies
-
|
It seems Plex recently phasing out .../hubs/search for Discover; some accounts/tokens now get 404 there, and other still work. I’ve switched the code to https://discover.provider.plex.tv/library/search and ive just updated /plex/_common.py You should now get something like this: |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it seems that now everything is working as it should. Although, I still have a few questions:
|
Beta Was this translation helpful? Give feedback.
-
|
No, apparently the search for TV show episodes isn’t quite working correctly. I still have some debug information about the value of this variable. It seems that for all episodes of a show from the watch history, the array adds an entry for the most recently watched episode. |
Beta Was this translation helpful? Give feedback.
-
|
oke, thanks for testing. I will pick it later this week. First need to finish the next release that includes new provider. So give me some time |
Beta Was this translation helpful? Give feedback.
-
|
Yes, this happens because of the function that generates the key for the fallback cache. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for debugging it. Our fallback cache key for episodes was “series-wide.” It didn’t include season/episode, so different episodes of the same show collapsed onto one key. Result: the cache kept handing back the last resolved episode for every entry. And besides that, one miss poisoned the whole show via the neg-cache. The key is now episode-specific. Changed _fb_key_from_row to build k2|ep|<show_id>|s|e (and only fall back to title/year if needed). No more collisions....at least, i hope. there is a new file in /plex/_common.py i did not test it myself.. sorry.. so hopefully you can do some small tests. regarding the numbers in insight. Thats a constant battle, i know the issue buts its rather time consuming to refactor the code as its too complicated at the moment. But its on my todo list, and with every new version i try to patch things. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Read below the v0.2.10 release notes. I've tested it with my Plex to Trakt and Plex to SIMKL and seems to work pretty good. Release notes v0.2.10
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I just tried version 0.2.10, and at first glance, everything seems to be working correctly. The entire Plex history is now synchronized. However, I noticed the following line in the logs: But I don’t see the Here is the full synchronization log: Thank you so much for your work — this is a really great feature that I was missing. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi, Enable it in config.json: "trakt": { |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found the problem. Most of the time, after watching something, I delete items from my libraries, so in the response to the
/status/sessions/history/allrequest, many entries don’t have thekeyandratingKeyattributes. It makes sense that they get filtered out here.I apologize for wasting your time. It turns out that in my particular case, syncing history outside of
Watchermode doesn’t make much sense.