I'm making a new installation. Everything was working right (hue lights, sonos speakers and a samsung tv) but today I installed some old X10 devices. They started to work ok through the CM15A interface. After making some tests, I started to make some triggers which run an action group after a X10 sensor detects motion:
-X10 sensor detects motion then
-Run action group (lights on)
-Run another action group delayed 10 mins (lights off)
The problem is that after 10 minutes, just after the second action group is run, Indigo gets a "ghost" X10 on command of the motion sensor, which makes an infinite loop. I found a similar case in the forum (viewtopic.php?f=87&t=12860) and after reading it I implemented an extra variable which doesn't let the trigger to be activated for a couple of seconds after the second action group is run. This solved the problem for now, but this is not what I expected. The turnaround is as follows:
-X10 sensor detects motion. If variable "sensorEnabled" is true then
-Run action group (lights on)
-Run another action group delayed 10 mins (lights off)
-Change variable sensorEnabled to false (delayed 10 mins)
-Change variable sensorEnabled to true (delayed 10 mins and 2 secs)
Currently there are no more X10 devices, so I don't think it's possible to have an actual device sending the signal. By now, there is only a motion sensor (address G2), the TM751 transceiver (set to house G), and the CM15A interface. I have made extensive tests modifying addresses, times, trigger configurations and the result is always the same.
I plan to include many more X10 devices, but I would like to solve this problem in the right way before my Indigo setup becomes unnecessary complicated and unable to be understood in the future.
How can I get rid of those nasty ghost signals?