Getting New Device Access Notifications from Plex triggered by PlexCache-D

[dougie175]

This issue is probably user error in my setup rather than something wrong with PlexCache-D itself, but I'm getting notifications from my Plex server than new devices have been added (in the middle of the night) see, below screenshot from my phone combined with authorised devices shown from my Plex Server. (Don't judge the username it was made so it was simple for my kids when they were younger!)

Is this an issue or just a setting I have wrong in my unRAID setup? Everything is functioning nicely but I'd like to stop the notification / device been re-authorised all the time

Thank You

[Brandon-Haney]

Hmm I hadn't ran into this issue but I just found that my notification for this was not enabled in my app, I enabled it and do some debugging on this and get back to you.

[dougie175]

Thanks appreciate it, let me know if you need anything from me that might give info for what's triggering it i.e logs and such

[Brandon-Haney]

Thanks appreciate it, let me know if you need anything from me that might give info for what's triggering it i.e logs and such

@dougie175 would you be willing to test my fix? You can update your repo to ghcr.io/brandon-haney/plexcache-d:dev and do a force update, it should fire that notification once but hopefully you won't see it again.

I'm running it for the next few days and with your confirmation that it solves the issue, I can proceed to PR the fix.

[dougie175]

Thanks appreciate it, let me know if you need anything from me that might give info for what's triggering it i.e logs and such

@dougie175 would you be willing to test my fix? You can update your repo to ghcr.io/brandon-haney/plexcache-d:dev and do a force update, it should fire that notification once but hopefully you won't see it again.

I'm running it for the next few days and with your confirmation that it solves the issue, I can proceed to PR the fix.

Done, much nicer that it call's itself Plexcache-D now too. I'll let you know how it gets on over the next few days. Thanks

[dougie175]

Just a bit of feedback. I haven't received any additional notifications so far, so looks like you fix is working. Thank You. If you can let me know when it's on the main repo it would be appreciated and I'll switch back over to the latest stable builds. Thanks

[Brandon-Haney]

Just a bit of feedback. I haven't received any additional notifications so far, so looks like you fix is working. Thank You. If you can let me know when it's on the main repo it would be appreciated and I'll switch back over to the latest stable builds. Thanks

I'll submit a PR later this evening and after it's merged I'll tag you here so you can revert the repo to this.

[Brandon-Haney]

@dougie175 good news, the fix is merged into the main repo now (#192). It'll roll into the next stable build of the official image.

One clarification on switching back, since the :dev build you tested is on my personal fork, not the main repo. Once the new stable image is published, set your container's Repository back to the upstream one:

ghcr.io/studionirin/plexcache-d:latest

That moves you off my fork and back onto the official builds, with the fix included.

Heads up that you'll likely see one more New Device notification right when you switch images, since the build changes, but it should stay quiet after that.

Thanks a lot for testing it and confirming it solved things on your end. That's what gave me the confidence to push it upstream.

[dougie175]

Thanks very much. Moved back to the main repo. I didn't get an additional notification by the way but all seems well with it. Thanks

[dougie175]

An hour later I just got this it was slicker when it says Plexcache-D. Hopefully it's the only one I get though. Thanks

[Brandon-Haney]

An hour later I just got this it was slicker when it says Plexcache-D. Hopefully it's the only one I get though. Thanks

When you changed the repo back did you make sure to force a fresh update? If not then please do that now.