croneter

> Will it work with an old settings.xml for futured PKC versions as well? Yes, no worries at all! If something changes, PKC won't blow up in your face 😉...

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

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...

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...

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

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

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

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

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: ```...

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