PlexKodiConnect icon indicating copy to clipboard operation
PlexKodiConnect copied to clipboard

2 devices reporting as one session/device: PKC's Unique Plex ID cannot be altered

Open aniel300 opened this issue 3 years ago • 28 comments

am having this issue similar to the one described here https://github.com/croneter/PlexKodiConnect/issues/764 where i have cloned a kodi instance and if i tried to play the same thing or different things plex dash will show it as one session/device etc. i have tried rebooting the server, changing the device name under pkc settings, closed and opened kodi, generating new unique id in pkc settings but issue still persist, thank you in advance.

aniel300 avatar Oct 08 '21 02:10 aniel300

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

croneter avatar Oct 08 '21 04:10 croneter

this is one of the ts step i took, it did not solve the issue

aniel300 avatar Oct 08 '21 05:10 aniel300

Do you use Tautulli? Or PKC only?

Make triple sure that you repeat my instructions above to the letter again, including starting Kodi again. Changing the device name is not sufficient

croneter avatar Oct 08 '21 08:10 croneter

i was using plex built in dashboard to check but let me check again with using Tautulli, and yes am pretty sure i have follow your instruction to the latter, i understand correctly only the cloned kodi need to to run the "Generate a new unique Plex device ID" option right ? is there a way to check the Plex device ID from plex or kodi ?

aniel300 avatar Oct 08 '21 12:10 aniel300

just checked with Tautulli, same issue still happening

aniel300 avatar Oct 08 '21 12:10 aniel300

Try this:

  • Run Generate a new unique Plex device ID again on BOTH PKC installations
  • Use a different device name on BOTH PKC installations
  • Shutdown both Kodis
  • Restart your Plex Media Server
  • Start Kodi

croneter avatar Oct 09 '21 10:10 croneter

Also make sure - on the Tautulli side, so to speak - that your Kodi devices use different hostnames!

croneter avatar Oct 09 '21 10:10 croneter

issue still happening, if i remember correctly ,y this didn't used to be like this. am using the same user for this test

aniel300 avatar Oct 09 '21 15:10 aniel300

Pfffff, there really shouldn't be any issue there! 😢

Kindly share the DEBUG logs from both Kodi devices, see https://github.com/croneter/PlexKodiConnect/wiki/How-to-Report-A-Bug

croneter avatar Oct 09 '21 16:10 croneter

do u have a discord, so i can send u the files, last time i shared log my plex was hacked

aniel300 avatar Oct 09 '21 17:10 aniel300

Ouch 🤕 Nope, but you could email them: croneter at gmail

croneter avatar Oct 09 '21 17:10 croneter

done.

aniel300 avatar Oct 09 '21 19:10 aniel300

Yes. Got it thanks. I edited your message, deleted my email to prevent spam 😜

croneter avatar Oct 09 '21 19:10 croneter

ok, i understand

aniel300 avatar Oct 09 '21 19:10 aniel300

For whatever reason, your unique Plex device ID did not change: Log of device 1:

NOTICE: PLEX.clientinfo: Unique device Id plex_client_Id loaded: 02e0c255-a1a0-4d88-9868-ccdf253c948a

Log of device 2:

NOTICE: PLEX.clientinfo: Unique device Id plex_client_Id loaded: 02e0c255-a1a0-4d88-9868-ccdf253c948a

These strings need to be different from each other.

Workaround:

  • Make sure both Kodi instances are not running anymore.
  • On one of the 2 devices, navigate to the Kodi userdata directory
  • Edit the file settings.xml in the folder addon_data/plugin.video.plexkodiconnect
  • Change the string in this line:
<setting id="plex_client_Id">02e0c255-a1a0-4d88-9868-ccdf253c948a</setting>

to something like this (so just a changed last letter a --> b

<setting id="plex_client_Id">02e0c255-a1a0-4d88-9868-ccdf253c948b</setting>
  • You may need to restart the Plex Media Server, don't know

croneter avatar Oct 10 '21 12:10 croneter

There's indeed a bug there, will fix it if I find the time

croneter avatar Oct 10 '21 12:10 croneter

ok sounds good, i wonder why this is only happening to me and not others

aniel300 avatar Oct 10 '21 12:10 aniel300

Happens to me, too. For whatever reason, the new setting value is not written back to file 😢

croneter avatar Oct 10 '21 13:10 croneter

am trying kodi 19 and the new pkc for it as a ts step, right now

aniel300 avatar Oct 10 '21 13:10 aniel300

same issue

aniel300 avatar Oct 10 '21 13:10 aniel300

Should finally be solved with PKC beta version 3.5.9

croneter avatar Nov 03 '21 07:11 croneter

thank u very much @croneter, i really appreciate it, keep up the good work

aniel300 avatar Nov 03 '21 07:11 aniel300

was this implemented into Kodi Leia

aniel300 avatar Nov 03 '21 07:11 aniel300

Not yet

croneter avatar Nov 03 '21 15:11 croneter

ok

aniel300 avatar Nov 03 '21 15:11 aniel300

Thanks, I had the same problem (just discovered this after cloning 10 devices :'( ) Changing the setting id="plex_client_Id" worked, only needed to restart Kodi (Android Shield TV 8.2.3, Android 9, Kodi 19.3) and voila.

Thanks for the advice and keep up the good work. And don't let the bugs annoy you too much; It's amazingly good what you've build right here!

hamakavula avatar Apr 10 '22 19:04 hamakavula

where do u change "id="plex_client_Id". btw i found a equal or better alternative, i just haven't play with and kodi in a long time. nor the dev of this project fixed the issue for kodi 17

aniel300 avatar Apr 11 '22 01:04 aniel300

can confirm the workaround works. however is there any way you can fix or automate the process of generating a new "plex_client_Id" ?

aniel300 avatar Oct 13 '22 14:10 aniel300