NRF24L01 will require programming.
actually it runs on SPI interface. (to send data as well as setup the
chip status.)
so the way i see the structure will be is.
PC (serial/parallel/USB) -> SPI adapter/board -> NRF24L01 (set to TX)
NRF24L01 (set to RX) <-> MCU (to get the command/data from the SPI
bus, as well as doing the initial programming to set the NRF24L01 to
RX states at boot up) -> relay
If you are trying to reduce the amount of programming,
the PT22** might be a better choice.
depends on the module you buy (or your build your own board)
you might have 4-11 address bit, and 1-4 data bit (coming in parallel,
number of bit depends on how your set up the Chip, just google PT2262
and find some PDF, and you will see)
with that setting, you can build all the smart in the TX controller,
before sending the address/data/command to the TX chip.
and the RX will be simply looking for the right address and activate
your appliance.
so it will be something like
PC(Parallel port) -> PT2262
or
PC(serial/USB) -> UART+TTL controller -> PT2262
then
PT2272 -> relay
the down side is, the PT series is not as reliable, and since with the
simple design, there are no MCU on the RX side. and therefore is not
upgradeable. (of course. you can still throw in a MCU there. to do
more fancy decoding to avoid cross trigger)
However, one thing i must say.
all these PT*, NRF24L01, or even xbee, zigbee, are just wireless interface.
So for prototyping (or if you plan to just make one), i would probably
pick something that are easily integrate with whatever embedded
platform you are using.
-K