Ever since I re-did my Plex integration for version 0.100 the integration has not discovered any of my Plex clients. Occasionally my Apple TV Plex client would get re-added and append a higher number to the end of it’s entity but at least it existed.
Is there anything different that must be done for the new Plex integration to pick up clients as they play?
It’d be really nice to lock those entities in so they wouldn’t get auto-discovered as something else and keep changing the entity name too.
Are you on 0.101.3 yet? The update mechanism has changed a lot over the last few releases. The 0.102 release tomorrow includes a few more fixes and additional debug logging to help troubleshoot persisting edge cases.
Any entries that reference Plex in your logs? Also, how have you set up the integration? Via the Integrations page, configuration.yaml, or legacy plex.conf file?
I added it through the config flow on the integrations page.
I deleted my old trusty integrations in the hopes that the new version would fix my issue of my entity being renamed all the time.
I’ll hang tight until tomorrow’s update to see if that sorts out my Plex client issues.
As an update version .102 has fixed the issue.
My Apple TV Plex Client showed up again.
Now if I could only find a way to lock it down so it doesn’t show up as Apple_TV_4K_2 in a week when I restart HA…
Maybe that’s fixed too…
I found a race condition that’s fixed in 0.102.1. It’s possible you’ll randomly encounter this again in older releases.
As for the media player getting a new name, that should not be possible unless the unique identifier sent by the client is changing. Any chance you’re deleting and reinstalling the Plex app on the Apple TV?
Now that you mention it I did switch from the Beta to the Main Release. I wonder if that’s when it happened and I didn’t put 2 and 2 together.
Thanks for the info.
It seems to be working fine still.