@vanstinator I had this problem today except that previously it would actually complete the action. This time it didn’t.
@vanstinator I just did a factory reset on my echo dot gen 3 today and unlinked from the plex skill and enabled it again, though I am still having the same issue.
It will also say uh-oh something went wrong. Though 9/10 times it will still do the command. Also sometimes I get an issue that says alexa is having trouble communicating with the plex skill.
Still having the issue running PMS 1.15.6.1079. Using a Echo Dot Gen 3 to control Plex for LG 3.98.0 running on webOS 3.8.0. The commands get executed but Alexa says “uh-oh something went wrong”.
Also sometimes when I ask her to do something, she replies 'I’m having trouble accessing your Plex skill right now."
Hi. In what version of PMS has this been fixed?
I have 1 15 6 1079 and Uh oh. For me it has not been reliable enough to use or show off (embarrassing!). There are other ways of course. Selecting server and player has possibly helped in past. Sometimes says uh,oh but plays.
It good that it is being worked on. Plex is very close to 10/10 IMHO and especially good on Oculus GO for easy access everything, especially 3d.
Our skill servers host the application code for the Alexa Plex skill backend. It interfaces with a fairly large set of PMS versions.
@RentreX @geezetosschot @jjross
Thanks for the reports. We’re investigating.
Same issue here use 2nd Gen Echo Plus. Tell Alexa to ask Plex to play a video funny thing is the process competes but still get visible error message. Please fix this.
Thanks @vanstinator - However unfortunately I am currently running PMS 1.15.6.1079 on a Windows Server, with a 2nd Gen Echo, and it no longer does anything with the Plex skill. Every command, Open Plex, Play this… always returns “uh-oh, something…”
same thing with me. the voice commands always work (play, pause, etc) but Alexa always responds with “Uh oh, something went wrong. I’ve alerted the plex team so they can take a look.”
New member here. My alexa/plex/nvidia shield integration was working fine till last few weeks. “Alexa, Open Plex” used to instantly open plex on my tv. Now, it says “I couldn’t find plex”.
I disabled the skill, re-enabled after removing all the links. I only have one Plex account so it’s not a matter of different accounts. While it does not open Plex, if I manually open plex, alex would let me Play/Pause.
When asked what my preference of default video should be, when selecting Nvidia shield, it says “uh oh, something went wrong, alerting plex team”
I am on the latest update of Plex as of 6/17/2019. Please help.
Still getting the “Uh-oh something went wrong” message regardless of command on server version 1.16.0.1226-7eb2c8f6f
Commands still seem to be going through and working but the error persists
ditto mhiggins. Alexa says “something went wrong” even though my commands work.
I tested using the echo and the Alexa phone app and both return the “Uh oh” message but perform the task correctly.
The Plex skill was working really well initially, but started to say “Uh oh something went wrong about a month ago. I’ve alerted the Plex Team so they can take a look.” but still actually performing the task.
If the message was simply removed (or there was an option to turn it off), then it would simply be working.
My server is on a Raspberry Pi 3 running plexmediaserver_1.16.1.1291-158e5b199_armhf.
Same issue.
I just installed the Latest beta version of plex server running on a WD NAS, then using echo dot version 3 and Apple TV as my player.
Alexa gives the command successfully and the action works but she still says “uh-oh… “
The Alexa app was recently “advertised” in a newsletter email - being able to tell a voice assistant to play a specific show or movie from my library sounded so amazing that I went ahead and bought an echo just for it.
I’ve set up everything correctly - skill, server and player. Server is fully accessible remotely as well. Any playback commands that I give it, it successfully fulfills the task BUT I ALWAYS get the “oh oh, something went wrong…” error, at the very end, when the command has been executed.
Come on PLEX, you must have all the information, logs and feedback you need by now to be able to find out what’s wrong!? Talk to us, say something, enough of the silent treatment. Help us help you to crush this bug once and for all.
Else don’t advertise such a feature if it’s still not ready for prime time. It’s been so long that it’s laughable and embarrassing.
I completely agree with you. Not sure how “big” the company is, but it would definitely appear that the marketing department are not talking to the devs about things that are not working. To Advertise a feature of the product that has been broken for months it totally embarrassing!
I’m also getting the “uh-oh, something went wrong” response even though Alexa is getting Plex to do what I want okay.
Hi all. Wanted to let you know that I now have the Plex skill working again on my Echo.
I disabled the skill via the Mobile app, rebooted the Echo and reinstalled the Skill.
When prompted to link to my Plex account, it linked without error and now works just fine.
My current PMS version is 1.16.2.1297 running on Windows Server 2012R2.
I’ll check it again tomorrow and will let ya’ll know if it’s still working.
Cheers,
Andy.
Still working 