The purpose of computed attributes is to compute a value based on other values. For example, your device might report an ADC voltage that you can convert into something like battery level.
As for notifications, what you probably should do is create an alarm computed attribute. And then you can enable a notification for that alarm.
Thanks, Anton for explaining Computed Attributes.
For notifications, as suggested, I created a computed attribute type alarm; however, it does not show up in the notification side. Please see the screenshot.
Also I have several Alarms enabled on the server but never receive any notification for type Alarm, other notifications types are working fine,
This is completely incorrect setup. Alarm attribute value shouldn't be a boolean. It should be one of the standard alarm keys. And then you select matching one in the dropdown.
Thanks again, Anton. I understand what you are saying, the attribute expression should be a matching event.
Pardon me but I am not a developer, could you please point me to something that allows me to write my use case i.e. battery goes below a threshold?
Your expression should be something like this:
battery < 12 ? "lowBattery" : null
I want to send a notification for low battery levels since there is no pre-built notification available. I am using a computed attribute and can test the expression (see attached). I have linked the computed attribute to the devices; and my goal is when expression turns TRUE it should notify, however, since it is not part of the notification system, I do not receive any alerts when the battery drops below a certain level.
If computed attributes cannot be linked to notifications, what is their purpose? Please help me understand.