No, the problem is purely with the way the CM15A reports some of the RF codes.
Since it handles commands, macros, etc. OK, it obviously understands the protocol and acts on the RF codes correctly but merely screws something up when reporting RF activity. More RF data from the CM15A might point to where it's screwing up.
Other devices seem to adhere to the protocol.
