Channel changes more than once when button pushed once

I see this all the time both with my dvr (VIP2250) and to a lesser extent with my wireless receiver (ISB7005).  The behavior is similar to "keyboard bounce" you can sometimes get on cheap keyboards where you press a key but it sends multiple times.

It's hard to reproduce this at will (like trying to test it out for this reply) but it appears the problem occurs for all remote models (silver/s10/s20, probably S30 to, don't have one of those but its basically the same as a S20).  It's also hard to know who is alt fault.  Is it the remote itself?  Is it the receivers?  I'm inclined to think it's the receivers, either the IR sensor code circuit (i.e., hardware) or the way the receiver software handles the IR signal.  In either case I would expect "debounce" logic to handle that condition (i.e., when the same signal is detected within a few milliseconds ignore the additional ones).   It's odd it doesn't happen all the time but that may be dependent on the response time of the the receiver, i.e. is it busy doing other things at that moment (e.g., accessing the network which is certainly a variable).

I've learned to expect it and live with it as frustrating as it is.

Note, in the "early years" I don't remember this problem occurring.  It could have been a receiver change I got but I have a foggy memory (getting old, a lot of foggy memories) of this starting to occur after a software update.  This was some time ago (years) and there hasn't been any software updates to the dvr/receivers in almost 2 years now (still waiting for them to fix the Favorites loss of position bug, but I digress).

I have another "off the wall" theory for this too -- literally "off the wall"!   The IR signal is bouncing off walls (or other things that reflect IR) and thus more than one IR signal is arriving at the receiver (albeit I would think microseconds apart).  It may be speed of light but its still not unlike a "bounce" that debounce logic would be able to handle.

Bottom line, no solution.  You need to live with it and expect it (and be ready to get frustrated with it...again).  That fact that there has been no software updates in almost 2 years when before that you could expect them annually (around November) leads me to believe att just doesn't care any more.  They are too busy updating the directv stuff to bother with uverse any more.  Maybe they think that if they continue to make the uverse experience frustrating enough (no updates, very minor promotions for existing users, no managing the dvr from a website for computers any more, etc.) they will want to turn to directv.  If they are really  thinking that I don't know what they are drinking! 

Hey, this turned into a rant.  Sorry.

I was able to work around this by placing a few strips of clear tape over the IR receiver window on the front of the DVR. Start with 1 and add another 1 at a time until it's better.

Did you hold the button in?  I found that if you press the button and release it the channel will change one channel at a time.

Had already tried this per other users' suggestions here but it didn't work. Turns out I taped the wrong spot on the box. 

The IR sensor is VERY hard to see. With the flashlight on my phone I saw what looked like two sensors just to the left of the arrow keys , between them and the menu button. These aren't the IR sensor. Go further to the left, just to the right of the red record light. I couldn't see it until I used a brighter LED flashlight aimed at just the correct angle. 

Been less than 24 hours but it seems to have helped. Put just one piece of scotch tape over the area. No problems yet. 

Well, it was nice while it lasted. The problem is back. It seems to happen only when the DVR is recording something.