This issue has been persisting over a week. Can someone from Plex please acknowledge and update?
Same issue…even updated my plex server, no luck. It will play on my echobee with voice control (alexa).
I read somewhere that all but gen 1 echos would be getting an update to meet some new IoT standard…is this the reason why?
Found the article I read…https://www.theverge.com/2021/7/21/22586377/amazon-echo-matter-standard-dot-show-studio-flex-plus-upgrade
1 Like
This issue seems to be limited to my 1st gen echo device now (I also have 2nd, 3rd, and 4th gen devices) - the other day most of my echos had an issue playing from plex, so perhaps there is some software update rollout that caused this as datusm suggests from the article.
I gave up on waiting and traded in my Echos for new ones. Sucks, but no one from Plex or Amazon has even acknowledged this issue. Very disappointing.
I agree, VERY disappointing. C’mon Plex, seriously… fix this up.
Plex devs, I did some debugging for you. The log differences are below.
Gen1 Device
Oct 15, 2021 12:01:41.180 [14112] Debug — Completed: [xx.xx.xx.xx:39736] 200 GET /hubs/search?query=holdingout&limit=25 (7 live) TLS 266ms 2236 bytes
Oct 15, 2021 12:01:42.679 [2376] Debug — Request: [xx.xx.xx.xx:29971 (WAN)] GET /library/metadata/50796?checkFiles=1 (7 live) TLS Signed-in Token (xxx)
Gen4 Device
Oct 15, 2021 12:07:45.352 [14112] Debug — Completed: [xx.xx.xx.xx:61123] 200 GET /hubs/search?query=holdingout&limit=25 (9 live) TLS 225ms 2236 bytes
Oct 15, 2021 12:07:46.248 [2376] Debug — Request: [<local_router_ip>:53238 (Subnet)] GET /library/parts/699464/1591271855/file.mp3?protocol=http&hasMDE=1&session=xxxx7fb4&directPlay=1&mediaIndex=0&partIndex=0&offset=0&Accept=application%2Fjson (7 live) TLS Signed-in Token (xxxx)
Oct 15, 2021 12:07:46.253 [2376] Debug — Streaming Resource: Attempting to create AdHoc dp session xxxx4c452 for part 699464
Oct 15, 2021 12:07:46.257 [2376] Debug — TranscodeUniversalRequest: using augmented profile Generic
Oct 15, 2021 12:07:46.257 [2376] Debug — Downloading document http://127.0.0.1:32400/library/metadata/50808?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&includeBandwidths=1&offset=-1&X-Plex-Incomplete-Segments=1&X-Plex-Session-Identifier=xxxxxx4c452
Oct 15, 2021 12:07:46.257 [2376] Debug — HTTP requesting GET http://127.0.0.1:32400/library/metadata/50808?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&includeBandwidths=1&offset=-1&X-Plex-Incomplete-Segments=1&X-Plex-Session-Identifier=xxxxx4c452
Oct 15, 2021 12:07:46.260 [17156] Debug — Request: [127.0.0.1:65220 (Loopback)] GET /library/metadata/50808?includeBandwidths=1&offset=-1 (8 live) GZIP Signed-in Token (xxxx)
Oct 15, 2021 12:07:46.269 [14112] Debug — Completed: [127.0.0.1:65220] 200 GET /library/metadata/50808?includeBandwidths=1&offset=-1 (8 live) GZIP 9ms 1176 bytes (pipelined: 1)
Oct 15, 2021 12:07:46.269 [2376] Debug — HTTP/1.1 (0.0s) 200 response from GET http://127.0.0.1:32400/library/metadata/50808?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&includeBandwidths=1&offset=-1&X-Plex-Incomplete-Segments=1&X-Plex-Session-Identifier=xxxxx4c452
Oct 15, 2021 12:07:46.271 [2376] Debug — Streaming Resource: Adding session 06715830:xxxx4c452 which is using 515kbps of WAN bandwidth. Used is now 515kbps
Oct 15, 2021 12:07:46.271 [2376] Debug — Streaming Resource: Added session 06715830:xxxxx4c452
Oct 15, 2021 12:07:46.271 [2376] Debug — Streaming Resource: Reached Decision id=50808 codes=(MDE=1000,Direct play OK.) media=(id=696311 part=(id=699464 decision=direct play protocol=* streams=(Audio=(id=1410008 decision= channels=0 rate=0))))
Oct 15, 2021 12:07:46.287 [2376] Debug — Found an ID3v2 tag at start of MP3 file with size 2177, skipping.
Oct 15, 2021 12:07:46.288 [2376] Debug — Content-Length of C:\Holdin_Out.mp3 is 5697152 (of total: 5697152).
Oct 15, 2021 12:07:46.320 [14116] Debug — Failed to stream media, client probably disconnected after 113527 bytes: 10054 - An existing connection was forcibly closed by the remote host
Oct 15, 2021 12:07:46.320 [14116] Debug — Completed after connection close: [<local_router_ip>:53238] 200 GET /library/parts/699464/1591271855/file.mp3?protocol=http&hasMDE=1&session=xxxx7fb4&directPlay=1&mediaIndex=0&partIndex=0&offset=0&Accept=application%2Fjson (8 live) TLS 71ms 113527 bytes (pipelined: 1)
Oct 15, 2021 12:07:46.435 [17964] Debug — Request: [<local_router_ip>:53240 (Subnet)] GET /library/parts/699464/1591271855/file.mp3?protocol=http&hasMDE=1&session=xxxx7fb4&directPlay=1&mediaIndex=0&partIndex=0&offset=0&Accept=application%2Fjson (8 live) TLS Signed-in Token (xxxx) (range: bytes=5697024-)
Oct 15, 2021 12:07:46.442 [17964] Debug — Found an ID3v2 tag at start of MP3 file with size 2177, skipping.
Oct 15, 2021 12:07:46.442 [17964] Debug — Content-Length of C:\Holdin_Out.mp3 is 128 (of total: 5697152).
Oct 15, 2021 12:07:46.445 [14112] Debug — Completed: [<local_router_ip>:53240] 206 GET /library/parts/699464/1591271855/file.mp3?protocol=http&hasMDE=1&session=xxxx7fb4&directPlay=1&mediaIndex=0&partIndex=0&offset=0&Accept=application%2Fjson (8 live) TLS 10ms 128 bytes (pipelined: 1) (range: bytes=5697024-)
Oct 15, 2021 12:07:46.567 [17964] Debug — Request: [<local_router_ip>:53240 (Subnet)] GET /library/parts/699464/1591271855/file.mp3?protocol=http&hasMDE=1&session=xxxx7fb4&directPlay=1&mediaIndex=0&partIndex=0&offset=0&Accept=application%2Fjson (8 live) TLS Signed-in Token (xxxx)
Oct 15, 2021 12:07:46.573 [17964] Debug — Found an ID3v2 tag at start of MP3 file with size 2177, skipping.
Oct 15, 2021 12:07:46.573 [17964] Debug — Content-Length of C:\Holdin_Out.mp3 is 5697152 (of total: 5697152).
Apparently the first gen devices first request after the search response is a GET on /library/metadata/ with the checkFiles field, while the second gen and higher subsequent request after the search response is a GET on /library/parts/
After the /library/metadata/ GET completes there’s no further API requests to get the file, while on the second gen and higher device, the /library/parts/ GET follows up with calls to GETs on /library/metadata with different fields including the token, etc.
I’m not an Alexa dev guru, but I’m sure this should be a big enough clue to investigate this and fix up the skill for us customers. If not, tell me what other data you want.
1 Like
Just saw this thread. To be clear, is it the 1st gen Echo (tall tower looking thing) or Echo dot (hockey puck)?
1 Like
In my case it’s the tall tower looking thing - the Echo - not the Echo Dot. Not sure about other folks devices though. Model number on bottom says SK705DI.
1 Like
I’m having the same issue with my 1st Gen echo.
Me too!
update: I upgraded to latest plex server yesterday which upgraded my libraries. Today I notice a “slight” change in response on the Gen1 Alexa Echo device. On the previous version of PMS, when requesting a song on the Gen1 device, it would not repeat the song title requested, just the artist and then play nothing (like the song title was blank). Now, the Gen1 device repeats the song title requested along with the artist, and then plays nothing. In the logs, API interaction remains the same as when posted previously, but since the log doesn’t include the contents of the API interactions, I’m just guessing that the updated PMS now includes the song title properly back to the Alexa skill.
Plex team - any new developments on this? Were you able to reproduce the issue on your side?
1 Like
It is also the Amazon Tap device as well as the 1st gen (tall) Echo.
Interesting that the projected Matter platform change (referenced in the linked article above) also leaves out 1st gen Alexa devices. But as far as I can tell, those devices’ Plex problem is directly related to the Let’s Encrypt expired certificate that has affected other software around the world. This includes the Plex for TiVo software (which has a workaround of setting it to not require a secured connection on local devices).
See this thread for more: Can't play music on Alexa tonight - #12 by tulsatv
Thanks for the confirmation. I’m checking with the team what could have happened.
2 Likes
I have two 2nd generation Echo’s running as a stereo pair with an Echo Sub. Always worked perfectly to have Alexa play music from PLEX from Windows 10 media server. For a long time now, Alexa recognizes the PC/Server, the song/album/artist titles, library radio, etc., it says it is now playing… then nothing ever happens, just silence. So frustrating. Doesn’t work at all. Used to work so great. Now I have two bookends and zero sound from my PLEX library going through the Echo devices. Talk to Alexa who responds perfectly, then… nothing. What changed? It is a PLEX pass feature now? An API issue? I don’t know where to turn. I’m going through the community threads and it appears I’m not alone. 10.22.2021
1 Like
interesting - I tried my 2nd gen Echo dot (model RS03QR) today and it played from latest PMS (v1.24.5.5160) with no issue, just like my 3rd and 4th gen Echo Dots. My ongoing issue is with my 1st gen Echo (model SK705DI).
@towerpower It would probably be helpful for the devs for you to indicate your PMS version as well as the specific device model numbers for the Echos you’re having trouble with.
@anon18523487 any movement from the dev team regarding this issue?
So glad I found this thread, spent almost 8 hours today trying to connect my tall 1st gen echo device, you’ve guessed it, nothing I tried worked. I also have 2 x 2nd gen echo dots and a echo show, all three work. Thought I was going mad. Finally found this thread to realise it’s not my settings, it’s the device.
1 Like
PMS Version 1.24.4.5081 - up to date as of 10/23/2021 7:44 PM Pacific.
Where do you find a model number for the 2nd generation Echo’s??? I can’t find a model number for the 2nd generation echo’s, certainly not on either device, nor on my original Amazon order, or by Googling anything about it on the Internet, YouTube, here on the PLEX forums, etc. I have seen 1st gen model numbers here, but not 2nd. It’s just the 2nd generation taller echo. Two of them connected as a stereo pair to an echo sub. Works for all streaming services except PLEX. Used to work great. Now silent. Tried everything such as reinstalling PLEX, disabling and reenabling the Alexa skill, etc. Re-analyzing the PLEX music database… Just seems like it’s never going to come back. Day after day, week after week. No luck, and I try daily.
@towerpower I had the same issue finding out the difference between the devices as well. Usually there a slight difference when connecting a gen 1 and gen 2 device. On a gen 1 echo you have to temporarily connect to the devices Amazon local network on wifi when pairing the device to your network, with a gen 2 and higher you don’t need to do this.
I already know I have gen 2 Echo’s, but was looking for an actual model number. Don’t even know if the dev team would need that. I don’t see how to determine that, as suggested by another member, the dev team could use my PMS # and Echo model #. So I put up the PMS Version of 1.24.4.5081 but can only say I have 2 - Echo’s - 2nd generation (no model numbers). Maybe someone can figure out how and why everything just quit working. Was it a Windows update? An Amazon change? A PLEX change? Everything is the same for me as far as equipment that used to work with Alexa sending PLEX to the stereo pair of 2nd gen Echo’s and the Echo Sub, and now Alexa says she’s playing music and nothing is happening.
