Contributor
•
1 Message
Point Anywhere RF remote
I have a new point anywhere RF remote with the Cisco wireless receiver - the remote appears to be very slow to respond or doesn't respond at all when either Guide or a channel is pushed. What is causing the slow or complete lack of response?
aviewer
Expert
•
3.2K Messages
9 years ago
@djacksonteebox1 - Slow response & no response have two different causes -
Slow response is your STB & software. You can see this if you watch the green light on the STB blink when you send a buttton click from the remote. Any time after the green light blinks is caused by upstream/internal processing.
Some STBs do seem slower than others. But, keep in mind, many actions have to go back through the network to the mother ship & the response comes back to your TV screen. Generally, it is amazing how fast that can happen.
No response is when the green light does NOT blink because the STB does not see the click as a valid IR. There are multiple possible causes -
Bad button contact in the remote.
Weak Batteries. I found the remote to work only when the batteries were fresh. A slight drop in capacity brings iffy function. So bad consider rechargable batteries.
Weak RF - see below for antennas
Weak IR - reorient dongle
Over strong IR - tape over IR sensor on STB
Over sensitve STB IR sensor
I replaced mine when it wore out after five years with a Logitech Harmony Smart Control (now Companion) - https://forums.att.com/t5/Using-your-U-verse-TV/Logitech-Harmony-Smart-Control-Remote/m-p/4028946#M2963 - Offers many more features.
Here are more options - https://wiki.ezvid.com/best-ir-remote-extenders?id=ezirremoteextenders-20&gclid=CPXTl57c28gCFVcSHwodousEYw
More Background -
IR Issues
Going back ten years there are many posts about IR interference. Remedies included taping over the IR sensor, hiding the STB, turning off auto brightness on the TV.
A common fault was the info button press corrupting to an STB mute action. The number of reports of this have totally fallen away. My personal initial primary problem was getting the zero to register. But, one day long ago that just went away.
Niles Audio Corp. makes IR repeaters & has a video on their web site showing the fragility of the IR coding that is used for U-verse & other boxes. They said their new line of repeaters could handle it. Oddly, a U-verse customer posted in this community that they had a NIles install that was not working & after they contacted Niles they did not get any satisfactory resolution.
I came to believe that the IR sensor is too sensitive, That the DVR is worse than other STBs. That command type buttons are worse than the number buttons. That, somehow software updates can make it better or worse, So, it is a moving target. Hard to pin down.
I noticed that the U-verse remote does work better than my Logitech Harmony model 700. I looked at the IR signal through a digital camera. It appeared to me that the Harmony IR signal is stronger than the U-verse remote. This reinforces my theory that the IR sensor is too sensitive.
Recently, my most common problem was FF and Play Buttons often corrupted to chan up and chan down more than six times a night while watching recorded shows, exclusively.
I happened to notice that I had a specific kind of "duct tape" covering the blue light on the STB. Actually, it just looks like duct tape, but is electrical tape available at the Home Depot in the electrical dept. - http://www.homedepot.com/p/Commercial-Electric-2-in-x-150-ft-Vinyl-Electrical-Bundling-Tape-Silver-30002664/202741845#specifications
This tape has a degree of transparency. I thought I would use it to cover the IR sensor. The remote has never worked better. In over 100 evenings since I applied the tape - watching recordings while FF through the ads - I have not had one chan up - chan down corruption . Previously, there would have been at least 6x100=600 occurrences.
Almost all button presses are accepted & none are changed to a different action.
RF Issues
It should not be a surprise, but it is, that half the problems with the RF remote are IR. I run an STB well hidden for a second TV. I had the IR sensor covered with black tape. I replaced the black tape with the "duct tape" & saw an immediate improvement in response to menu buttons. The number buttons were already good - see below for that solution.
The STB using RF must be hidden due to the dongle conversion of RF to IR. If it is not hidden it is subject to the following problems:
IR corruption - Ironically, the RF remote was often offered as a resolution for IR problems. But, if the STB is not hidden nothing has changed to eliminate theI IR corruption problem. If the corrupting light can be seen by the STB IR sensor it will continue to corrupt the IR signal.
If the STB IR sensor can see IR from another remote, it will respond to it.
If another STB can see the IR generated by the dongle, it will respond to it.
Note that hidden means the IR does not see outside light - If you have an optical repeater(like the Niles mentioned above) it is IR subject to corruption. If you have an IR receiver that produces RF to go through a wall, it is still IR subject to corruption. Any optical link open to the room is still open to IR corruption.
Only if the remote is RF (like the point anywhere remote) transmitted to a well hidden device will it ward off IR corruption. The ultimate solution is a wireless remote app. These are available, but incomplete & other devices do not yet support wireless remote. But, the Buddy TV remote can be used for a u-verse STB.
Previously, I found the RF remote lacking in RF power - in the same room, twelve feet away, hidden only by a thin sheet of cardboard. One method to increase RF power is to hold the remote under your chin while pressing a button - using your head as an antenna.
A better way is this antenna placed in the battery compartment - http://www.amazon.com/Cellular-Innovations-A-BOOSTER-Universal-Antenna/dp/B00009WCAP/ref=sr_1_8?ie=UTF8&qid=1366128630&sr=8-8&keywords=cell+phone+booster
With this antenna, the channel numbers are almost always accepted. With the "duct tape" in place, the other buttons work almost every time. The remote now works better than ever.
But, recently, I discovered that weakened batteries triggers poor results due to low power. If the remote starts acting up go for fresh batteries. Before I realized the batteries were low I was getting better RF by holding it against a metal arm of a reading light.
To increase RF sensitivity - Cut off the base and one leg of a wire coat hanger (one piece). Hold the short leg perpendicular to the dongle and wrap the longer end around the dongle a few turns until the two perpendicular ends are about the same length (about 3”). Cut the longer one to the same length as the shorter one.
STB Issues
Once IR and RF issues are resolved, there are timing issues with the STB to contend with. Numbers process fast and Menu items process slow. You need quick, light touch on some numbers to avoid duplicates and a slow, strong press on menu activities. Effort is required to suppress the urge to press again while waiting for a response. It takes concentration to get effective results. Frequently a second press immediately cancels a slow responding first press. Current IR and RF issues amplify the effect of the timing issue.
0
0
ATTU-verseCare
Community Support
•
865 Messages
9 years ago
@aviewer thanks for the detailed information!
@djacksonteebox1, resetting the DVR by pressing and holding the power button for 10 seconds and replacing the batteries are common fixes for slow responsiveness.
If this does not work, send us a message by clicking here. Provide your name, 9 digit U-verse account number, and phone number. We may need more information to be able to take any action within our systems.
at the top right corner of your screen for a response. In the meantime, let us know if you have any other questions or concerns!
Keep an eye on the
-ATTU-verseCare
1 Attachment
envelope.png
0
0
ATTU-verseCare
Community Support
•
865 Messages
9 years ago
Hey @djacksonteebox1,
We have received your private message and look forward to working with you to get this sorted.
ATTU-verseCare
0
0