Hey Brian,
Yeah I am seeing the same thing....unfortunately
6/13/2011 5:38:09 PM Receive RF East Guest Bed - Sensor Closed
991 6/13/2011 5:38:09 PM Receive RF M MTCDDVD
992 6/13/2011 5:38:10 PM Receive RF A 00TV
993 6/13/2011 5:38:10 PM Receive RF Security Module - Sensor Closed
994 6/13/2011 5:38:10 PM Receive RF A 00TV
995 6/13/2011 5:38:10 PM Receive RF Security Module - Sensor Closed
996 6/13/2011 5:38:10 PM Receive RF A 00TV
997 6/13/2011 5:38:10 PM Receive RF Security Module - Sensor Closed
998 6/13/2011 5:38:10 PM Receive RF A 00TV
999 6/13/2011 5:38:10 PM Receive RF Security Module - Sensor Closed
My logs are filled these (although the A 00TV are all M MTCDDVD entries in the AHP 'internal' viewer). So since you are seeing the same thing it would appear that this is how they are supposed to work although I am not sure why. I can understand them sending the current state when checking in but I don't see why this triggers a state change and thus a macro in my case. Technically for security, one is more concerned with open then closed I guess but it will still be nice to have the option to have an action performed when the sensor is closed (and not have it repeat continuously). Would figure that more people would have chimed in to confirm this also
So in your case, does the external input trigger something different than Delayed Sensor Triggered or Sensor Triggered? If what we are seeing is the case then I would assume if the sensor was left open then it would check in and cause the Triggered macro (if one existed) to run every time. So I am somewhat surprised that you don't get that due to having the internal switch missing and thus that part of the sensor always being open. If that makes sense lol