Hi ArticWolf, thank you for the reply. Sometimes it will wake up in a second or so other times it will take 5+ presses and 5 - 10 seconds to respond - although the keyboard has lit up after the first press. Is this normal ?
You're welcome
.
Have you tried going through the re-pairing procedure first & foremost? (It's printed on the quick start guide included with the remote or just open the user guide at the following link for the instructions....
https://theminixforum.com/index.php?threads/neo-w2-info-sheet-and-user-guide.141/ )
Sometimes this is all that's required & problem solved
.
What Windows device are you using the W2 with such as one of the MINIX Win mini PC's? (Although, it should still function normally with any Win 10 device & other Win OS's as it communicates via the supplied USB dongle alone rather than using IR .)
Otherwise, no, it's not entirely normal!! However, a very small minority of other users that own a "similar but different" model "A3 Backlit" (essentially the Android version of a Windows W2) have sporadically reported similar symptoms. Their A3 Backlit's seem to behave in an identical fashion & immediately wake/light up upon the initial button press but it then sometimes takes them an additional 2 - 4 button presses to get the receiving device to eventually respond to their desired input. After that, however, once awake these affected remotes apparently then carry on functioning perfectly normally again until they re-enter the power saving mode again. Having said that, I can only recall seeing maybe 2 or 3 posts of this actually happening with a W2 in the past 12 - 18 months which seems less affected by this particular issue to the more recent A3 Backlit.
Personally, I've used the W2's, A3 Backlit, (& A2 Backlit) remotes too since release & never experienced these issues with any of these remotes used across a number of different Android & Windows devices respectively. It doesn't seem to be a widespread issue & reports have been very random indeed from differing geolocations, & across a broad time spectrum as well. (I.e these remotes aren't apparently appearing in clusters/batches & it's not a common problem with the W2's either going by reported cases.)
Some of these users have kept their remotes & simply carried on just using them & just adapt to quickly multi-clicking a button rapidly if they're aware the remote has re-entered its sleep mode to work around it. Others have obviously exchanged their remotes & otherwise reported their replacement as working fine after that.
Ultimately, it's really up to you on whether you're happy to continue with it as is & workaround or return it to your point of retail for a quick exchange? Obviously the remote is actually functioning but after the initial button press to wake it, it should then immediately respond to any subsequent inputs you make, (rather than several additional inputs being necessary which I could certainly understand as being an annoyance & why you've questioned it).
Let us know if the re-pairing procedure as above works, or keep us posted what you do if that's not successful as to whether you opt for a replacement & that resolves the problem too. (It could prove useful for other members, for example, if the problem persists with a new remote if you're using a specific Win mini PC/PC, etc.
.)