Strange behavior from MCE remote.

[blade]

I don't really have a question, but thought I'd post something very odd that happened to my MCE remote tonight because I've never heard of one doing this before.

I was using the remote and all was well. I went to eat supper and came back 15 minutes later and Sage wouldn't acknowledge any commands from the remote (btw I'm using a USB-UIRT). Come to find out my remote is no longer sending 2 codes for each button. Instead it is only sending 1 code and the codes are different from anything it has sent before.

I linked the new codes to Sage commands and it is once again working with the USB-UIRT. I have another client using an MCE receiver and the remote has always worked with it; however, now that the remote is acting strange it no longer works with the MCE receiver and Sage's built in support.

I know the MCE remotes are known to have a few odd issues so I'm going to remove the batteries and let it sit for a few hours to see if it fixes itself.

[Opus4]

The last time I heard of a remote suddenly sending completely new codes, I think the moral of the story was that it needed new batteries. (Unless your MCE remote can somehow be configured to send a completely different code set.)

- ANdy

[blade]

I thought of that and changed them, but still the same thing. I even got my multi-meter and checked the voltage of the batteries to make sure they were good. Something very funky has happened to it.

I know the MCE remotes had a problem where they'd stop working completely and removing the batteries for awhile would get it going again. I'll be curious to see if it goes back to normal after it sits without batteries for awhile.

[blade]

Well after letting it sit for an hour without batteries it's now working properly. My only complaint about my MCE remote has been the occasional oddity that requires removing the battery and letting it sit.

[evilpenguin]

They're so cheap, I should just buy a spare for when the first one starts acting up