I guess this is the first time I've done this type of setup..it's temporary, but..

T2C and RP1 in master are hunky-dory.

Cabinetry not arriving in time is preventing full setup in family room, but I wanted to give them a quick remote solution, so just needed an additional T2C to control cable box, Integra receiver, and Elite plasma. No processor, only temporarily, just didn't want to set it up yet.

Set family T2C to standalone in device properties and seems to be goofing with the master system upstairs.

Had to run out but will be back tomorrow. Was it me or did I forget something?

Also, on the subject of setting up multiple processors later, I should go into device properties and specify the processor it will address, correct? With the URCs each one would get it's own "number" but in the RTI world that is just assigning it to a processor, correct?

Thanks!

This is from memory and I'm out of town so I can't double-check, but I think that there are also overrides for each button. So, if you set them both up the same way and had it set per each button, you have to change each button back to stand alone.

CJ

I thought the same thing but I decided to check since I do very little completely stanalone devices.

I found that if I right clicked on the page away from any buttons it changed the output properties for the device globally, however, if you copied over a device that was calling system macros, it will still call those system macros on the processor via the trigger codes. It will not convert a system macro to a standalone macro because that macro is on the processor. It will only change the property of the button and any IR codes placed directly in the button macro. So... perhaps you are unintentionally calling system macros or when you changed the output in the device properties you accidentally clicked on a button or overlayed graphic and changed only the property of that object.

If you have a processor in the system... then by default the remote will assume that you want the commands to not be standalone. If you click on properties for the remote you have an output tab. Set it to the processor you want it to default to... in the bottom section.

Every button that was set to system default will be changed to stand alone with what you've already done. If the button wasn't in the output mode "system default" it wouldn't have changed. Even if you change the buttons to standalone it will continue to send via RF triggers to any place you've listed a system macro in your macro list on the handheld.

My suggestion would be to do File, Save As, (make a second file), then remove the processor and put the remote in standalone. If there are any issues then they'll show up in red lettering when you look at your macro. Plus it will be easy to revert back to the original file whent the time comes.

Good tips. As always, you guys are tops. Thanks for the help!

Don't make the mistake that I did. Same sort of situation. Temp setup of local theater, and in my infinite wisdom I started a second project for the rest of the house thinking I would just import the first remote when I got a chance. Bad idea, I think the trigger codes were the same in some cases and the remotes were messing with each other. 1 project file for everything. (probably goes without saying, but I usually find a way to mess something up. )