Support for Alexa voice control has launched!
FIXES:
- fixed an issue that was causing docker images to crash
- fixed an authentication loop caused by an expired plex token
A small update went out to our Alexa service today. Servers older than version 1.5.1 are no longer supported.
FIXES
-fixed an issue where removing the device from your plex account would cause an authentication loop when trying to use the -skill again
-improved media matching capabilities
-uttering STOP would not always properly exit the skill
NEW
-support for shuffling and playing a playlist
-support for shuffling an album
NEW
- support audio playback on echo devices that support audio playback
- pick a default server for new users
FIXED
- some players would fail to save to the database
- http content was not properly throwing an error when being played on Alexa
- various cases where starting media would fail and the user would receive the “Oh no…” error
- in certain cases audio would appear to randomly stop and move to the next track
FIXED
- the Now Playing screen in Plex Web would erroneously show
Direct Playwhen the PMS was transcoding - an invalid token will now redirect the user to link their account again
FIXES:
- send timelines on a regular schedule to prevent transcodes from dying
- use the correct access token when accessing shared servers
FIXES
- send a session id in the timelines sent to PMS
FIXES
- tracks now pre-buffer by calling the decision endpoint
NEW:
- fallback to relay when media playback fails due to NAT loopback
NEW:
- support for artist, library, and time travel radios!
- available in Canada, Australia, and India
FIXED:
- fallback to a local connection when remote connections fail due to NAT loopback
- some cases of continue watching would throw an error response after media began playing
- respond with a warning if a custom domain is used with the media server and has a mismatching certificate
- slight tweaks to easter eggs
- recently added tv doesn’t fail when suggested
-
httpmedia urls should fail and alert the user to turn onhttps
FIXES:
- test available remote connections before trying to connect to a server
NEW:
- fall back to unsecured local connection if both the secured remote and secured local connection have failed
FIXES:
- in some cases timelines would fail to send ending playback prematurely
FIXES:
- test server connections when picking a default server during the first run experience
- stop caching server connection info if no valid connections are found during testing
FIXED:
- Fixed a case where timelines could fail to send
NEW:
- Show additional metadata in the device settings page for Alexa devices
FIXED:
- Include the platform type on timeline requests to fix issue with 3rd party reporting tools showing blank device type
NEW:
- Support the new metadata display feature on the Echo Show and Echo Spot
FIXED:
- In some cases a song could fail to enqueue causing playback of a play queue to prematurely end
1 Like
FIXED:
- Rewrote timeline event handler to avoid various state issues
- Timelines could fail to send causing playback to abruptly end after the current track
- In rare cases offsets were reported greater than the duration causing timeline events to get rejected
- Transcode sessions for buffering content could end early causing tracks to prematurely stop playing
- Tracks were sometimes being queued up twice causing duplicate playbacks
2 Likes
FIXED
- in some cases remote control commands failed to send
- changing default video players could fail
1 Like
NEW
- music playback will use local connections first when possible
FIXED
- in some cases a play queue could prematurely run out of items
- improved media connection logic for networks with NAT Loopback or DNS rebinding protections
- media connection information is cached less aggressively when in a non-working state
2 Likes
