I know in the early days of AHP (when nothing worked and we all payed to be beta-testers) Michael Cole used to read and respond to let us know that X10 was listening. (I miss him.)
You
payed to be a beta tester? I certainly was never charged. Matter of fact, X10 provided me with the hardware/software free to test.
Yea, I miss Michael Cole too, and the relationship we built over the years. I could always shoot him an email, even after formal beta testing was over, if I found a new bug.
My latest issue about the "Nighttime" condition is a glaring logical error - anyone who understands how the CM15a works should have been able to predict this would occur. (I.e. if you understand how the CM15a combines AND and OR conditions you would see that NIGHTTIME cannot be combined with and AND condition.)
Being a programmer, I kind-of liked the graphical flowcharting style of entering a macro, that AH2/CM14A used. With it, one could be very specific on how execution flowed.
BTW, for nighttime vs daytime, could not one use a single flag and thus eliminate the logical condition error? I am not home right now, so I can't verify this myself, but I even think one of the flags is already pre-defined to be a day vs. night flag (can someone please confirm/deny that?).