Elk M1 via M1XEP Development


#42

Ok Great! I will do a couple of tests when I get home from work in a little while. Then if all goes well, post an update. I think it has to do with how your code is being used and since our systems don't require a code to arm, I should be able to work around it. The problem will be if someone else comes along and wants to require a code to arm


#43

COOL!! Thanks for your time and effort, this works AWESOME so far!


#44

Glad to hear! If I were a programmer perhaps I could figure things out a bit quicker but nonetheless we will get you up and running!


#45

Ok if you go into Elk RP. Click on user and check if the box 'User has an access credential instead of a code' is check or unchecked. Also, under user authorizations is 'Arm checked or unchecked.


#46

Im in Elk RP right now, and it does not have "user has and Access credential" checked. In User Authorizations, Arm is checked


#47

How about for user 2.


#48

both are the same


#49

Do you have another user code you can try? If you do you will have to remove the Elk M1 App and then reinstall it. I am racking my brain but unfortunately don't know what is going on. Your setup sounds similiar to mine so far. Also I was going to try and arm the system without a code but no luck so far.


#50

i can create another user with another code.


#51

Ok worth a try. Like I said though you will have to remove app and reinstall. I have it in my list to be able to change user code.


#52

Ok created a new user, removed app, reinstalled, initialized, and ran "Arm Night"

app:1872019-03-07 07:03:06.386 pm debugElk M1 Module: Connection Driver: LogData: 1313

app:1872019-03-07 07:03:06.368 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 1CLD13130031165203070005190049

app:1872019-03-07 07:03:06.336 pm debugElk M1 Module: Connection Driver: The event is unknown

app:1872019-03-07 07:03:06.327 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 17IC000000000000003010078

app:1872019-03-07 07:03:06.288 pm debugElk M1 Module: Connection Driver: sendMsg 0Da410055550032

app:1872019-03-07 07:03:06.275 pm debugElk M1 Module: Connection Driver: armNight()


#53

Ouch same issue/message. So hopefully we can get another tester to see if we can repeat the issue. I will continue to look at my setup to see if there could be any differences.


#54

It is weird you are getting that same 1313 message straight away.


#55

I tried arming thru M1togo, and the log said this:
app:1872019-03-07 07:10:03.052 pm debugElk M1 Module: Connection Driver: The event is unknown

app:1872019-03-07 07:10:03.045 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 09EM0010014

app:1872019-03-07 07:10:03.018 pm debugElk M1 Module: Lock

app:1872019-03-07 07:10:03.008 pm debugElk M1 Module: Connection Driver: armed

app:1872019-03-07 07:10:02.973 pm debugElk M1 Module: Connection Driver: LogData: 1173AREAARMED

app:1872019-03-07 07:10:02.958 pm debugElk M1 Module: Connection Driver: LogData: 1173

Just as an FYI


#56

another thing to note, is i had Elkm1togo running, and then hit the disarm in the HE app and it still worked. So the connection is definitely ok, its receiving info both ways, the issue must be in a different config in my M1


#57

Ohhh what Firmware version are you on. i think mine is old 5.2.10 i will try to upgrade


#58

Try this! Open up the driver code and go to line 239.

Replace the line that says:
msg = msg + cc
With this:
msg = msg + cc + '\r\n'

Then click Save in top right corner!


#59

Hey Guys,
I will be back home next week and be able to test with my M1.


#61

Thanks for trying. No luck
app:1892019-03-08 10:38:05.834 pm debugElk M1 Module: Connection Driver: LogData: 1313
app:1892019-03-08 10:38:05.818 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 1CLD13130021223703080006190048
app:1892019-03-08 10:38:05.782 pm debugElk M1 Module: Connection Driver: The event is unknown
app:1892019-03-08 10:38:05.768 pm debugElk M1 Module: Connection Driver: Parsing Incoming message: 17IC000000000000002010079
app:1892019-03-08 10:38:05.690 pm debugElk M1 Module: Connection Driver: sendMsg 0Da4100555503C
app:1892019-03-08 10:38:05.680 pm debugElk M1 Module: Connection Driver: armNight()


#62

Think I got it. Just woke up in middle of night and checked Elk RP before putting on alarm. I think you may have an item labeled 'Access' checked under User Authorizations. Try unchecking this box for the user code you are using and see if it works.

Cheers and Good Night!