All Quiet on the Western Front

David Li wrote:

I suspect it's a timing thing
Ensure your SmartRemote is on a static set IP (not DHCP). This speeds up network handshake.
It's a tradeoff of never go to sleep (and kill the battery) and fast pickup response.
It wakes up pretty darn fast as it is.
 

Thanks for the suggestion.  It is on a fixed IP address.  I'm glad the battery life is much better now with the screen shutting off.

When a key is pressed and the remote wakes up, is it possible to act upon that keystroke and not discard it?  Having behavior that varies depending on when a key is pressed and the remote is moved seems problematic.  I often have the remote on the arm of my sofa and I just tap a key without picking it up.  Sometimes the initial keystroke is discarded, sometimes it isn't if I bump the remote slightly.

Thanks for the suggestion.  It is on a fixed IP address.  I'm glad the battery life is much better now with the screen shutting off.

When a key is pressed and the remote wakes up, is it possible to act upon that keystroke and not discard it?  Having behavior that varies depending on when a key is pressed and the remote is moved seems problematic.  I often have the remote on the arm of my sofa and I just tap a key without picking it up.  Sometimes the initial keystroke is discarded, sometimes it isn't if I bump the remote slightly.

Once programmed, I have found these remotes to be excellent.  I have nothing to complain about and have it doing everything I need.  However, I also have the slight inconvenience of often pressing hard buttons twice, once to wake up and the other to actually execute the button press.  If the button press could wake up and send the command, that would really be amazing!!

If I'm holding it, I give it a shake first. If it's on the table I poke it to wake it up then press a button. It would be nice not to have to though.

It may technically be possible to have the first button push (not web page click) to be recorded locally on the SmartRemote and then after a WebSocket is connected to myServer, send it.

But...it's a timing thing as the Android OS on the SmartRemote on wake up starts up both Javascript AND the Websocket connection.  Both need to be up and running to send info to myServer.  The javascript needs to be running first for this to work.  So, maybe it will work, maybe sometimes.  Maybe no help.  Needs to be developed and tested.

I am curious as to how much battery draw would occur if we left those stuff enabled? The biggest battery draw is the screen, so that would still need to be turned off, of course. And have some way for the user to put the remote to sleep would be desirable.