I still cannot get the MS16A to work with the light I am trying to control when using the CM15A. I have my WS467 set on A10 (its wired to the front porch light and works with a PalmPad and with local control) and I have my MS16A set to A9. When the WS467 was set to A9 also, it would work plenty fine. It actually worked WAY TOO MUCH, as in it was on all day and would constantly seem to detect motion (maybe from trees in the distance?!). I did not however seem to trigger too much during the night, according to the log in AHP. Also, I now have this motion sensor sitting in the corner on my porch. there is no direct sunlight to it. My main reason for putting them on a separate code was to use a macro to tell it to only turn on the light during the night. I set up the macro to be triggered by A9 ON and then used the condition "if time is between dusk and dawn, run macro". The macro was just A10 (Front Porch Light) ON. So if an A9 ON was triggered and the time was between dusk and dawn (which I assume would come from the dusk/dawn times stored in the CM15A which I have done), then A10 would turn on. If it wasn't during that time, then nothing should happen (except of course A9 being turned on but nothing is on that code except the MS16A).
I had the macro set up, downloaded it to the CM15A, made sure the interface was updated, and tried it (after the dusk time, well after actually). The light did not turn on. The logs did show that A9 ON had been sent but there was no macro run for A10. Actually, a couple times, I did see the macro run and it would say A10 bright/dim 100% which should work, but the light would not turn on. Didn't see that at all time though. Now this was when my CM15A was connected tot eh PC on the other side of the house so it was receiving the codes from the powerline coming from the TM751 which was near the MS16A. I then tried putting the CM15A in an outlet on the same circuit as the light. It's actually on the same breaker and is directly below the switches. I tried with and without the nearby TM751 plugged in. This outlet is also just on the other side of the door as the MS16A so I know range is not an issue. Range shouldn't matter either when I tried holding the MS16A right in front of the CM15A plugged into that outlet. In all of these instances, the light did not turn on. But I could always press the local button on the WS467 and it turned right on. I could press A10 ON on my PalmPad and it would go on. If I pressed A9 ON on my PalmPad, nothing, except for one time when I think it went on and then off. It was weird. Don't quote me on that. It could have been that one time when I hit A10 ON on my PalmPad and then it went on and then off. I had also tried the on button directly on the MS16A and still nothing.
I just can't figure out how simple this is and how it is not working. Every code is set right. The macro has been checked and downloaded multiple times. But I'm still getting nothing. When I set both the MS16A and WS467 to the same code, it works, but when it is on separate codes and relies on the macro to use one to turn on the other, I get nothing. I'm gonna double check the time on the CM15A to make sure its right but I believe it was fine when I did it. I think I had seen in the log where I was trying it before the dusk time and it was getting A9 ON but no macro triggered (which is good) and then I got to the time that dusk was set at for that day and when it got an A9 ON, it executed an A10 bright/dim 100% (also good). And then I tried it in the outlet near the door since maybe the A10 code was not be received by the WS467 (all the way across the house) and it did not work. Any suggestions on this one? I'm gonna try doing some more tests and see when I get. I may use my laptop to plug in the CM15A and use the log while it is in the outlet near the door.