This is an old revision of the document!
Message Templates Tags
The following tags are available in message templates:
| Tag | Purpose | Example |
|---|---|---|
[MESSAGEID] | A unique message id | ABC123-2-14-7474 |
[ZULUTIME] | Zulu/UTC time when message was triggered | 2019-12-31T23:59:52Z |
[ISODATE] | Date when message was triggered, in controller time zone, ISO format | 2019-12-31 |
[USDATE] | Date when message was triggered, in controller time zone, US format | 12/31/19 |
[ISOTIME] | Time when message was triggered, in controller time zone, ISO format | 23:59:59 |
[USTIME] | Time when message was triggered, in controller time zone, US format | 11:59:59 PM |
[WEEKDAY] | Weekday when message was triggered, in controller time zone | Mon .. Sun |
[MONTH] | Month when message was triggered, in controller time zone | Jan .. Dec |
[DAY] | Day when message was triggered, in controller time zone | 31 |
[EZEID] | ezeio serial number | ABC-987 |
[EZENAME] | ezeio name | From Configure→System→Name |
[EZENOTE] | ezeio note | From Configure→System→Note |
[TYPE] | Message type | ALARM, REALARM, RESTORE, INFO |
[SOURCE] | Message source | SEND, LOG, SCRIPT |
[GROUPNAME] | Name of the group where the ezeio is assigned | From Group Settings→Group Name |
[SOURCENAME] | Name of the source alarm | From Configure→Alarms→Name |
[ACTIONNAME] | Name of the action source action | From Configure→Alarms→Alarm action→Name |
[GPS] | GPS coordinates (if available) | Lat:38.671447, Lng-121.152385:, Ele:105.2 |
[GPSLINK] | GPS coordinates Google maps link | https://maps.google.com/maps?q=… |
[GPSSIGNAL] | Signal quality of the GPS receiver | 14 |
[RSSI] | Cellular signal RSSI | 0 (no signal) .. 31 (full signal) |
[P#] | Message (#=1-4) parameters (see script command “Event”) | |
[FV#] | Field value, #=1-90 | 318.2 |
[FU#] | Field unit, #=1-90 | psi |
[FN#] | Field name, #=1-90 | Pressure |
[F#] | Field status, #=1-90, as “Field name: Value Unit”, same as [FN#]: [FV#] [FU#] | Pressure: 318.2 psi |
<AssetTag> | Can be used in place of the Field #, Example: [FV<outsidetemp>] | |
[TEXT] | Event text (see script command “Event”) | |
[ACTIONMESSAGE] | The message/template from the action (typically used in the destination list) | |
[RECIPIENT] | The name of the destination (recipient) for this message (from Destination→Name) | |
[DESTINATION] | The address of the destination (from Destination→Address) | |
[DESTINATIONTOKEN] | The token of the destination (from Destination→Token) | |
[DVC#COMMSTAT] | Device communication status, #=1-40 | n/a, ERROR, WARNING, WARNING2, WARNING3, OK, OK2, OK3 |
[DVC#OPSTAT] | Device operational status, #=1-40 | n/a, ERROR, WARNING, OK |
[DVC#APPSTAT] | Device application status, #=1-40 | n/a, ERROR, WARNING, OK, OK2, OK3, OK4, OK5 |
[DVC#STATUS] | Device overall status, #=1-40 | OK or if there's an issue COMM:ERROR |
[DVCSTATUS] | List all devices overall status | #1 Pressure sensor: OK #2 Energy meter: OP WARNING #3 Geiger counter: APP ERROR |
[DVCWARNINGS] | List all device warnings and errors (if any) | #2 Energy meter: OP WARNING #3 Geiger counter: APP ERROR |
[DVCERRORS] | List all device errors (if any) | #3 Geiger counter: APP ERROR |