Dokładnie tego używam. Z najnowsza aktualizacją i problem występuje.
Zresztą chodzi o oprogramowanie samego pilota a nie program którym się go programuje. Sprawdziłem to na dwóch pilotach, jak dzwoniłem na infolinie to pracownik sprawdzał moje zgłoszenie na swoim domowym pilocie, robili również testy na kilku sztukach, które posiadali każdy zachowywał się w ten sposób. Ja to określam jako na 10 naciśnięć fizycznego guzika kiedy pilot jest wygaszony, 2-3 nie zaskoczą i nie obudzą go. Dodatkowo czasem pilot się wybudzi ale nie wyśle sygnału do urządzenia. Tutaj dokładnie to jest opisane, test z 2009:
"There is another problem with the firmware that is far more annoying and problematic. It is a fairly serious flaw. When the LCD on the remote is lit, then when a hard button is pressed a device command is sent. The device command is sent every time, as it should be. However, when the LCD is not lit and a hard button is pressed, the LCD always lights up, BUT the device command is only sent some of the time! This inconsistent behavior seems to be random. I have yet to find a way to cause this problem to occur consistently. I have pressed the same button 10 times in a row, allowing the LCD to go out in between presses, and had the remote fail to send a device code each time (you can tell when a device code is not sent because the device activity icon doesn’t light up and the device doesn’t respond). Then, after that, pressed the same hard button repeatedly, and had the remote send the device code each time. This problematic behavior seems to occur with every hard button, and ONLY when the LCD is off. Since the LCD is coming on each time a button is pressed, it is not some sort of hardware failure - the button presses are being sensed. Apparently there is some inherent design problem in the firmware causing this. The bottom line here is that the remote can be a nuisance to use. For example, if you are scrolling through a channel guide, you may press the down button a few times, pause for a few seconds to read information about a show (during which time the LCD turns off), then press the down button and… it didn’t work! So you may think that you need to press the button again. But wait! Perhaps it did work and the satellite receiver is just slow in responding - so then you don’t want to press the button again. There’s no way to tell except to wait for a while, see what happens and respond accordingly. This is not what I want from a remote! Unpredictable, inconsistent behavior should never occur with these kinds of computerized devices. Currently this is happening on my remote quite frequently, perhaps 25% or more of the the time. It is apparently a major firmware design/implementation flaw that should have been corrected long ago by Logitech."
Strona:
RC User Reviews: Harmony One Remote Control (1)
Przyznam, że przez tą przypadłość mocno się rozczarowałem na tym pilocie, nie wiem czy bym go w ogóle kupił wiedząc o tym. A szkoda bo poza tym jest to naprawdę bardzo udany pilot. Logitech Polska twierdzi, że tylko większa liczba tego typu zgłoszeń może wymusić na producencie rozwiązanie tego problemu.