Setting correct input delays on Harmony remote


Recommended Posts

I've got a Harmony 550 and a Samsung SlimFit 30" TV

To switch inputs on the TV, I have to go into the menu and scroll through them. Initially, the remote would pause for about 500ms between key presses, so it would scroll through the inputs list rather slowly.

I went into the harmony app and brought up the speed delay screen for the TV. I set the inter-key and input delays to 100ms. However, this only seemed to make things slower. The remote now paused about a second between 'key presses'. Well, the light would stay on for the whole second, so I'm not sure if it sends the signal and then waits a second, or if it sends the signal for a full second before sending the next one. Either way, it got slower, not faster.

So I went back in and set both delays to 0ms. Now the delay is closer to 2 seconds. This isn't making any sense. Can someone help me out here? What's the difference between the inter-key delay and the input delay? When is each delay applied?

did you mean "enter-key delay" and "input delay" ?

since I'm putting together a home theater with my roommates, I've been reading up on Harmony remotes. And by what I have read:

"enter-key delay" is the amount of time it takes between key-press and sending the signal to the device.

"input delay" is the amount of time it takes to switch from one device to another.

but by what you said... it sounds like the timings are wrong. If you don't remember what you've changed.. I would suggest starting from square one... wipe the remote and set it up again.

I should be getting my Harmony 360 by next week (I hope), so maybe I could give more help by then.

not quite. after some searching on logitech's support site, I tracked it down:

Power On Delay. When a device receives a PowerOn command, it takes a certain amount of time to "warm up" the device and resume normal operation. For most devices this happens very quickly, but for some devices, such as televisions and receivers, it can take up to 3000 milliseconds (three seconds).

Inter-key Delay. When a device receives an infrared command the device is considered"busy" while it processes the command. The amount of time required before the device will respond to another command is known as the inter-key delay, and normally ranges from zero to 300 milliseconds. Devices with long inter-key delays take longer to respond to multiple infrared commands (e.g., when changing television channels).

Input Delay. When a device switches inputs (e.g. goes from Video 1 to Video 2) the device is considered "busy" while it processes the command. The amount of time required before the device will respond to another switch input command is known as the input delay, and normally ranges from 500 to 3000 milliseconds. Devices with long input delays take longer to change inputs.

Inter-Device Delay. When an infrared command is sent for a particular device, each device in your system will receive the command, but only one will respond to it. The other devices will ignore the infrared command. Sometimes, when this happens, a device will ignore the infrared signal and then stop accepting infrared commands for a period of time. This period of time is known as the inter-device delay. During this time no infrared signals are generated by the remote. In rare cases this delay can be several seconds.

Right now I'm back at defaults for everything. I just swapped out my regular cable box for a shiny new HD converter, and I've been sick the last few days, so I haven't gotten around to changing anything yet. I may try a few things when I get home today.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Elon Musk once again claims Tesla robotaxis are coming soon by David Uzondu Image via Depositphotos.com Tesla's CEO, Elon Musk, has announced a tentative start date of June 22 for the company's long-awaited public robotaxi service. According to a post on his social media platform X, the initial launch will be in Austin, Texas. Musk added a significant condition, however, saying "We are being super paranoid about safety, so the date could shift." The service is expected to begin with just 10 to 20 Model Y SUVs operating within a limited area and with remote human supervision. He also mentioned a plan starting June 28 for new Teslas to drive themselves from the factory to a customer's home. This is a moment many are probably waiting for, though it comes with a heavy dose of skepticism. Musk has made grand promises about self-driving before. This robotaxi network brings to mind the bold claims from all the way back in 2019 when the company said a similar service would launch the following year. That evidently did not happen. Federal regulators also have their doubts. Last year, the National Highway Traffic Safety Administration criticized Tesla for making its "Full Self-Driving" feature sound more capable than it actually is, demanding the company align its marketing with reality. Tesla is also driving into a field that is no longer empty. Waymo, Google's sibling company, is already a major player, offering hundreds of thousands of paid rides per week across Phoenix, San Francisco, Los Angeles, and even Austin. The company is so far ahead that it has begun testing in Tokyo. But being ahead means Waymo is also the first to face certain dangers. For example, on the evening of June 8, a group of protesters in downtown Los Angeles summoned Waymo vehicles during a demonstration. When the vehicles arrived, they slashed the tires, smashed the windows, and spray-painted the cars before setting three of them on fire. Which raises a thorny question for Tesla: if you can summon a car with no one inside, can you summon it just to destroy it? It's one thing for protesters to stumble upon a robotaxi and vandalize it; it's another for someone to use the app to call a driverless car to a secluded spot for a planned attack. With public sentiment around Musk so divided, especially given his DOGE shenanigans and his recent face off with Donald Trump, that's not just a theoretical problem. We've already seen this hostility play out in attacks where people vandalize Teslas, carving swastikas into them and spray painting slogans like "Burn More Teslas" on walls.
    • This is actually quite useful. But why wouldn't they implement this in the local file system? The code is obviously all there now... maybe in 5 years.
    • The new "Story Cards" in the Software section are nice, but I wish they had the product icon included. I use this section to identify updates for software that I use regularly, and it's sometime difficult to identify the software without the product icon. Thanks for your consideration. pelaird
    • Mozilla really needed to focus on their core product for a while now. I will not mourn the death of pocket or AI garbage. One thing they don't do that I believe they should is advertise more, and not just to their core audience, especially their additional services. Let people know they actually exist.
    • Is this like tailscale?
  • Recent Achievements

    • Week One Done
      Food-Beverages-Nutrition earned a badge
      Week One Done
    • Week One Done
      Tech Dogs earned a badge
      Week One Done
    • Enthusiast
      computerdave91111 went up a rank
      Enthusiast
    • Week One Done
      Falisha Manpower earned a badge
      Week One Done
    • One Month Later
      elsa777 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      524
    2. 2
      ATLien_0
      271
    3. 3
      +Edouard
      199
    4. 4
      +FloatingFatMan
      196
    5. 5
      snowy owl
      138
  • Tell a friend

    Love Neowin? Tell a friend!