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

    • That would be nice, if excel could refresh pivot tables without bugs. Frequently you refresh a pivot and all parameters get lost. Now this will happen automatically. Bravo MS!
    • If one could ever put all the crap of the world in one box, that would be Microsoft.
    • The most corrupt and vile CEO any company ever had ! The only company that makes an insane amount of money decade after decade but doesn't deliver on even barely passable quality to customers, screws over partners and treats employees like trash
    • PSA: Some other versions of Windows are losing support on October 14 too by Usama Jawad All of us here at Neowin likely know pretty well by now that Windows 10 is reaching end of support on October 14, 2025. You can extend support through paid and "free" means, but if you don't, you won't get any more security or feature updates following the aforementioned date. We also highlighted that the Long-Term Servicing Channel (LTSC) version Windows 10 22H2 is also reaching end of support on that date. Now, Microsoft has reminded customers that yet another variant of Windows is reaching end of life on October 14, 2025 too. On the Windows Release Health dashboard, Microsoft has published a reminder that the Enterprise, Education, and IoT SKUs of Windows 11, version 22H2 will hit end of support on October 14 as well. It is important to keep in mind that the Home and Pro variants of Windows 11, version 22H2 already reached end of life on October 8, 2024, and the extra year of lease on life will end for other SKUs within a few months too. Windows 11, version 22H2 for IoT, Enterprise, and Education was released on September 20, 2022, which means that they would have received just over three years of support by the time they "die", compared to the regular two years for Home and Pro. Customers on any of these versions should consider upgrading to version 23H2 or 24H2 as soon as possible, which have end of support dates of November 10, 2026 and October 12, 2027, respectively. Staying on a supported version of Windows is crucial as that allows you to receive regular security updates on your machine. If you're an IT admin, you should immediately begin planning a migration to a supported version of the operating system, and if you're an employee or someone using these versions of Windows in some other scenario, go to Settings > System > About and check out Windows Specifications > Version.
  • Recent Achievements

    • Dedicated
      Profit earned a badge
      Dedicated
    • One Month Later
      hhgygy earned a badge
      One Month Later
    • Week One Done
      hhgygy earned a badge
      Week One Done
    • One Year In
      NIKI77 earned a badge
      One Year In
    • Week One Done
      artistro08 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      632
    2. 2
      ATLien_0
      237
    3. 3
      Xenon
      167
    4. 4
      neufuse
      146
    5. 5
      +FloatingFatMan
      123
  • Tell a friend

    Love Neowin? Tell a friend!