I have several PI’s and recently cloned one PI from another. The Device names were changed in Preferences and System Settings and they are both using different user accounts, but they will ‘bump’ each other off if they are both using transcode settings. I’ve had less problems with direct play.
Is there a unique identifier I’m missing here? Perhaps they are both registered with Plex under the same device id, and thus matching tokens from the authentication?
[Edit] Just realized this token data should be in the debug log. But I’ve had that data obscured during testing.
@benjaminwolf said:
I have several PI’s and recently cloned one PI from another. The Device names were changed in Preferences and System Settings and they are both using different user accounts, but they will ‘bump’ each other off if they are both using transcode settings. I’ve had less problems with direct play.
Is there a unique identifier I’m missing here? Perhaps they are both registered with Plex under the same device id, and thus matching tokens from the authentication?
[Edit] Just realized this token data should be in the debug log. But I’ve had that data obscured during testing.
I have four RPi’s all with different names in Preferences and System Settings, all run on the same network and logged in with the same user id without any issues, have you checked that they all have unique IP’s handed out by your router. Did you sign in to each RPi via the use of ah PIN by visiting plex.tv/pin? Have you checked in devices in PlexWeb that they are all registered as unique devices?
Cloning RPi’s is not the best way to set them up, each one should be setup individually, sign out of each one and sign in again using the PIN method.
I signed in with PIN on the first clone. The other was cloned from this one. I’d need to do some re-cloning to confirm but I’m guessing they were using the same supertoken. I’m not certain this was the case as I didn’t have tokens enabled in the server log. It seems that there appears to be some overlap in the devices in PlexWeb that maybe causing the issue.
I may clone another and kill all devices and force them to log back in via Pin to see if that’s good enough to get a unique id for each PI.
Thanks, Ned. Having done some experimenting over the weekend, I believe removing the device and signing back in may not be enough. I had two conflicting PI’s cloned from the same signed in PI, which has been signed out and resigned in with alternate Pins. A clean install for both fixed the issue.
