Jump to content

"Alexa Next" issuing FFWD command rather than next [on Emby Theatre]


ginjaninja

Recommended Posts

ginjaninja

Emby Stable.

Havent found all the circumstances when it goes wrong......may have something to do with Emby Theatre client type.

To reproduce

[default device has been set to Emby Theatre]

talking to Alexa DOT..

"Play Album Reflections by Artist Carly Simon

[Play back starts on default device]

"Alexa Next"

The current track playback fast forwards 30 secs (FFWD) rather than Next.

(Alexa Pause and Alexa Resume are working), (Alexa Previous goes back 30 secs in track)

 

2024-01-08 16:37:52.316 Info Server: http/1.1 POST https://‌‍‍XXX.XXX.XXX‌:8920/emby/Sessions/65d7a779cfe1278ea1d2fc27b3c4b4dd/Playing/NextTrack?Command=NextTrack&ControllingUserId=XXXXXXXXXXXXXXXXXXXXXXXXXXX. UserAgent: node-fetch
2024-01-08 16:37:52.436 Info Server: http/1.1 POST http://‌‍‍192.168.4.162‌:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby Theater&X-Emby-Device-Name=X670e&X-Emby-Device-Id=X670e&X-Emby-Client-Version=3.0.20&X-Emby-Language=en-gb&reqformat=json. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.20 Chrome/112.0.5615.165 Electron/24.3.0 Safari/537.36
2024-01-08 16:37:52.437 Debug SessionManager: OnPlaybackProgress TimeUpdate 1704730242918
2024-01-08 16:37:52.439 Info Server: http/1.1 Response 204 to ‌‍‍192.168.4.163‌. Time: 2ms. http://‌‍‍192.168.4.162‌:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby Theater&X-Emby-Device-Name=X670e&X-Emby-Device-Id=X670e&X-Emby-Client-Version=3.0.20&X-Emby-Language=en-gb&reqformat=json

the debug log seems to show Emby received a next track command ..so maybe this is an Emby Theatre Issue more than Emby Alexa Issue?

Link to comment
Share on other sites

hatharry

Alexa is sending the correct command by the looks of your logs. I've tried to replicate the issue with no luck. Does it happen randomly or with a certain album?

Link to comment
Share on other sites

ginjaninja
On 16/01/2024 at 00:31, hatharry said:

Alexa is sending the correct command by the looks of your logs. I've tried to replicate the issue with no luck. Does it happen randomly or with a certain album?

i can reproduce the issue just by using swagger, so its an emby theatre issue nothing to do with Alexa.

 

Link to comment
Share on other sites

ginjaninja
On 22/01/2024 at 20:01, Luke said:

What did you send to Theater?

image.png.7b724989e10064bd2a1728898c1c75f1.png

https://XXX.XXX.XXX:8920/emby/Sessions/65d7a779cfe1278ea1d2fc27b3c4b4dd/Playing/NextTrack?api_key=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

 

Link to comment
Share on other sites

ginjaninja
18 hours ago, Luke said:

How about if you click it in the ui?

Apologies i think i caused confusion. I was using Emby Theatre WMC. Not Emby Theatre...although WMC generally works i think softworks said to use this client on the Beta and i moved back to stable [4.7.14] which might explain why Alexas not working as expected for the "next track" function. [The ui next track button works as expected in WMC]

(next track command works as expected on Emby Theatre from windows store)

image.png.36b51a40aeaeabfc99c034963d65c83b.png

Edited by ginjaninja
  • Thanks 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...