Button press lag when controlling my devices

Hey all!

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!

Reply
30replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Kimberly Static This does not sound normal. Seems a bit like a network latency. Patrick will have the right developer having a look at it. Would you mind posting a list of your network equipment here?

    Like
    • Raphael Sure!

      My router is a Ubiquiti EdgeRouter Lite and the wifi is driven by a Unifi AC-lite that's ~25 feet from the brain. 

      As part of debugging, I ran an ethernet cable to the brain's final resting place above my TV. The ethernet gets to the brain from the router via two TP-link gigabit switches (one by the router to hook up the house, and one within the TV cabinet to hook all the devices up). Same issue across ethernet unfortunately, but that is what it's running with right now.

      Like
  • 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. 

    Like
    • Matt B Makes sense. My IR Extender is right in front of my FLIRC and Tivo though, so I don't think line of sight is my problem. 

      Like
      • Matt B
      • Matt_B
      • 2 yrs ago
      • Reported - view

      Kimberly Static where is the neeo brain relative to the IR puck?

      Like
      • Patrick@NEEO
      • Community Manager
      • Patrick
      • 2 yrs ago
      • Reported - view

      Kimberly Static Do you see any difference in the lag when controlling your device from the NEEO App or the NEEO Remote? Do you see the same lag for all devices?

      Could you also let us know which firmware you are running on the NEEO Brain and the NEEO Remote?

      Like
    • Patrick Yeah, I do see the same lag with I'm using either the remote or my phone.

      I did try out the Neeo Link feature of the remote but it didn't seem to help either - it shows the same problems.

      For the firmware: my Brain is on 0.45.7-bd15897, and the remote is 0.45.6.

      Like
      • Patrick@NEEO
      • Community Manager
      • Patrick
      • 2 yrs ago
      • Reported - view

      Kimberly Static OK, so that does not seem to be related to the connection in between the NEEO Remote and Brain.

      Would you mind sharing some pictures of your setup including the current position of the NEEO Brain? Even though you have tried, I would very much like to make sure that this is not the cause for this issues before putting the developer team on the case. Based on images we can sure help to make sure that is all fine.

      Like
    • Patrick Sure!

      Here's the brain on top of the cabinet controlling the TV and the soundbar.

       

      And, the inside of my cabinet (below and to the left of the first picture) with the IR puck. The flirc is the silver thing on the left and is connected to my Nvidia shield.

       

      Like
    • Does anyone have any other thoughts about what could be causing the lag I'm experiencing?

      Like
    • the only thing I can think off is iR signal and placement. Assuming you’re not sending commands to your TV and then via HDMICEC to the controlled device. But I’m sure the NEEO guys can figure out why there’s a delay.

      Like
      • Patrick@NEEO
      • Community Manager
      • Patrick
      • 2 yrs ago
      • Reported - view

      Kimberly Static Are you seeing the same lag on all devices that you are controlling? That would indeed be strange and I would have to put a developer on the case. Since you see no difference when using the NEEO App or when using NEEO Link, I do currently not think it is related or networking issues or the connection in between the NEEO Remote and Brain. But since you are controlling different devices, I do also assume that it is not related to the IR codes, if you see the lag on all devices.

      Like
    • Patrick Yes, all of my devices are exhibiting similar behavior. Most noticably they all have the same click + hold lag where scrolling continues for a moment after I release the button (I tested this on my tivo, shield, and my soundbar).

      Like
    • Kimberly Static although this might feel like lagging I’m pretty sure this is because some queuing mechanism. I think your last reply could be very helpful in finding a solution. I’ll do some tests to see if queuing is a general issue or that it’s specific to your unit or setup when I’m home.

      Like
    • Niels de Klerk You know, that would make some amount of sense. Over the weekend I accidentally mashed a bunch of buttons at the same time (AKA I sat on it for a few seconds before I figured out what was happening :) ) and even after I got up there were still chains of commands firing (with a modest delay in between each one, as reported) for around 5-6 seconds. 

      A silly way to learn something, but whatever works.

      Like
    • Niels de Klerk Patrick

      I can confirm that the lag I'm seeing is not a network latency issue - I set up command forwarding to my local PC and can see that my box is getting the commands within a few ms of the button press.

      Hopefully this helps narrow it down for you guys if you're still looking in to this. I'm not sure if the neeo API is able to report real-world latency time but I'm happy to run some tests if you need it.

      Like
      • Patrick@NEEO
      • Community Manager
      • Patrick
      • 2 yrs ago
      • Reported - view

      Kimberly Static Would it be somehow possible for you to take a video where we see you sending the commands and the devices with the lag? That would help me a lot to explain to the developer team.

      Like
    • Patrick Happy to! See attached video.

      The lag between single keypresses and the screen updating is not super clear, but the click and hold lag during the 2nd half of the video should be pretty easy to see. 

      If you guys need anything else from me, please let me know!

      Like
      • Patrick@NEEO
      • Community Manager
      • Patrick
      • 2 yrs ago
      • Reported - view

      Kimberly Static Thanks for that. Our developers are looking into this. I hope I can soon let you know about a fix.

      Like
    • Patrick Howdy, any change there has been any progress on this front? Just to update, I've gone through the latest updates but this issue is still present.

      Like
    • Kimberly Static As Patrick isn't online. i'm tagging Jeff , maybe he can tell you more about the status.

      Like
  • I forgot about doing the tests, looks like the iR signals are queued.

    Like
  •  .25 - .5 a second lag is not bad if you compare it to 5-15 second lag (if I get a response at all) that I'm experiencing.

    Like
    • Andris did you create a post  for that?

      Like
    • Andris Kimberly Static Last Friday we were able to reproduce a configuration that also showed some lag. We have a backup of that config so we can permanently reproduce. I’m confident that this can be identified and resolved. It’s happening only in some very specific setups so we might reach out to you with some questions while we are identifying the root cause. Thanks

      Like
      • Andris
      • Andris
      • 2 yrs ago
      • Reported - view

      Niels de Klerk Yes, I've been discussing this with the NEEO team here ( https://planet.neeo.com/r/k9k3wt ) but somehow the conversation dropped off.

      Like
  • 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!

    Like
  • 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.

    Like
    • Mike Whooley I've noticed that! I didn't realize it was a firmware issue, I thought I was going crazy. Yeah, that has been really annoying.

      Like
    • Kimberly Static Same here! :) Even more odd, is that the physical button presses don't reset the 'sleep' timer.

      So if you're holding the remote still and changing channel, the Remote can go to sleep, then the next press wakes it but doesn't get sent. It seemed like random button presses were slow or weren't getting through at all, but there's a reason for it. 

      They say they'll have a fix in the next release.

      Like
Like1 Follow