Plex on Apple TV 4K (2022) won't announce as player (to be controlled from Plex on other devices)

Just curious if there’s an ETA on the fix version?

1 Like

8.16 with fix should be public in the next couple days unless something unexpected comes up that blocks it

2 Likes

Hi and thanks.

Solved :clap:

By the way. Is it possible to make the Plex players announce themself with different names? As of now my (Apple TV) players just says “Apple TV” and It’s impossible to tell them apart.

Heh, raised this a week or two back: Is there a way to rename an Apple TV player?

1 Like

Watching that topic now. Thanks.

If only 8.16 fixed it.

And you’ve definitely got the new version?
Did you try turning off the setting, force quitting the app, then turning it back on? @ShaGe mentioned needing to do that when using the 8.16 beta.
Will try it myself once I get some time.

Working for me after the above steps btw. Persists over sleep/wake too.

Sorry I’m not clear if working for y’all as some has said it does or not. May need to toggle it off thne on again but should work with 8.16

Well, it works but not always out of the box. Sometimes, after a day off power, it takes a while before the AppleTV-player appears on iphone or ipad. I thought it might have to do with 2.4 vs 5khz channels of my router. iphone should be on 2.4 – but reading the comments here, I wonder if a little tweak in the plex-app is needed still…

Edit: Announce as player-toggle works sometimes, sometimes with a significant delay.

Definitely seems fixed for me in the new v8.16.

Not entirely fixed here. I just tried again: force quit to be sure, then I need to toggle announce as player before I can control my AppleTV4 with another device. As I said above, migth be wifi channel, but that shouldn’t be the problem…

Don’t get me wrong, I am happy to have it working with little effort, but I don’t think this should be the way. Perhaps another little software tweak will settle it for everyone. Unless I am the only soul remaining with this issue…

Definitely still flaky for me too. Gotten it to work with the iOS Plex app on occasion, but when (I should rather say if) my Apple TV shows up in the Plexamp cast menu, I always get a red bar indicating a failure to connect.

Not fixed for me. My Plexamp still doesn’t ‘see’ my Apple TV Plex, and I can’t connect to it.

Can we please get the Apple TV logs and the logs from the player you are casting from after opening cast menu

You’ll find logs attached. I reinstalled the AppleTV app and enabled the network broadcast in settings - the iOS Plex app picks it up straight away, but nothing shows up in Plexamp.

EDIT: it showed up in the list of available players! However selecting it as the cast target results in a red error bar and now it doesn’t react at all if I try to select it. Attaching the updated logs.

EDIT2: removing logs for privacy

1 Like

I need to toggle the Announce as a player-setting in the Plex AppleTV app every time I fire up my system. The setting is not remembered when I power off the AppleTV.

Moreover, connection/cast is lost regularly when using my iphone as remote for watching movies or using PlexAmp.

If you need more logs, let me know.

Unfortunately I’ve started experiencing issues again too. Nothing specific I can point to that’s causing it, but sometimes when Plex has been paused/stopped for some time, the player advertisement seems to just stop. Toggling it off then on has resolved this for me every time so far, while just restarting the app works maybe one in three.

Yup. It is possible to control the Apple TV4 after the announce as player setting in Plex on ATV4. However, it is not a persistent setting. I need to go through the sequence after every reboot (all power off) of the ATV4, which is quite often as all my media devices are shut off from power when I go to sleep. They all keep their settings…

I experimented with assuring that both ATV4 and iPhone of iPad are on the same 2.4 WiFi channel. No differences.

I fear that this issue will not be adressen anymore, given the suggestion here that the initial problem was fixed. It was, but only partially in my experience. Unless I am overlooking something very obvious, can someone please look into this again?

2 Likes