Webhook and Scripter-X Events delay

[frankythedog 5]

Hello,

I'm using Android TV on a Xiaomi Mi Box S 3rd gen.

On it, I've installed both versions of Emby Client.

- Emby for Android TV (Beta)
- Emby for Android (Beta)

When a video is played on the first version (for Android TV), a webhook and the event in Scripter-X are triggered almost immediately.

With the second version, the webhook and the event are only triggered when the video starts, or after approximately 30 seconds.

I use this mechanism to send a Wake-on-LAN notification to the relevant NAS.

With the first version, it's very fast, but with the second, this delay is quite annoying (and incomprehensible).

Why this difference, and will this principle ever apply to the "Android TV" version as well?

Thank you in advance for your help and keep up the good work.

[Luke 42077]

Hi, it is intended to be a notification that playback has successfully started, so the client waits until the video player has signaled that, and then it reports that to the server. Based on that intended design, it sounds like the TV app is actually reporting too early (e.g. before playback has successfully started).

I know that's not the response you wanted to hear. It sounds like what you want is an additional notification that would fire when playback is requested, but before we know that it will actually successfully start to play or not.

[frankythedog 5]

Hi,

 

Indeed, a notification when the user presses the Play button could be useful for home automation and/or enable certain actions to facilitate reading, such as sending a Wake-on-LAN command, as I do.

 

 

[Luke 42077]

OK so maybe a playback requested event then. Thanks.