I'm convinced X10 should pull their support for RF Tx from their software. It is so unreliable. Below is another bizarre behavior. I’ve tried to make this a clear as possible. Before starting, I’ve unplugged and removed the batteries from the CM15A and repeated these tests several times.
Test case 1
1. Create macro K4 to send one RF command dim absolute 50% to M4.
2. Configure it to Run From PC
3. Save it and download to the CM15A
4. Switch to all rooms view
5. View the activity monitor (F2)
6. Execute the macro by clicking on the Run Macro button
Results: Four transmit commands get logged to the activity monitor; M4 Off, M4 Off, M4 On, and M Dim.
Continue watching the activity monitor window. It shows the Receive for the Off and On commands and then about 80 Receive M Dim 10% (takes several minutes before it stops)
Test case 2
1. Edit macro K4 to send one RF command dim absolute 50% to M4.
2. Configure it to Store in Interface
(The only difference from test case 1)3. Save it and download to the CM15A
4. Switch to all rooms view
5. View the activity monitor (F2)
6. Execute the macro by clicking on the Run Macro button
Results: Three transmit commands get logged to the activity monitor; M4 Off, M4 On, and M Dim
Continue watching the activity monitor window. It shows the Receive for the Off and On commands and then about 4 Receive M Dim 10%
In both cases, watching the actual device confirms what’s in the log. In fact, in test case 1, manually pushing the button on the wall switch turns the light back on to full brightness and then it begins to dim until off just as the activity monitor would suggest.
I’ve tested this in versions 3.228 and 3.271 (downloaded/installed today)
I really want X10 to be aware of this situation. Can anyone suggest the best avenue for bringing this (along with the other bizarre behavior in this thread) to their attention?
Thanks again for everyone’s help and suggestions.