I concur with GeorgeP.
A proper phase coupler is a must,
preferable installed at the panel; a phase
couple/blocker is a better option because
it will eliminate interference from
external X10 signals.
I got the Cm15a to work reliably, by
minimizing the use of RF commands( motion
detectors),
My test set up was a single light (stairs),
controlled by 2 motion detectors;
A night time either motion would brighten
the lamp, when the off motion command was
received it would dim to zero. Flag 2 was
used to prevent the lamp to brighten when
the second motion was activated.
As long as I walked slow, (avoiding
triggering both sensor within seconds of
each other) it worked fine, if I triggered
the second motion while light was being
dimmed or brightened it would stop working;
If I left the CM15a connected to the
computer it would work fine every time, it
was easy to conclude the Software Clock was
being messed up.
I have done many other test and they all
confirmed the same: the processor can not
handle the work load and has some internal
flaws of it’s own. The processor used is
Cypress Encore series and has GPIO problem,
after talking to my Cypress FAI (Jesse: FAI
stands for “Field Application Engineer) he
suggested for new design to use Encore II
series, to my surprise the Encore II line
is PSOC based, a totally different silicon.
I wonder why Cypress would totally redesign
the part?, is this a hint to X10?