Another topic that might be of interest:
How can device types communicate critical alerts (without the use of custom smartapps in the middle.)
For example: A z-wave door lock is detecting that a burglar is smashing the door lock (actual example would be the schlage touchscreen door lock “tamper” or “kick” alarms that send z-wave events to the controller.) Being that this is a device manufacturer specific alarm, not even a generic smartapp could handle it without some pre-defined protocol.
As a possible solution:
ST could implement a new capability: urgentAlert. This new cap indicates that a device is capable of generating (duh) urgent alerts. (Yes, this can be abused - but so can nearly everything else… I have great fun strobing the lights when my kids get home from school.)
Anyway, this new cap would have a single string attribute: “alert”. If a device type (such as a door lock) detects an urgent event (such as someone disassembling the door lock), it could create an event setting the “alert” attribute to some string, and the ST system would notify the user (as configured in a manner similar to battery or hub disconnected messages.)
An alternative is to just have the “alert” attribute of capability “urgentAlert” be a boolean, and then the descriptionText is used for the alert message.
(credit to @tgauchat for suggesting “urgentAlert” and pushing me to edit this message…)