Is there a technical reason why a MX980 remote (via RX250) can not send serial and IP commands via a MRX2/MRX1 or is it that the feature has not been added to the software in CCP and on the remote(software/firmware)?

Or the big if ... have I missed something and it is possible? Given it can be done iOS module the areas of concern would appear to be remote firmware, data file configuration downloaded to remote, and RF protocol since it would be sending full string and not triggering like MSC400.

If it is not possible today, is it being considered as enhancement to Complete Control Remotes?

yes, the mx980 is not a network based remote.   only the mx5000, mx6000, KP4000, and the MXiOS app can send IP commands.   You don't even need the MRX1/2 to do IP commands with those remotes. (except for the MXiOS)

It will never be possible to do what you want to do with the MX980 and MRX1/2.  They would have to build a new basestation similar to the MSC400, but give it network capability.

I don't see them doing that any time soon though, since Total Control seems to be getting the majority of attention.

Just to be clear it is not something I need/want to do (I've got msc400 and MRX1/2) -- just a point for discussion.

I think that base station could be a MRX1/2 with RFX250 or other RF device. The Remote would not need to be network enabled just communicate with a network device (with firmware mods to support). You're right it will not happen but missing piece seems most likely to be that RF protocol and does not support encapsulating message so MRX1 could de-encapsulate and route as required.

Again, it is just a thought not to disagree or start a debate.

How do you expect an RF device to send an IP command? It has to have some native feature to the network to allow this. I mean the mrx-2 is like $400 bucks. Do you really expect to have this sort of functionality or chip set? You can't even walk into a URC networked remote for under ~$1000.

The weak point here is your old remote. While the 980 is a great piece, it's been out almost a decade. Do you have any other decade old equipment you are trying to force to work in a modern way? I don't expect my pronto ts1000 to send network based commands. :-)

Firmware doesn't fix everything. In urc's case, it usually breaks something the first few times.

Again not wanting to disagree or do anything my ancient equipment doesn't do -- I have no trouble upgrading (in fact just did it by adding MRX2) and moving forward -- my technology budget shows it. :-)

But back to discussion, think of the way an MX980 encapsulates an IR command (simple binary encoded data) with port routing and sends it to a RFX250 where it is forwarded to a MRX2. The MRX2 de-encapsulates the signal, reviews for routing, and sends an electrical signal to appropriate emitter where it becomes IR. Assuming the RF protocol is not hardware locked at RFX250 (even that could be made to work with upgrade), an MX980 could send an IP or RS232 (with firmware support since it is simple binary data) command with IP/ RS232 port routing that MRX2 could output via it's Ethernet or an RS232 port via same process. This is the basis of network protocol stacks such as IP and protocol conversion exists in countless forms.

I never thought it would happen or have a clue if it could make financial sense for URC with the CC vs TC lines. Just intellectual curiosity.