Elk M1 getting arming status request via sockets

[mishab]

Sent email to Elk M1 customer support asking for help. Hopefully someone here will answer faster

I have Elk m1 controller connected to my network via m1xep.

I created a quick and dirty app to connect to elk m1 via Sockets. The app works great except for one thing:
When I arm my Elk M1 away I get a sequence of codes, which seems to be out of sync.

For example:
When I push the away button I get the following codes:

1. 1EAS000000001111111100000000000E (current state)
2. 1EAS100000004111111100000000000A (fully armed away state)
3. 1EAS1000000031111111000000003BF6 (exit delayed away state)
4. 1EAS100000004111111100000000000A (fully armed away state)

Why is #2 is inserted in the sequence? Is this by design?
ELK m1 RS232 Protocol documentation does not say anything about this behavior.

 

[AnotherOne]

You discover the M1 sends lots of arm / disarm command and keypad commands which make no sense.