Elk M1 via M1XEP Development


#22

the Disarm button works!!!

Quick question:

In the preferences, what is the difference between password and code? I assume code is your unlock code (which was tested to work), and i assumed password is your user password that is created in the ELK EXP module. However i was thinking that the EXP module also requires a username, so i am guessing i am wrong here.


#23

Ok the logs look good. No event is just an event that hasn't been defined so no worries. As for the arming, they should all work. Oh it may only work for area 1, I can't remember I will check when I get home.


#24

Yes the code is what you use to arm and disarm the system. Where as the password is the elk rp password. I don't think I am using the password for anything at this point.


#25

Try arm away and see if your system arms.


#26

If your system isn't ready to arm it wouldn't maybe tell ya so make sure its ready to arm.


#27

I tried the arm away, and got:
app:1512019-03-03 10:46:30.958 am debugElk M1 Module: Connection Driver: AlarmState: Area 1 - No Active Alarm

app:1512019-03-03 10:46:30.937 am debugElk M1 Module: Connection Driver: ArmUpState: Area 1 - Ready to Arm

app:1512019-03-03 10:46:30.891 am debugElk M1 Module: Connection Driver: ArmStatus: Area 1 - Disarmed

app:1512019-03-03 10:46:30.876 am debugElk M1 Module: Connection Driver: AlarmStates: 00000000

app:1512019-03-03 10:46:30.847 am debugElk M1 Module: Connection Driver: ArmingStatusState: 11111111

app:1512019-03-03 10:46:30.829 am debugElk M1 Module: Connection Driver: ArmStatuses: 00000000

app:1512019-03-03 10:46:30.809 am debugElk M1 Module: Connection Driver: Parsing Incoming message:

So, it seems like the connection is working fine. I am guessing that my system is not receiving the "arming" command correctly.


#28

Ok I will check when I get home later today. By the way in your previous logs message (around message 20) the one towards the end contains your arm code if you want to delete it.


#29

Thanks!. No rush, just trying to provide as much input as i can.

Also, i forgot to say that i did check to see if i the system was ready to be armed at the keypad before i tried arming it from HE.


#30

Hey so I checked a few things and can't see any issues so far. It definitely will only work with area 1 at this time. All my arms work without any issues. If possible can you try to arm the system in 'armnight' mode and send me the log. If you want to blur out your code just copy the log over to notepad and change the to all 5's but make sure to leave the rest.

This is the log data we are looking for. You can also send me disarm log data so I can see why that is working.

app:3682019-03-04 08:55:09.923 am debugElk M1 Module: Connection Driver: LogData: 1173AREAARMED
app:3682019-03-04 08:55:09.784 am debugElk M1 Module: Connection Driver: LogData: 1173
app:3682019-03-04 08:55:09.646 am debugElk M1 Module: Connection Driver: Connection Driver: Parsing Incoming message: 1CLD11730011090203040002190050
app:3682019-03-04 08:55:09.635 am debugElk M1 Module: Connection Driver: Parsing Incoming message: 1CLD11730011090203040002190050
app:3682019-03-04 08:55:09.143 am debugElk M1 Module: Connection Driver: sendMsg 0Da410055550034


#31

Sorry for the delayed response. I did an "armnight" and this is what i got
app:1862019-03-07 01:32:44.369 pm debugElk M1 Module: Connection Driver: ArmUpState: Area 1 - Ready to Arm
app:1862019-03-07 01:32:44.350 pm debugElk M1 Module: Connection Driver: ArmStatus: Area 1 - Disarmed
app:1862019-03-07 01:32:44.339 pm debugElk M1 Module: Connection Driver: AlarmStates: 00000000
app:1862019-03-07 01:32:44.326 pm debugElk M1 Module: Connection Driver: ArmingStatusState: 11111111
app:1862019-03-07 01:32:44.310 pm debugElk M1 Module: Connection Driver: ArmStatuses: 00000000
app:1862019-03-07 01:32:44.296 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 1EAS00000000111111110000000000E2
app:1862019-03-07 01:32:44.254 pm debugElk M1 Module: Connection Driver: LogData: 1313
app:1862019-03-07 01:32:44.239 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 1CLD13130021112103070005190053
app:1862019-03-07 01:32:44.211 pm debugElk M1 Module: Connection Driver: The event is unknown
app:1862019-03-07 01:32:44.202 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 17IC000000000000002010079
app:1862019-03-07 01:32:44.119 pm debugElk M1 Module: Connection Driver: sendMsg 0Da41005555003C
app:1862019-03-07 01:32:44.102 pm debugElk M1 Module: Connection Driver: armNight()

It looks like the command is being sent, and received, but not activating the alarm. I am wondering if it may be a configuration at the ELK M1 itself that is different.

Also for disarming, this is what i get (and it works)

app:1862019-03-07 01:38:52.200 pm debugElk M1 Module: Connection Driver: disarming
app:1862019-03-07 01:38:52.174 pm debugElk M1 Module: Connection Driver: LogData: 1174AREADISARMED
app:1862019-03-07 01:38:52.158 pm debugElk M1 Module: Connection Driver: LogData: 1174
app:1862019-03-07 01:38:52.143 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 1CLD11740021112703070005190048
app:1862019-03-07 01:38:52.106 pm debugElk M1 Module: Connection Driver: The event is unknown
app:1862019-03-07 01:38:52.095 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 17IC000000000000002010079
app:1862019-03-07 01:38:52.038 pm debugElk M1 Module: Connection Driver: sendMsg 0Da010055550040
app:1862019-03-07 01:38:52.024 pm debugElk M1 Module: Connection Driver: Disarm()

Also, i am trying to decrypt what the sendMsg is telling the Elk system. Do you happen to have a breakdown of what each digit does. I have only figured out digit 5 is the zone, digits 6-11 are the password, I believe digits 14-15 are a checksum?

thanks again for all the help


#32

Just curious do you have HSM installed?


#33

Here is your disarm code brokendown.

0D a0 1 005555 00 40

0D - String length
a0 - Command code
1 - Area
005555 - Code
00 - Future use
40 - Checksum


#34

Sorry not sure what HSM is? Is it something on the ELK or HE. If its on the HE then no


#35

Your arm incoming message shoud be something like 1207 so 1CLD1207
app:1862019-03-07 01:32:44.296 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 1EAS00000000111111110000000000E2
app:1862019-03-07 01:32:44.254 pm debugElk M1 Module: Connection Driver: LogData: 1313
app:1862019-03-07 01:32:44.239 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 1CLD13130021112103070005190053

Your disarm incoming message is spot on.
app:1862019-03-07 01:38:52.174 pm debugElk M1 Module: Connection Driver: LogData: 1174AREADISARMED
app:1862019-03-07 01:38:52.158 pm debugElk M1 Module: Connection Driver: LogData: 1174
app:1862019-03-07 01:38:52.143 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 1CLD11740021112703070005190048


#36

Awesome thanks! Looks like my Checksum is wrong.

yours was 0Da410055550034
mine was 0Da41005555003C

So maybe the M1 system is thinking its a bad command?


#37

I will check your checksum but mine would be different if my code is different. Actually to check your checksum I would need your code but I don't think that is the problem.


#38

Does anything with 'Access Keypad' or Proximity reader sound familiar to you and your Elk installation?


#39

I've opened up ElkRP, and have a Keypad 01 and do remember looking into proximity readers. i installed the Elk myself (which may be the problem!!)


#40

I installed myself too, uh oh, lol! Also can you arm your system by just pressing the stay or away button. I think I have an idea and what to do.

In addition, we can now import all zones for contact, motion, etc...


#41

When i press the stay or away button, it has a countdown timer.