Why would a remote unpair itself?

[Jon J]

Both remotes unpaired from the den H3. I finally figured it out and easily re-paired them. Does this happen often?

 

[Bobby]

Not often but, obviously, it does happen...

 

[Jon J]

Possible cause?

 

[Bobby]

The ether...

 

[charlesrshell]

Never happened to me.

 

[dweber]

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.

 

[HipKat]

My 50 remote kept unpairing. finally got to the point that as soon as I paired it, within seconds it would unpair... now it's in a landfill somewhere...

 

[JS_racer]

all mine unpaired on the 504 update on the hopper 3, was spooky when nothing worked after the forced update.
40, 50 . 2x 52 all didn't work.

 

[charlesrshell]

all mine unpaired on the 504 update on the hopper 3, was spooky when nothing worked after the forced update.
40, 50 . 2x 52 all didn't work.

I wonder if DISH quit handing out U504 due to all the issues! I still don't have it yet.

 

[Juan]

Possible cause?

Dead batteries

 

[Jon J]

Dead batteries

Nope.

 

[DisplayPort>HDMI]

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.

 

[Juan]

Sometimes lack of use will do it..I had it happen with a roku I hadn't touched for 6 months