I am working on a MX980 at the moment. It is controlling a basic home theater system in a basement via a MRF350. I am also trying to control a separate Denon receiver's Zone 2 via RF on another MRF350. I have the MRFs both assigned in the RF setup, and the Denon AVRs assigned to their respective MRFs and IR outputs.

Here is the issue: I want to turn on the basement AVR to a single input, and turn on the upstairs AVR's Zone 2 to an input. I can do it manually with the 980, but when I try it with a macro, both receivers' Zone 2 is switching. Any ideas?

Send me a copy of your config and I will look at it..

I have encountered issues with multiple MRF's even with separate ID's, if you separate the ID's by only one it can still bleed thru, i.e. base station 1 set to ID 3, and base station 2 set to ID 4, separate the ID's by more than 1 digit.

I apologize for starting this thread without checking everything first. I have another issue that is causing this one....I will start another thread about it.

Ok....nevermind....problem is still there. I thought I had other issues, but another download to the remote seemed to fix all the RF/IR routing issues, EXCEPT the problem with the macros as explained above. I have control of devices on the upstairs MRF from the basement MX980. No problems. However, when I do a macro that has Zone 2 commands on it for the upstairs AVR, the downstairs AVR still is receiving them as well. Even though, I can go to the page for the upstairs zone 2 and control it fine without the basement AVR receiving those commands. Same commands are aliased in the macro. Weird.....Im not using Zone 2 on the basement avr, so its not a huge issue, but I would like to learn why this is happening.

The RF ID of the device being aliased to is used and not the RF ID of the device where the macro is run. Could this be the issue?

I thought of that. In the RF setup you can assign the Listen page to a MRF350....but not more than one. The buttons the macros are assigned to are on the listen page. This might be part of the problem. But even then, the receivers are connected to different ports on the MRFs. Basement AVR is on port 1, upstairs AVR is on port 4. So the crosstalk shouldnt happen if it was simply sending the commands to the wrong base....since it would still come out the same port....make sense?

simple problem, stupid design issue (that has not been fixed since the first MRF's). Once any mrf device becomes activated by its ID, it will accept commands from any ID numbered device/macro stream. the 2 ways to solve this are to make sure that port routing is used and that there is no cross talk within the port routing scheme...also make sure the IR blaster(s) are set to off or they will cause the problem (same for 'stray' IR signals). Solution 2 will require some trial and error but at last check the ID window is open for approximately 6 seconds so if you set the delay between system ID's to an amount greater then that you should also be able to accomplish your goals.

the follow up of this relative to your last post is that once an ID is open any code from a 'random' or 'rogue' MX remote can go out all outputs (though I have not tested this scenario)