Button press lag when controlling my devices
While using my Neeo, I've noticed that there seems to be a bit of lag ( .25 - .5 a second) between my pressing a button on my remote (via either the remote or the Neeo app) and the action actually occurring on the device.
For most commands this is hardly noticeable, but it has made navigation fairly difficult. Delays on single button presses are fairly okay, although at times it seems that the remote doesn't quite keep up (Ex. if I press the button three times in quick succession, it only catches 1 or 2 of them).
The worst offender is when I'm pressing + holding to scroll though lists. When I release the button it's ~a half second before the scrolling actually stops, which makes it very difficult to actually navigate down long lists. I'm constantly scrolling back up or down (slowly, because the buttons don't respond quickly) to find the item I'm looking for.
My two primary devices (a Shield TV controlled via a FLIRC and a Tivo) both exhibit this behavior, so it doesn't seem localized to a specific device. If it's relevant, they're both in a cabinet with the IR extender - though I did try moving the neeo brain into the cabinet instead of the extender and it exhibited the same problems.
This is a pretty annoying issue and is the main reason I'm not fully enjoying my new Neeo. I'm not sure if there's any fix that would make this easier, but please let me know if I'm wrong! If not, I'm hoping there will be future enhancements in this area or further user customization (debouncing time? Total guess) that will help clear this up.
Thanks for your attention!
I also found this issue with the IR blaster plugged in and the brain and IR weren't in line of sight(ish). Example for me was trying to control volume on my soundbar and was getting terrible response and button pushes that did nothing. I have the IR blaster just at the front edge under the fireplace mantle to provide better line of site to the sound bar under the TV. But if the brain was pushed too far back on top of the mantle. Well. It was trouble. I moved the brain up to the edge and instantly had way better response. Something tells me they need to literally see each other.
I've updated to the latest firmware but unfortunately the issue does not seem to be resolved with the update, unfortunately. It miiight be a little better, but since it's still laggy and being unable to compare with the old version means it's hard to tell. Raphael did research ever continue with this issue? Thanks!
FYI, there is a known issue with the new firmware that the first button press after wake is ignored. (i.e. if you hit one of the buttons to 'wake' the Remote, it'll wake but the command isn't sent. If you wake the Remote by picking it up, then pressing the button, it's fine).
This isn't exactly the same issue, but might make it seem worse.