You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried this with 2 different hubs, with both an AV receiver and a TV, and get the same results.
If my H command is set to repeat of 1, I get a burst of Volume up, or down commands. The AVR move 3 ticks, and the TV moves 2 ticks. So, I think the Logitech Hub is sending a burst that is interpreted differently depending on the device. If I increase the repeat value, it increases accordingly, but always gets the same number of extra ticks it does when set to 1.
If it matters, I'm trigger the H command with an HTTP in node, GET method but get the same results with a timed "inject" node.
Oddly, if I send a mute command, it doesn't toggle repeatedly. I expect this is because the TV or AVR itself "debounces" this signal to avoid toggling on/off rapidly if someone holds a button too long.
The text was updated successfully, but these errors were encountered:
Bit late in the day, but I saw the same issue. I have created a fork https://github.com/marsjupiter1/node-red-contrib-harmony
this tries to solve the issue in H command by allowing a lot more tweaking of what it does. Can't get it to work like that though.
However I have also added H press and H release amongst other things and this solves the issue for me on a couple of devices where I was the issue. Just connect a press and release node and it works. Doesn't make a lot of sense to me at this point.
I've tried this with 2 different hubs, with both an AV receiver and a TV, and get the same results.
If my H command is set to repeat of 1, I get a burst of Volume up, or down commands. The AVR move 3 ticks, and the TV moves 2 ticks. So, I think the Logitech Hub is sending a burst that is interpreted differently depending on the device. If I increase the repeat value, it increases accordingly, but always gets the same number of extra ticks it does when set to 1.
If it matters, I'm trigger the H command with an HTTP in node, GET method but get the same results with a timed "inject" node.
Oddly, if I send a mute command, it doesn't toggle repeatedly. I expect this is because the TV or AVR itself "debounces" this signal to avoid toggling on/off rapidly if someone holds a button too long.
The text was updated successfully, but these errors were encountered: