search

croneter / PlexKodiConnect

Plex integration in Kodi done right
GNU General Public License v2.0
1.16k stars 77 forks source link

Tautulli receiving the same session_id for different playbacks #764

Closed Panja0 closed 5 years ago

Panja0 commented 5 years ago

Describe the bug

I have 2 Kodi boxes running with PlexKodiConnect. If I play a (different) file (movie, tv show etc) on both boxes at the same time they both have the same session_id. This causes issues with the app Remote for Tautulli.

Expected behavior

Every new play should have a different session_id.

croneter commented 5 years ago

Try this: in the PKC settings under Advanced, choose "Generate a new unique Plex device ID" on one of the devices. Restart Kodi. Issue should be solved

Panja0 commented 5 years ago

Not working... I even did it on both machines (generating a new unique Plex Device ID) without luck.

Kodi/PKC one: "session_id": "44cc7f30-3726-4fed-8913-919d61252743"

Kodi/PKC two: "session_id": "44cc7f30-3726-4fed-8913-919d61252743"

croneter commented 5 years ago

Please share DEBUG log files of you playing something for both devices, see https://github.com/croneter/PlexKodiConnect/wiki/How-to-Report-A-Bug

Panja0 commented 5 years ago

Here ya go!

Kodi 01 machine: kodi01.log

Kodi 02 machine: kodi02.log

croneter commented 5 years ago

I'm pretty sure you already fixed the bug by following my steps above. Might be that either the PMS or Tautulli somehow took their time to pick up on the change.

Reboot both devices again please. Then try again

Panja0 commented 5 years ago

I’m sorry. It did not fix anything for me. I have rebooted the boxes several times the past days without any luck.

Aan za, mrt. 16, 2019 om 17:38, croneter notifications@github.com schreef:

I'm pretty sure you already fixed the bug by following my steps above. Might be that either the PMS or Tautulli somehow took their time to pick up on the change.

Reboot both devices again please. Then try again

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

croneter commented 5 years ago

Does Plex web have any issues when you play 2 different items simultaneously? Or only Tautulli? My guess is that Tautulli is the culprit here

Panja0 commented 5 years ago

The problem is with the app Remote for Tautulli. I had contact with the developer and he told me the problem is with PKC.

The only thing I know and see is that PKC gives the same session_id to both streams...

croneter commented 5 years ago

With PKC, there is no session_id. Could the Tautulli dev be very specific here?

tfonfara commented 5 years ago

@croneter hi, I'm the developer of Remote for Tautulli app, maybe we can solve this together.

I've developed this app to work properly with any original Plex client. So far this is the first issue in that matter. After some analysis @croneter and me found that PKC is sharing the same session_id across multiple devices which should not be the case (a session should be unique). So at that point PCK behaves different to the official clients. For my understanding this isn't a bug in my app, as this behavior is "not usual".

WDYT?

tfonfara commented 5 years ago

Maybe one additional note, I'm just accessing the api of Tautulli itself, maybe the issue could also be there.

croneter commented 5 years ago

Hell there @tfonfara :wave: .

There is no session_id that is passed to the PMS. What is passed is a unique client id as . This id will be identical if a Kodi installation is cloned/copied. Choosing Generate a new unique Plex device Id in the PKC settings under Advanced will set a new unique id. A Kodi reboot is then mandatory. I have seen in the past that it took the PMS a while to pick up this change.

Only exception is if PKC/Kodi should transcode - which was not the case here

I don't know what else besides X-Plex-Client-Identifier could be causing the behavior :disappointed:

Panja0 commented 5 years ago

I have generated an unique Plex ID for both the Kodi boxes and rebooted numerous times.

croneter commented 5 years ago

That's why I'm thinking it might be a Tautulli issue.

Panja0 commented 5 years ago

On the Tautulli website I’m see 2 different streams and I can click on both of them. Getting the individual information for the streams...

tfonfara commented 5 years ago

@Panja0 this only means that Tautulli web interface might use a different property for selecting the streams this does not mean that session_id isn't unique 🤔

Panja0 commented 5 years ago

Hmm I see. Well I don’t know.

Probably this will be something unresolvable...

croneter commented 5 years ago

Is this still an issue?

Panja0 commented 5 years ago

The problem has been solved. The creator/dev of Tautulli made a workaround which works for me.

Sorry for not getting back to you earlier.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, 25 June 2019 18:21, croneter notifications@github.com wrote:

Is this still an issue?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

bxprbadboy commented 5 years ago

Can you share the work around with the community for those that use tautulli?

Panja0 commented 5 years ago

There is no workaround on an user level. It’s implemented in Tautulli so everyone can benefit from it.

Aan di, jun. 25, 2019 om 22:08, bxprbadboy notifications@github.com schreef:

Can you share the work around with the community for those that use tautulli?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

croneter commented 5 years ago

So it's solved? Great

Panja0 commented 5 years ago

Yes, it’s solved.

Aan wo, jun. 26, 2019 om 06:43, croneter notifications@github.com schreef:

So it's solved? Great

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.