Watchstate from all managed Plex users being pulled in instead of certain accounts... #295
-
Ideally, I'd pull in watched status from only locally managed accounts for my wife and I into watchstate. If I can only do a single account, that's fine I'll live with that. My main problem right now is that for a LONG time I could never pinpoint why randomly some things were getting marked as watched and I finally found out it was tied to managed users in Plex having their watch events get imported, I think through webhooks. I was looking at Plex play history today and saw that as managed users were watching things, at the top of the next hour it was marking those items as watched for my local admin account. I'm trying to figure out how to narrow this down to import for only a specific set of accounts. I can't figure it out in the docs alone, and here's what I've tried so far:
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi, Great questions, Let me try to answer them.
That's expected as we request new token using the provided admin token, as this token sometimes is temporary. nothing to worry about. as long as you get your data synced it doesn't matter which token shows in config.
This should not happen automatically, unless you actually enabled webhooks and forgot to set match user, plex way of doing webhook's is kinda not ideal as they used the endpoint for all users regardless as such if match user is off, it's expected that the event be recorded. What you should is start clean add your plex backend, make sure to enable both match user id and backend id, add the webhook endpoint to your plex server, and observe the logs if it's says the user id incorrect or backend id is incorrect, it should also tell you what value was provided by the user you can then change it to match your user. Plex way of doing webhook's is really unhelpful and sometimes downright wrong, user id changing depending on having managed users or not is not something that i can account for =) Anyway, Enable both options i listed and check the logs and link them if you cant proceed further. |
Beta Was this translation helpful? Give feedback.
Hi,
Great questions, Let me try to answer them.
That's expected as we request new token using the provided admin token, as this token sometimes is temporary. nothing to worry about. as long as you get your data synced it doesn't matter which token shows in config.
This should not happen automatically, unless you actually enabled webhooks and forgot to set match user, p…