Alarm Types and the associated events are now completely dynamic, and controlled via a config file, rather than hardcoded in 1.4.
Different Alarm Types (eg, Smoke) will be present on different ValueID indexes, and the associated events with a Smoke Alarm (eg, Smoke Detected, Smoke Test, Maintenance Required) will be populated in the ValueList. For new devices, only events the device supports will be populated. For older devices, all events applicable to that alarm type will be populated.
In addition, some events support additional parameters (eg, Access Control Type - Keypad Lock Operation can report the UserCode that was entered). These additional parameters will be dynamic created for the associated events. The types of parameters are limited and will always appear at the same ValueID Index. (eg, usercode param will also be at index 260 regardless of the Type of Alarm, or event). Basically, any ValueID index above 255 is a parameter to a Event.
Need to check that no hardcoded Alarm Decoding is present in the wrapper. To support new Alarm Types, or Events, OZW will just update the NotificationCCTypes.xml file
kdschlosser
commented
5 years ago
Per the OZW 1.6 Release Notes, the Alarm CommandClass has undergone a complete rewrite.
Alarm Types and the associated events are now completely dynamic, and controlled via a config file, rather than hardcoded in 1.4.
Different Alarm Types (eg, Smoke) will be present on different ValueID indexes, and the associated events with a Smoke Alarm (eg, Smoke Detected, Smoke Test, Maintenance Required) will be populated in the ValueList. For new devices, only events the device supports will be populated. For older devices, all events applicable to that alarm type will be populated.
In addition, some events support additional parameters (eg, Access Control Type - Keypad Lock Operation can report the UserCode that was entered). These additional parameters will be dynamic created for the associated events. The types of parameters are limited and will always appear at the same ValueID Index. (eg, usercode param will also be at index 260 regardless of the Type of Alarm, or event). Basically, any ValueID index above 255 is a parameter to a Event.
Need to check that no hardcoded Alarm Decoding is present in the wrapper. To support new Alarm Types, or Events, OZW will just update the NotificationCCTypes.xml file