Harmony Remotes

[bevhoward]

I think this event will make a good case for having the ability for users to run a simple utility in order to run "known good" usb update of their remotes from their pc with no server connection.

Beverly Howard

[SandManx]

Has this kind of problem ever occured before?  I just purchased the remote a couple of days ago so I'm confident I can get my money back.  They're only $130 on Amazon now but when I first started looking they were around $250.  I would be a bit upset if I owned it for a while and it quit working when Logitech did an "upgrade".  I'll at least post a review on Amazon telling people not to buy until Logitech fixes the problem.

[dupfold]

I've got exactly the same 'repeating command' problem!

I've had my 885 for over a year now but haven't updated since I first got it. Moved my sat downstairs now and so tried to add that to the 885 but this has caused all sorts of nightmares!

[bandb]

I for one have had my 720 for over a year and had it nicely customized to my needs. It has gone completely nuts with double commands and all sorts of erroneous behavior. If all my stuff is lost, I will be most unhappy.

[Hiway49]

I got this just a few days ago, just in time for all this nonsense to start happening. This is NOT giving me a good feeling about Logitech products. The remote itself is cool, but that software is among the worst and most counter-intuitive pieces of software I've ever used. I'm getting repeat commands everywhere, this thing is now useless. I'm outraged. There needs to be a fix right now, this might be acceptable for a $20 cheapo remote, but not this one. I expect better, I paid for better.

[Transman]

Change the setting to the biggest number not zero, it fixed mine!

[alexruffell]

Looks like they got the instructions backwards where it says to pick a lower number 2 to 0 to eliminate the repeating commands. As the previous poster said, my remote stopped repeating commands as soon as I set it to 5. I think this bug was introduced when Logitech switched from using the more logical millisecond delay time to a 0 to  5 setting (this might be easier for people who don't have a clear understanding on what a millisecond delay is, but I wish they had left both). I wonder if the issue will come back as soon as they fix their software and our "5" setting will cause it to repeat. Anyhow we now know what to do! Thanks Transman!! I was trusting the instructions and had not attempted to do the opposite.....

[SandManx]

I tried setting mine to "5" as suggested but still seem to be having the same problem.

[alexruffell]

I am not sure if this had anything to do with it but I went to the download software + firmware page and updated both my software (7.5) and firmware (4.4.2) then updated my remote and set both my cable box's setting to 5 and the A/V receiver's setting to 5 as well. They both stopped repeating all commands. Try that and see if it makes a difference. Hopefully Logitech will fix this bug soon (I am hoping that the recent release of 7.5 was not supposed to do so as the problem is surely still here....) and in which case we might have to go back and change the setting to the default 3 (or lower).

[SandManx]

Thanks for your suggestion.  I ran an experiment; I verified that I have 7.5.0 software and 4.4.2 firmware.  I tried setting everything at "0", checked the operation and the set everything at "5" and checked the operation.  With the delay set at five commands consistently repeated twice.  With the delay set at "0" commands repeated anywhere from 0 to 3 times. 

Maybe it has something to do with our devices?  I have directv hrr20-700, pioneer 4340 tv, xbox360, polk audio rmds1 and impact acoustics fiber switch of some sort. 

Anyway I'm just disgusted with the whole situation.  What makes it worse is that it worked great for one day and before Logitech broke it.  I can't believe that this is that hard to remedy.  I suspect they don't care and just didn't want to work on the weekend.  I wish I had that luxury!  The bottom line for me is that they said it would be fixed by Tuesday.  I'll give them until Wednesday and if it doesn't work I'm sending it back and looking for another solution.  I hate the thought of going back to programming a Pronto but at least it worked!