*My goal is to be able tu trigger actions (programmed in pluto events eg: turn on a light) when the motion sensor is triggered. Simple enough. (I want the Motion Sensors signals (off/on) to be used by pluto trough tranceiver and CM11A, NOT in a "stand alone" way. )

When there is no Motion Sensor in the setup, eveything works fine. I can control lights from my scenarios, it's great.

If I forget about the core/hybrid pc and the CM11A module plugged to it, and simply set my motion detector to A1, and my light module also to A1, everything works. When movement is detected, lights turn on for 1 minute, then turns off (default setting for the motion detector / working in Stand Alone mode, no Pluto or CM11A involved).

The problem occurs when I try to make everything work together.When CM11A controls the light switch, it works alright UNTIL I put the batteries in the motion sensor. As soon as the motion sensor sends its first ON signal, everything stops working. I found this (see below) in the CM11A logs, witch is most probably the source of my problem:

Hi again... I found this quote on a "X10 DEBUG" site. Has anyone experienced this problem?If so, how can it be solved ?

Here's the quote:

"RF Transceiver Problems

X10 TM751 and RR501 RF transceivers are known to have an "endless dim" problem. In certain situations, they can repeatedly transmit X10 dim (or brighten) signals onto the power line, corrupting X10 transmissions from other devices. Another problem can occur if you have more than one of these devices. The TM751 does not monitor the AC line to see if it is colliding with X10 commands already being sent (the RR501 does monitor the line before starting a transmission). As a result, two or more transceivers could corrupt each other's signals. If you have such devices, disconnect them while troubleshooting other X10 problems."