-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
watch doesn't add to history anymore #758
Comments
anymore? what is the last version this worked then? what's the output of watch command? have you tried enabling debugging and see debug log of when play has stopped what appears to log? |
It just stopped working - not even sure if there was an update. I used version 0.8.14 before when the issue appeared (at least I think that was when it appeared - I don't check regularly and only noticed recently, but it did definitely work about 3 weeks ago). Updated to latest (0.18.15) to see if it might be fixed already I created one that only has the timeframe I basically skipped through an Item. The Play doesn't appear in Trakt history |
@player8472 revoke your trakt token. you have shared it publicly with debug log ( |
hmpf, overlooked that one - thx |
as you described scrobble stop is sent:
after that trakt.tv site should mark item as played. perhaps the trakt.tv sit was slow and it needed to update cache> there's also tons of json errors
but unclear, were those retried and then recovered? i've already submitted PR to trakt library to improve logging there: |
I can assure you it is not just slowness. It would be helpful to have the actual historyID the scobble sends back in the log, so I can check it. |
what is historyID? link? or perhaps send yourself PR with adding logger.debug? and describe how you would check it? |
that's logs from different project:
you could git blame there, maybe there's reasonable commit message explaining :D but I guess it's just debugging what headers are sent. I would drop it from there. or redact. EDIT: submitted a PR moogar0880/PyTrakt#195 |
https://trakt.docs.apiary.io/#reference/scrobble/stop According to the API the scobble-stop should return the 64Bit historyID it saved the scobble as in the trakt-db. I am not too sure how to check it, I'd research that if I had it (I really didn't use the API directly that much, so far ... ) |
I'm experiencing the same issue. I only installed 10 days ago and watch never worked whereas sync works just fine. |
Maybe instead of sending scobble->stop, sending scobble-pause (so it doesn't double add when trakt gets their sh** together at some point) + sync->add to history? Could be a workaround and should be more stable The call for add to history could also be used for #506 (although this bug wouldn't be half as bad if #506 was already implemented :) ) Here however, a simple call with watched_at set to the present system-time should suffice. |
History Id is added to debug log if you take changes of this branch and apply changes to trakt library (linked in the pr): |
Encountering this myself too now. So far no errors. looks like trakt.tv side something changed?
I don't read anything new from docs: |
managed to capture response (details on how: #758 (comment)):
so, somewhy action=pause and progress=0.0 in response. that's not expected. |
got message where it worked, with this branch applied:
|
The problem
When watching something on plex, it scobbles progress fine - but at the end it doesn't mark it as completed in Trakt-History
Error trace
No response
Expected behavior
Watched Episodes/Movies should be marked as watched in Trakt-History.
Steps to reproduce the behavior
Watch something on connected PLEX-instance
Inspect of problematic items
No response
Workarounds
Using Sync, but that only works if Item hasn't been watched before.
Install method
docker-compose
Version
0.18.15
Python Version
3.10.0 (according to docker inspect)
Operating System and Version
Fedora 35 (Containers Host)
The text was updated successfully, but these errors were encountered: