Dpad issues with SmartRemote @davep

I'm hoping that you can weigh in on this one. I have nothing left to try to figure this out.

I have struggled with the dpad on the SmartRemote since launch as far as holding the direction buttons. Originally if you did a long keypress it ran a macro looping a keypress of that direction button a set number of times. You changed this months ago and in theory you should be able to hold the button and it should stop issuing commands upon release of the button.

This is not what happens with my system. I can hold the button and it will repeat the command as expected, but upon release of the button it will keep issuing the command for a variable amount of time where the amount of time depends on how long the button was held for. If I hold a dpad direction for, say, 5 seconds and then release it myServer will continue repeatedly issuing that command for many more seconds. During that time frame you cannot interrupt it and must wait for the server to finish sending whatever commands have built up in the queue before you can do anything else.

Can the dpad be made to work like the Denon volume behavior? For volume up and down the server issues volume commands smoothly, consistently, quickly, and most importantly stops immediately when I release the button.

It would be great if all the drivers worked this way but I don't necessarily need that...but I REALLY need it at least for IR with the ip2ir. Specifically, can that driver be modified to flush whatever commands have built up in the queue/buffer immediately upon releasing a directional button? Holding down a dpad button to scroll is completely useless when it overshoots like this and I can't keep repeatedly pressing the direction buttons to navigate. After 6 months of doing this the buttons on my remote wore out from so many thousands of keypresses.

I'm DESPERATELY hoping that you can help me here. I got another Pi4 myServer to test with in hopes that this is being caused by some change that I had previously made to my system but unfortunately this behaves exactly the same way on a bone stock system with no modifications made to it whatsoever. I really try to avoid wasting your time involving you in things that I can eventually address myself with enough effort but at this point I've done enough troubleshooting that I suspect this isn't something that I can fix on my end. I've already replaced my broken remote as well and this was fine but continuously replacing remotes because of worn out buttons isn't going to be viable in the long term.

Any chance that this can be looked at? I've noticed that a second remote is starting to display the same symptoms as the original failed remote, where some of the direction buttons aren't consistently registering button presses. It's pretty disheartening.

Following this thread closely. I have the same issues (and more ) It's very frustrating and disheartening at the moment.

I don't really expect that this will be addressed. I don't know if it even can be addressed. The lack of even a response after two weeks leads me to wonder if it's a hard limitation of the system. I'm already researching potential replacements and getting closer to pulling the trigger. Opening this thread was really more of a last ditch effort to solve the problem before I sell off my system and move to another platform.

I don't especially want to switch systems. I love these remotes and their flexibility and my wife has come to like them as well. I have a ton of time already invested in this whole endeavor, plus I'm going to take a bath when I sell all this hardware.

At this point I feel like I don't really have a choice though. I still have two fully functioning remotes left but without a means of reducing the number of keypresses it's just a matter of time before these start to fail as well. I don't expect anything to last forever, but replacing $500+ remotes every six months simply isn't rational or sustainable.

I'm holding out hope for SmartRemote2. There really isn't anything out there that meets my needs for sharing variables between two remotes to allow them to function as one system.

I'm a bit concerned about the radio silence... Hopefully it is not an indication that this project has lost steam.

Hi Nillaz,
Can you provide more detail: What is in the myDesigner command for the webpage that is currently loaded for the navigation button you are pressing?
What is in the log when this occurs?
Are you using a custom command?

For example, on the roku.html, If I have the guide up on the TV, I press, cursor moves as long as depressed. I let it up, it stops. That's what I would expect for that use case.

I also use the Channel Up Short to go "Up 5 clicks" with one press. This gets uses a LOT. I use Channel Up Long to go "Up 30 clicks". I use this when going from "middle of the guide to top of the guide, quickly".

These two functions are used extensively on my system (which should be the default behavior) which significantly eliminates pressing the Up / Down nav buttons.