Jump to content

API - arm vs disarm


James Peterson

Recommended Posts

  • 2 weeks later...

I SUSPECT the answer is yes, since the Elk M1 RS-232 protocol does not have separate commands for arm and disarm. There is 1 command for both arm and disarm, which takes a parameter to specify what arm state to set it to. If the parameter = 0 it will disarm the elk.

 

Again, my SUSPICION is based on what I know about Elk, not based on any knowledge of how the isy Elk module works.

 

Sent from my LG-V410 using Tapatalk

Link to comment
Share on other sites

I SUSPECT the answer is yes, since the Elk M1 RS-232 protocol does not have separate commands for arm and disarm. There is 1 command for both arm and disarm, which takes a parameter to specify what arm state to set it to. If the parameter = 0 it will disarm the elk.

 

Again, my SUSPICION is based on what I know about Elk, not based on any knowledge of how the isy Elk module works.

 

Sent from my LG-V410 using Tapatalk

The API of the ISY seperate it out, and provides two apparent methods to disarm. I use the discrete disarm command in my app, and it works flawlessly. I've not tried the type 0 arm command.... I suspect there may be differences depending on the Elk firmware of the various components...
Link to comment
Share on other sites

Elk has been incredibly consistent with the RS-232 protocol over the years versions. I used some perl modules that were written over a decade ago that I only had to add new commands to -- all of the other code, including the arm/disarm command has not changed since the first release of the docs.

 

I can't locate a public version of the doc, but will continue to search.

 

Sent from my LG-V410 using Tapatalk

Link to comment
Share on other sites

We are talking about the http API to the ISY Elk module, not the serial protocol used by the M1.

It's pretty much the same thing as that's how the ISY communicates with the Elk.

 

I'm Gary Funk and I approved this message.

Link to comment
Share on other sites

It's pretty much the same thing as that's how the ISY communicates with the Elk.

 

I'm Gary Funk and I approved this message.

Not really.

 

The M1 expects a binary string, and the ISY is a REST API. The question presented is does 'armType=0' equal 'disarm' when sent thru the REST API. What's the difference? Does it have different meaning when the ISY has translated it into the binary string to send to the M1.

 

It's valid (and helpful) to know that it is thought that there is only one disarm command in the serial API - but the specific strings sent to the serial port of the M1 via the M1XEP are *very* different to the API commands sent to ISY.

 

I guess I could sniff the traffic and see - compare the two ISY API commands to see if they generate different strings to the M1XEP.

Link to comment
Share on other sites

I wonder why there isn't a RAW function. That would simplify a lot. Then we could use the new Elk commands.

 

B.R.I.A.D.A.

Best regards,

Gary Funk

You can always use the network module and send commands to the M1XEP. It's documented somewhere, from when people were figuring it out pre-Elk module.
Link to comment
Share on other sites

 

 

Hello all,

 

Everything you can do with ELK is already defined ISY-WS-SDK-ELK (in the current WSDK). As such, I am not so sure what I'd be answering since that's the official API for ISY/ELK.

 

With kind regards,

Michel

Michel;

 

Since ArmType "0" = Disarm

 

is area/X/cmd/arm?armType=0&code=XXXX

equivalent to area/X/cmd/disarm?code=XXXX

 

Or do they perform different tasks in some way?

 

 

 

B.R.I.A.D.A.

Best regards,

Gary Funk

Link to comment
Share on other sites

Archived

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


×
×
  • Create New...