HS3-Pi X10 problems

To replace a defective CM15a-Active Home combination with 4 rolling shutters and 5 lamps, I have set-up a Raspberry Pi 2 running with HS3 version 3.0.0.258

There are two plug-ins installed :
HSTouch Server : version 3.0.0.68
X10 (with CM11a connected) : version 3.0.0.36

Because of power-line noise, the X10 commands are repeated 3 times with 1 second interval at first
But that gives me multiple X10 errors each day, and after that the X10 devices are not controlled any more (see log-file sample below)

Mar-28 20:24:14 X10 ERROR Unable to send to CM11A/CM12U
Mar-28 20:24:14 X10 WARNING No checksum received, will retry send
Mar-28 20:23:54 X10 WARNING No checksum received, will retry send
Mar-28 20:23:34 X10 WARNING No checksum received, will retry send
Mar-28 20:23:14 X10 WARNING No checksum received, will retry send
Mar-28 20:22:54 X10 ERROR Unable to send to CM11A/CM12U
Mar-28 20:22:54 X10 WARNING No checksum received, will retry send
Mar-28 20:22:34 X10 WARNING No checksum received, will retry send
Mar-28 20:22:14 X10 WARNING No checksum received, will retry send
Mar-28 20:21:54 X10 WARNING No checksum received, will retry send
Mar-28 20:21:34 X10 ERROR Unable to send to CM11A/CM12U
Mar-28 20:21:34 X10 WARNING No checksum received, will retry send
Mar-28 20:21:14 X10 WARNING No checksum received, will retry send
Mar-28 20:20:54 X10 WARNING No checksum received, will retry send
Mar-28 20:20:34 X10 WARNING No checksum received, will retry send
Mar-28 20:20:14 X10 ERROR Unable to send to CM11A/CM12U
Mar-28 20:20:14 X10 WARNING No checksum received, will retry send
Mar-28 20:19:54 X10 WARNING No checksum received, will retry send
Mar-28 20:19:34 X10 WARNING No checksum received, will retry send
Mar-28 20:19:14 X10 WARNING No checksum received, will retry send
Mar-28 20:18:57 Event Event Trigger "rolluiken Luiken kant Ton sluiten bij zonsondergang"
Mar-28 20:18:54 Event Event Trigger "Lampen Lamp bij computer aan bij zonsondergang"

Disabling / Enabling the X10 plug-in resolves the problem for a short time.

The CM11a has worked flawless on an other system just before, so I thought that should not be the problem.
Because of the limited computing power off the Raspberry Pi2, I thought that to much X10 signals in a short time could perhaps be to much to handle.
Therefore I changed the X10 command repeating interval to 5 seconds and made sure no events where started at the same time.

This made the system much more stable, it then runs for 5 days without problems.

Then the following X10 WARNING/ERROR showed up (see logfile below)

Apr-02 20:37:40 X10 ERROR Unable to send to CM11A/CM12U
Apr-02 20:37:40 X10 WARNING No checksum received, will retry send
Apr-02 20:37:20 X10 WARNING No checksum received, will retry send
Apr-02 20:37:00 X10 WARNING No checksum received, will retry send
Apr-02 20:36:40 Warning Plugin X10 is not responding but it is still running, not restarting yet.
Apr-02 20:36:40 X10 WARNING No checksum received, will retry send
Apr-02 20:36:20 X10 ERROR Unable to send to CM11A/CM12U
Apr-02 20:36:20 X10 WARNING No checksum received, will retry send
Apr-02 20:36:05 Error Calling SetIOMulti in plugin X10:Object reference not set to an instance of an object
Apr-02 20:36:00 X10 WARNING No checksum received, will retry send
Apr-02 20:35:40 X10 WARNING No checksum received, will retry send
Apr-02 20:35:39 Warning Plugin X10 is not responding but it is still running, not restarting yet.
Apr-02 20:35:35 Error Calling SetIOMulti in plugin X10:Object reference not set to an instance of an object
Apr-02 20:35:20 X10 WARNING No checksum received, will retry send
Apr-02 20:35:10 Event Deleting event after run: "Delayed Actions Lamp op Pilaar (Delayed Action) – 1"

Disabling / Enabling the X10 plug-in resolves the problem again, but I don’t now for how long.


Has anyone some ideas what could be the problem and how to solve this?

Regards, Peet