ELK Variables ${elk.area.#.armUpState}?

[sanders2222]

Does anyone know how to include the 'built-in' ELK status variables in a communication? I use the either the form:

Armed State: ${elk.area.#.armedState}
Arm Up State: ${elk.area.#.armUpState}

OR

Armed State: ${elk.area.1.armedState}
Arm Up State: ${elk.area.1.armUpState}

The latter assumes the '#' is supposed to be substituted with the numbered zone. But neither form works; just shows blank values. If there is a Wiki link describing what all the built-in variables represent and how to use them, please point me in that direction. I posted this question under the Variables forum but this may be a better place for this post.

[apostolakisl]

You have made the correct assumption. You are to replace the # with the actual number. I have not used this feature for armed/armed-up state, but I have used it for zones and it works as expected. Have you tried it for zones? I assume the email is showing the part you typed in, the "Armed State:" and "Armed Up State:" followed by blank space. Correct?

[sanders2222]

Have you tried it for zones? I assume the email is showing the part you typed in, the "Armed State:" and "Armed Up State:" followed by blank space. Correct?

No, I haven't tried zones. And Correct, my text message/email just shows a blank space following the label. Same thing happens with ${elk.area.1.armedState}.

My workaround (for now) uses variables and I am able to get that information. Here is how my Notification message is set up

Home Away mode has been set.

$iAway=${var.1.1}

$sHouseArmAway=${var.2.6}

$sHouseArmVacation=${var.2.8}

$sHouseArmStay=${var.2.7}

Armed state:${elk.area.1.armedState}

Armed up state:${elk.area.1.armUpState}

It just seems if this is available, I wouldn't need the variables. I wonder if anyone has had success using the ELK Security alert variables? And where can I find out what they all mean? (Granted, most are obvious)

[apostolakisl]

I just tested the following in the body section:

 

Frt Dr ${elk.zone.1.status}
Bck Dr ${elk.zone.2.status} 
Fam Dr ${elk.zone.3.status}
Arm ${elk.area.1.armUpState}

 

And this was in the body of the email I received:

 

Frt Dr Normal
Bck Dr Normal
Fam Dr Normal
Arm Ready To Arm

 

Not sure where you are going wrong.

[sanders2222]

I just tested ...Not sure where you are going wrong.

Thanks apostolakisl, Your success made me try something. I moved the ELK variables infront of my defined variables and it worked. Oddly values for my defined variables is coming up blank:

Away mode is set:

$iAway=0

Armed state:Armed Stay

Armed up state:Armed fully

$sHouseArmAway=0

$sHouseArmVacation=0

$sHouse

It appears there may a limit to the number of characters I can include in a text message. When I tacked on the ELK alerts, apparently I exceeded the limit so values/text gets truncated.

 

This will work though and I can get rid of my redundant defined variables!

[apostolakisl]

I believe texts are limited to 160 characters.

 

Did you have a bunch of other stuff in your body section that you didn't show in your original post?

[sanders2222]

Did you have a bunch of other stuff in your body section that you didn't show in your original post?

No. The original post was the extent of the message. 15 words, 214 characters.

 

The last post (above) has 129 charcters shown. But if you count all the characters in the formulas that generated the display, it took 183 characters.

[apostolakisl]

I think all of the "from" field letters also count. Also carriage returns and spaces.

 

The limitation is not ISY, it is the protocol for texts within the cell network. So I truly doubt the letters used to describe the variable matter since none of them get sent to the cell provider.

[Xathros]

Some of it may depend on your cell provider as well. I know with AT&T if I send more than 160 chars through the email to text gateway, AT&T will split the message into multiple 160 char texts.

 

When counting the chars, the important part is the length of the variables value not the variable itself as the ISY replaces the variable with the value before the message is sent.

 

The ISY is sending an email, not a text, there is no 160 char limit enforced at the ISY.

 

-Xathros