Seerr and Tautulli Integration Issues #2898
Unanswered
Krissverse
asked this question in
Q&A
Replies: 1 comment
-
|
I would recommend creating a support ticket on our support channel (discord) for further troubleshooting. I don't personally use tautulli but it seems to be working for others that do. |
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
Uh oh!
There was an error while loading. Please reload this page.
-
Just to preface, I don't code anything and I have no idea what I'm talking about!
I'm trying to get Tautulli integration working and when it wasn't popping up properly, I went down a rabbit hole of AI prompts to try and diagnose every step along the way.
I checked all the settings, logs, and console results all the way down the chain to figure out where things are breaking and in the end, it concluded that there was a frontend rendering bug and generated the following report explaining what it found. This might be AI gibberish nonsense or it might point to an actual issue, but all I know is that I've gone through every setting I can think of and verified everything I can and it still isn't working!
Gemini Report
Description:
The frontend fails to display the Tautulli Watch Statistics panel on the right sidebar for media items, despite the backend successfully fetching and calculating the data perfectly.
When inspecting the network request for watch_data, the backend is returning the payload wrapped inside a parent "data": {} object. It appears the React frontend is expecting the payload at the root level, fails to find the playCount, assumes the total count is 0, and programmatically hides the UI panel.
Steps to Reproduce:
Successfully configure Plex and Tautulli settings.
Ensure Plex users are fully imported and mapped.
Navigate to a movie or show page that has verified watch history in Tautulli.
Observe that the right sidebar is missing the Watch Statistics panel.
Inspect the watch_data network request in browser DevTools and observe the {"data": { ... }} wrapper.
Expected Behavior:
The frontend component should correctly parse the nested "data" payload (or the backend should strip the wrapper) so the Watch Statistics panel successfully renders on the media page.
Network Request Payload Example (watch_data):
If anyone has any ideas about where else I could look to fix the integration, I'd happily take a look or provide more information. As I said this Gemini diagnosis might be entirely nonsense but I fed it logs and screenshots every step of the way and checked a lot of things off the list. Tautulli is getting the API requests, IDs are matching for what it's requesting, and when I go to a movie/series with dev tools open I can see the response to watch_data is handing back an actual playcount for these things.
Let me know what else I can do to help figure this one out!
Beta Was this translation helpful? Give feedback.
All reactions