Jump to content

Can't ARM/DISARM From ISY


FRR

Recommended Posts

Posted

I verified that User Code 1 is able to Arm/Disarm using the ELK Web Console. I set the ELK access code in the ISY config to User Code 1. Still CAN'T Arm/Disarm from the ISY Admin Console. The log is below. There is a [ELK-ERR ] in the log which probably indcates a problem of some sort. I CAN control outputs from ISY.

 

What next?

 

Frank

 

Wed 11/30/2011 06:26:26 PM : [ELK 0 0 4] Keypad : Master Bedroom : Access Code Valid (101/1/0)

Wed 11/30/2011 06:26:34 PM : [ELK 0 0 4] Keypad : Master Bedroom : Access Code Valid (101/1/0)

Wed 11/30/2011 06:26:43 PM : [ELK 0 0 4] Keypad : Master Bedroom : Access Code Valid (101/1/0)

Wed 11/30/2011 06:26:51 PM : [ELK-ERR ] Arm Stay : House

Posted

Hi Frank,

 

Here's a few things to try:

 

1. Try using your access code directly on a keypad to arm your system (or use the virtual keypad). This would at least verify your access code is correct.

 

2. When using Elk RP, try doing "Send to Control" on the User page again.

 

3. Just guessing on this one, but you may want to check G11-G12 values in Globals.

 

Try to arm/disarm directly from your browser using these URLS:

 

(replace 123456 with your access code). If you omit the "code" attribute, it will use the one configured in ISY.

 

http:///rest/elk/area/1/cmd/arm?armType=2&code=123456

http:///rest/elk/area/1/cmd/disarm?code=123456

Posted

IndyMike and I experienced the same problem. Both of us fixed it by re-entering and saving the password in ISY. Even though the password showed correctly, after the firmware upgrade it didn't work.

Posted

Chris, apostolakisl, Thanks for the suggestions. Below are my results:

 

1. Try using your access code directly on a keypad to arm your system (or use the virtual keypad). This would at least verify your access code is correct. Access code works at the keypad and Elk's web page console

2. When using Elk RP, try doing "Send to Control" on the User page again.Tried this many times setting the access control to several different 4 digit codes. Also reentered and changed the Access code in the ISY Elk config page.

3. Just guessing on this one, but you may want to check G11-G12 values in Globals. Set to 4 digits

 

Try to arm/disarm directly from your browser using these URLS:

 

(replace 123456 with your access code). If you omit the "code" attribute, it will use the one configured in ISY.

 

 

http:///rest/elk/area/1/cmd/arm?armType=2&code=123456(When ELK is Disarmed)

ELK Status: Did not Arm

 

<?xml version="1.0" encoding="UTF-8" ?>

-

404

 

http:///rest/elk/area/1/cmd/disarm?code=123456 (When ELK is Disarmed)

ELK Status: Remained Disarmed as Expected

 

<?xml version="1.0" encoding="UTF-8" ?>

-

200

 

http:///rest/elk/area/1/cmd/disarm?code=123456 (When ELK is Armed)]

ELK Status: Disarmed - Actually responded to the command

 

<?xml version="1.0" encoding="UTF-8" ?>

-

200

 

Bottom line at this point is that I can disarm the ELK using the REST command or the Disarm button in the ISY Admin console. I can not arm it using ISY.

 

Suggestions?

 

Regards,

Frank

Posted

apostolakisl Now that's very obscure! By disabling the "Access" attribute I'm now able to arm Elk. Many thanks! I knew it was something I was doing incorrectly. Although I don't fully understand the "Access" attribute yet, at least I'm now able to arm. Seems that there are many of such attributes in the Elk system that are marginally documented from my point of view.

 

Thanks again,

Frank

Posted

My security system is not ELK so this may not be apply. I can define a User Code that allows a person to enter the house and disarm the system but little else. The idea is a maid service or similar can enter without tripping the system but not have the authority to put the system back into operation. That could be described as "Access" or "Access Only". The option exists to make the User Code restrictive rather than authorizing. The check box Access may make more sense when viewed from how User Codes can be used rather than from a programmers perspective. I found various internal terminology in the security system counter intuitive when looked at through the eyes of a programmer.

Posted

Thanks Chris. That's a good post and would have saved me a few hours but that's they way it goes for early adopters. I appreciate all the work you guys do and the attention you give us on the forum.

 

Regards

Frank

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      37.2k
    • Total Posts
      372.4k
×
×
  • Create New...