as said above under "Arm Failed" partition event, you could have some code to manually check each zone and store their state in a variable to then report which zones triggered the alarm - could be the same programming macro code so would only have to code it once. The "OPEN_ZONE_COUNT" will indicate the number of zones open. when an alarm is triggered, the DISPLAY_TEXT variable (and panel display) will not report which zone causes the alarm to be triggered. (per above) if an invalid PIN code is entered, DISPLAY_TEXT partition variable for "Operation Rejected by Panel" which is the error message displayed when an invalid code is entered the alarm arm/disarm panel will allow logging of the arm/disarm event and will report that a PIN was used, but will not display the actual PIN used (it's obscured) As a workaround, you could watch the DISPLAY_TEXT partition variable for a change to the string "Operation Rejected by Panel" which is the error message displayed when an invalid code is entered. I'd say this is a BUG in the 584e driver. the "Disarm Failed" partition event is NOT triggered if an invalid alarm PIN is entered to disarm the alarm.
You could create a programming macro that would add all open zones to a variable, and then use that variable to report open zones. You could (manually) query each zone to see which one (or more) are open if this event is triggered. The driver, however, will not report back what zone is open. the "Arm Failed" partition event will be triggered if a zone is open when arming is attempted. if greater than zero, then something is open. the partition OPEN_ZONE_COUNT variable will indicate the number of zones that are open when arming is attempted. You can then use the individual sensor state to trigger programming or to query the open/closed state. The sensors will show the open/closed state of as reported by the panel. after the 584e driver queries the panel and adds the zones to the system, you can connect contact sensors (or other) to the 584e driver. when the 584e driver is put into an appropriate Log Level, you can see that the driver has access to all of the panel events/messages and will log/display all the alarm panel events that it sees, BUT not all of these events are exposed outside of the driver Not sure that the integration is any better from the 587e driver to the 584e, but here's some of what I see (may be incomplete): Will this allow better integration? IE Will it report to c4 which zone caused failure to arm, which zone is open if want to use the new weather and voice app to say family room window is open and it will rain in two hours, will it report which alarm code was used to disarm.
0 kommentar(er)
