Delay after Waking up

Just wondering out loud... Is there a way to send a dummy command to the server when the remote comes out of sleep?  There is typically a delay where the first command doesn't work.  The second time hitting the button works fine.

Not a big deal, but it would be a nice have if it was possible (and it solved the problem)

I have noticed this as well. I suspect that the initial command is lost due to the remote being asleep. After the remote wakes up, it can then respond to the next command.

I can eliminate that missed command by ensuring the screen is on before initiating the command (my remote is configured to turn on when it detects movement).

It's a bit weird, after waking up it's hit or miss if the first command goes through. There really isn't any pattern if it works or not. It's not a big deal, just a minor annoyance.

Often, the first touch is to put focus on the screen. The second touch is then understood as the command to process.

That is why I was wondering if you could have the remove do the "first" touch automatically so the second one would fire. Basically send a keystroke that does nothing...

David Li wrote:

Often, the first touch is to put focus on the screen. The second touch is then understood as the command to process.
 

For me, if we're watching something, the first touch is usually hitting the pause button or adjusting the volume, so a hard-button press is being used.  If there is some way to allow configurability to the wake-up function, that would be nice.