I see a blank plex server id in your account. Can you just try re-selecting the server and saving the settings so it sets it correctly?
Is it currently possible to push Trakt watchlist to Plex watchlist?
@yendi Please try the settings page now and it should respond a lot quicker when selecting your server. I was able to optimize the connection handling, so hopefully this allows you to configure your user and other settings properly. After doing that, please try running a manual sync.
The main issue seemed to be there were no libraries selected to sync, so even when the sync did work it wouldn’t pull any data. With the improved settings and being able to save the settings properly, that will hopefully fix that issue too.
Unfortunately no. From my research, there doesn’t seem to be Plex APIs to get or send data to the Plex watchlist.
Yeah, i got real frustrated and deselected the server until I heard from you, save using unnecessary resource’s.
I’ve gone ahead and selected the TV server, seeing as nothing at all has ever synced from server yet.
All the usually port configuration set and can be seen
Thanks again, Justin 
I’m curious how PlexTraktSync is able to do this then.
1 Like
Good call! I was actually able to make some progress using the Python PlexAPI package. It appears there is another Plex web service that allows me to get the watchlist info. It appears watchlist sync might be possible after all 
3 Likes
Thanks, solved the issue !
My main issue with PlexTraktSync is that you have to have one watchlist as “Master”, as a 2 way sync seems to mess things up. So currently I add stuff to my Trakt watchlist and let plextraktsync update my Plex watchlist. If you manage to get a 2 way sync working properly, that would make things a lot easier.
1 Like
I have the same problem. Everything is setup and selected, but nothing ever sync’s. If I shutdown my Plex Server for period, I get an email to reconnect so it works at some level, just never sync’s.
Note: I don’t have 2 way sync working yet, so the below answers are just what I plan to do if possible.
No, I’d consider Trakt as the source of truth and mark it watched on Plex.
It would be marked as watched on Trakt.
1 Like
Awesome! Yes, the best approach for me currently is to use PlexTraktSync like @WilhelmStroker does - to push from my Trakt watchlist to my Plex watchlist, since I’m always browsing Trakt. I would just prefer to use Trakt exclusively and move away from scripts like PlexTraktSync. Thanks again!
1 Like
Also Justin, this is exactly how I use PlexTraktSync as well. You should be able to deconstruct how that API works to do these things. Looking forward to the implementation!
PlexTraktSync is a really awesome project. My goal is to replicate most if not all of that functionality natively with the Plex Sync feature. As long as there are public APIs (on Plex or directly on your media center) then it should be possible.
3 Likes
Awesome feature, really love it and saves a ton of time!
One feedback from my side would be the ability to lower the frequency of sync events. I’d be happy syncing once per day or even just once per week.
The hourly syncs are hammering my array needlessly 
I don’t believe/think it’s requesting an entire scan of your server every hour, rather it’s reading data from a text file after a Metadata refresh, hence why we are asked to do a Meta refresh after enabling, though I could be wrong. 
Personally the once an hour or longer delay is something I find annoying compared to the Webhook feature. Once older items have been imported going forward it should be instantaneous just like the webhook. If not there’s no point tbh when there’s other platforms or self-hosting options that can and do provide that.
When you say hammering, do you have more specifics? Trakt saves the timestamp of the last sync, so it should only be asking your server for items greater then that timestamp. We might consider making the frequency a user setting.
I want to look into using the webhook to queue up the piex sync more quickly. A self hosted app on your local network is likely holding a more consistant connection or not adding any overhead since it’s all internal to your network. Since Trakt is external, we can’t do it quite the same way.
This is where I get confused with your vision for the future with this.
One of the perks and probably one many used as a motivator to become VIPs here was to use the existing webhook which generally works fine in 99% of the cases.
Its limitations and issues are known: new series added to a collection, or many added at the same time can cause a failure.
Yet, explain to me why the progression you envision going forward with a limited or delayed update to what’s being scrobbled or added is in fact not going to be as efficient. What’s the advantage to us as paying / supporting users?
Wouldn’t a better path be to create your own fork of PlexTraktSync to assist users wanting to import their prior history, viewings, collected items etc while leaving the webhook completely untouched to update plays and collections going forward.
It really seems to me reading between the lines that you’re trying to do away with the existing webhook. Something I don’t think is right at all.
And because it’s not being said in the vein of trying to suggest people look elsewhere, but in addition to PlexTraktSync, maybe there’s some use in you reviewing Yamtrack and even retired utilities like Plaxt. Maybe there’s some ideas you could harvest from there to keep things at least status quo. Rather than what is definitely perceived by me as a regression with the inability of Plex Sync to handle multiple servers and non-standard ports like I’ve raised before in addition to the very much delayed updating of plays and next to be watched.
1 Like