Why would a remote unpair itself? (1 Viewer)

Jon J

Thread Starter
SatelliteGuys Pro
Lifetime Supporter
Nov 16, 2005
484
323
Music City, USA
Both remotes unpaired from the den H3. I finally figured it out and easily re-paired them. Does this happen often?
 

dweber

SatelliteGuys Pro
Pub Member / Supporter
Jul 29, 2005
1,101
1,186
Plain City, OH
When I updated my software to U504 I had to again pair both my 40 and 52 remotes before they would work on my Living Room Hopper3. But the Family Room Hopper3 did not have any problem with my 40 and 52 remotes when I updated the software to U504.
 
  • Like
Reactions: JSheridan

DisplayPort>HDMI

New Member
Dec 11, 2017
2
0
Westerville, OH
This is totally speculation, so take it as you will. I'm extrapolating from how I know computers work. I think a given remote stores the variable for remote address in volatile memory. Thus, there has to be a constant flow of (small amounts) of power going to said memory, or it'll default back to a factory state. So if the CMOS battery is dead, the remote will lose all information that had been changed since it was first built, and it'll do that every time the batteries die/are changed. If I'm right, short of taking the thing apart and replacing the CMOS battery, or Dish replacing the remote, there's nothing that can be done about it.
 

Users who are viewing this thread

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Latest posts

Top