Strange behaviour with Plex skill for Alexa on one of my Alexa devices

General Discussions Plex Features
1

Don’t really know the best category for this query because I can’t find any reports of similar behaviour.

Background: I run 2 Plex servers, one on my Windows 11 Desktop PC and another on a WD MyCloudHome device. The Desktop server is named STUDY-PC and the other is simply named MyCloudHome. I have several Alexa devices linked to my account (2 x Amazon Echo, 2 x Amazon Echo Spot, 1 x Amazon Echo Show and integrated Alexa in my car).

Problem: When using the Alexa app in my car only (problem does not exist on any other device - all linked to the same Amazon account), if I tell Plex to choose the MyCloudHome server and then try to play any content, it tells me that “I couldn’t find xxxx on Synology1”. I have no server named Synology1, and never have had one. In telling the skill to choose a server, it correctly names my 2 servers as the options available to me. If I tell it to select my other server everything works as expected. Every other Alexa device I have works perfectly with either server. This problem only began a couple of months ago - prior to that it worked perfectly in my car as well as on all my other devices.

I have tried disabling the Plex skill for Alexa and reenabling it, but the behaviour continues. I’m at a loss to understand where the problem even lies, and can only hope that someone here has some ideas of what else I can try to resolve it.

2

Have you tried unlinked your account from Alexa and relinking?

3

I’ve integrated Wyze cameras in my Alexa environment, and I’ve noticed that once you give Alexa permission to access a device in another ecosystem (Wyze, Plex, etc), Alexa makes up a name for the device in ITS ecosystem. So while your servers might not be called Synology1 (and Synology2?) in Plex, I bet that it is an auto-generated name for the server when you first associated it with Alexa.

I’d wager that you may be able to fix it by de-linking the servers from Plex and re-connecting, as BigWheel suggests. If you want to try something less drastic first, try opening up your Alexa app, and see if your servers show up there under this mystery name.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.