Trakt in conjunction with Kodi/"Up Next" problem

[Pankookis 10]

Hi.

 

I've had a problem for a while that several episodes doesn't scrobble to Trakt. I use Kodi to watch my media.

 

I believe I have found what cause this problem. When the addon Up Next start the next episode it doesn't report the episode as stopped, it just starts the next one.

 

Usually you see a "Info Trakt: Playback Stopped" in the Emby logs. If Up Next start the next episode, it just moves on to "Info Trakt: Playback Started". Took a snippet out of my log that showcase this.

 

Can this be solved or is it just the nature of how the addon play the next episode?

 

Thanks

 

 

Untitled.txt

Edited June 3, 2020 by Pankookis

[Luke 39294]

Hi there, does the server activity viewer on the server dashboard say that it stopped?

[Pankookis 10]

Hi there, does the server activity viewer on the server dashboard say that it stopped?

Hi Luke

 

No, it doesn't. It just goes to the next one.

 

[Luke 39294]

If you play from the web app, how does that compare?

[Pankookis 10]

If you play from the web app, how does that compare?

When I have "Play next episode automatically" enabled, it works as expected with the web app.

2020-06-04 19:44:49.205 Info HttpServer: HTTP Response 204 to 192.168.1.6. Time: 97ms. http://192.168.1.7:8096/emby/Sessions/Playing/Stopped
2020-06-04 19:44:49.206 Info PlaybackReporting - EventMonitorEntryPoint: _sessionManager_PlaybackStop : Entered
2020-06-04 19:44:49.218 Info PlaybackReporting - EventMonitorEntryPoint: Saving final duration for Item : xxx
2020-06-04 19:44:49.233 Info PlaybackReporting - EventMonitorEntryPoint: Removing Old Key from playback_trackers : xxx
2020-06-04 19:44:49.233 Info Trakt: Playback Stopped
2020-06-04 19:44:49.233 Info Trakt: Item is played. Scrobble
2020-06-04 19:44:49.233 Info HttpClient: POST https://api.trakt.tv/scrobble/stop
2020-06-04 19:44:49.352 Info HttpServer: HTTP POST http://192.168.1.7:8096/emby/Sessions/Playing. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0
2020-06-04 19:44:49.357 Info SessionManager: Playback start reported by app Emby Web 4.4.3.0 playing Charlie and Dee Find Love. Started at 0 ms
2020-06-04 19:44:49.358 Info PlaybackReporting - EventMonitorEntryPoint: _sessionManager_PlaybackStart : Entered
2020-06-04 19:44:49.358 Info PlaybackReporting - EventMonitorEntryPoint: Adding PlaybackInfo to playback_trackers : xxx
2020-06-04 19:44:49.358 Info HttpServer: HTTP Response 204 to 192.168.1.6. Time: 6ms. http://192.168.1.7:8096/emby/Sessions/Playing
2020-06-04 19:44:49.358 Info PlaybackReporting - EventMonitorEntryPoint: Saving PlaybackInfo to DB
2020-06-04 19:44:49.387 Info Trakt: Playback Started
2020-06-04 19:44:49.420 Info HttpServer: HTTP POST http://192.168.1.7:8096/emby/Sessions/Playing/Progress. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:76.0) Gecko/20100101 Firefox/76.0
2020-06-04 19:44:49.422 Info HttpServer: HTTP Response 204 to 192.168.1.6. Time: 2ms. http://192.168.1.7:8096/emby/Sessions/Playing/Progress
2020-06-04 19:44:49.495 Info HttpClient: POST https://api.trakt.tv/scrobble/start

 

[Luke 39294]

So this only happens when playing from Kodi?

[Pankookis 10]

On 6/20/2020 at 8:34 PM, Luke said:

So this only happens when playing from Kodi?

Yes, it's the Up Next addon by im85288 that play the next episode without "stopping it".

[Luke 39294]

Ok thanks for the info.

[im85288 1493]

@Pankookis Make sure you have the Kodi Trakt addon installed. This communication between up next and trakt has been in there for a long time and as far as I know working well. If there are still issues create an issue on my GitHub (link in sticky, assuring to attach the required information).

[billy_neptune 0]

Sorry to dig this up, but this issue persists in Kodi with Trakt+UpNext.  There is no time between the two episodes, so the trakt resume point of the former episode never clears.

 

I'm on an Nvidia shield