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.
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.
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.
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.
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.
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)
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?
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.