Descriptive SMS macros

[DCIM_Support]

Good day all

Please assist.

I receive sms notification from Netbotz appliance 550 as below;

--------------------------

123.123.123.124

Room 1

Fail

2018-09-21 08-37-53

---------------------------

At first we unable to determine what the issue was until we collated all info and compared the e-mail notification time with the SMS notification error: " Critical communication error with device"

Is there anyway that we can add/change the Macros so that it can be more descriptive for SMS?

Current Macros are;

${IP} ${LOCATION} ${SENSORNAME} ${ALERTPORT} ${SENSORVAL} ${ALERTSEV} ${DATE} ${TIME}

Is there anything that we can add to the current Macros to provide more info when SMS notifications are sent ? when loosing connectivity or when Nrtbotz Appliance is unavailable ?

Thank you and Kind regards

(CID:134036416)

[DCIM_Support]

Hello Juice,

Within advanced view/help you can find a description of the macro's. I have also attached them to this question BotzWare Macros.pdf

Best regards,

Cees

(CID:134036431)

[DCIM_Support]

Personal favorite goes to : ${ISACTIVE?yes?no}

You can replace the word yes to alarm and no to alarm cleared or something more descriptive.

This way, recipients knows immediately when alarm is active or cleared.

(CID:134036930)

[DCIM_Support]

You can also find the macros on page 136 of this document 

http://www.apc.com/salestools/LSCZ-7B7KY3/LSCZ-7B7KY3_R12_EN.pdf

Note that some macros return blank values if the device does not support them.

I have never found a definitive list of device / macro support...

(CID:134036440)

[DCIM_Support]

Thank you All for your input.

I need a macro that is as decriptive as the e-mail, " Communication failure"  or something similar to this...  I didnt get that macro. Will keep looking...

Once again i appreciate everyones willingness to help = Thank you!

(CID:134037759)

[DCIM_Support]

Dear juice,

Tell us, please, did you solve your question or not?

With respect.

(CID:134679953)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.