We have moved at community.getvera.com

Author Topic: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin  (Read 153981 times)

Offline Quixote

  • Sr. Member
  • ****
  • Posts: 350
  • Karma: +18/-35
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #555 on: March 29, 2017, 01:49:34 am »
This guy was a legend long ago.  ;)

Keep up the good work, Zoot.
Haven't updated lately since I've been away fairly often recently and worried about messing with my system, but it's good to know capable people are handling business.
Thanks for your efforts.
My "Karma" has been modified by 2 or 3 douchebags that didn't like that I criticized the plugin that they worship. I'm not actually a bad person. (I guess I'm "Chaotic Neutral").

Offline Quixote

  • Sr. Member
  • ****
  • Posts: 350
  • Karma: +18/-35
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #556 on: March 30, 2017, 08:19:06 pm »
Strangely my Vera is not triggering the scene I have for when the system is disarmed. Are there any known issues that I'm unaware of? When I trigger the scene manually, it works correctly. Additionally, the scene triggered by arming the system works as intended.
Thanks.
My "Karma" has been modified by 2 or 3 douchebags that didn't like that I criticized the plugin that they worship. I'm not actually a bad person. (I guess I'm "Chaotic Neutral").

Offline zoot1612

  • Moderator
  • Hero Member
  • *****
  • Posts: 603
  • Karma: +21/-2
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #557 on: March 30, 2017, 09:36:22 pm »
@Quixote
Will need to see your scene and logs to get an idea.

Thanks

Offline Quixote

  • Sr. Member
  • ****
  • Posts: 350
  • Karma: +18/-35
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #558 on: March 30, 2017, 09:38:20 pm »
Ok, how do we go about that? Screen-shots?
My "Karma" has been modified by 2 or 3 douchebags that didn't like that I criticized the plugin that they worship. I'm not actually a bad person. (I guess I'm "Chaotic Neutral").

Offline zoot1612

  • Moderator
  • Hero Member
  • *****
  • Posts: 603
  • Karma: +21/-2
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #559 on: March 30, 2017, 11:44:57 pm »
@Quixote
Screenshot for scenes to start with.

Offline Quixote

  • Sr. Member
  • ****
  • Posts: 350
  • Karma: +18/-35
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #560 on: March 31, 2017, 05:44:12 pm »
There is no Lua script in the scene. The two device actions are sending an email using the SMTP plugin, and setting the Home Mode to "Home".

Also, I should mention that the method I use to disarm the system is through Elk-M1 rules. I watch a certain zone, and when a piece of hardware that I have to read iButtons closes a relay and triggers that zone, the system is disarmed.
« Last Edit: March 31, 2017, 05:46:35 pm by Quixote »
My "Karma" has been modified by 2 or 3 douchebags that didn't like that I criticized the plugin that they worship. I'm not actually a bad person. (I guess I'm "Chaotic Neutral").

Offline zoot1612

  • Moderator
  • Hero Member
  • *****
  • Posts: 603
  • Karma: +21/-2
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #561 on: March 31, 2017, 08:21:39 pm »
@Quixote
Will have to do some experimentation to check that it all works OK and get back to you. As far as the method goes that shouldn't make any difference.

Offline zoot1612

  • Moderator
  • Hero Member
  • *****
  • Posts: 603
  • Karma: +21/-2
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #562 on: March 31, 2017, 08:50:51 pm »
@Quixote
Probably the easiest way to trouble shoot in the case is to check your logs.

Here is a breakdown of what you need to do: -

When partition/area is disarmed you should see something along the lines of this: -

06   04/01/17 8:34:27.449   Device_Variable::m_szValue_set device: 190 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: AlarmMemory1 was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2fba5680>
08   04/01/17 8:34:32.207   JobHandler_LuaUPnP::HandleActionRequest device: 188 service: urn:micasaverde-com:serviceId:AlarmPartition2 action: RequestArmMode <0x2fda5680>
08   04/01/17 8:34:32.207   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=188 <0x2fda5680>
08   04/01/17 8:34:32.208   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:AlarmPartition2 <0x2fda5680>
08   04/01/17 8:34:32.208   JobHandler_LuaUPnP::HandleActionRequest argument action=RequestArmMode <0x2fda5680>
08   04/01/17 8:34:32.209   JobHandler_LuaUPnP::HandleActionRequest argument State=Disarmed <0x2fda5680>
08   04/01/17 8:34:32.209   JobHandler_LuaUPnP::HandleActionRequest argument PINCode=XXXXXX <0x2fda5680>
02   04/01/17 8:34:32.211   luup_log:187: ElkPlugin::requestArmMode: Request to arm partition 1 (device 188) to state 'Disarmed'. <0x2fda5680>
02   04/01/17 8:34:32.318   luup_log:187: ElkPlugin::sendCommand: Send command: '0Da01XXXXXX0035'. <0x2fda5680>
02   04/01/17 8:34:32.345   luup_log:187: ElkPlugin::checkMessage: length=23(0x17), message type=IC, data='00000000000000103', misc=00, checksum=78 <0x2fda5680>
02   04/01/17 8:34:32.346   luup_log:187: ElkPlugin::checkValidUserCode: Got expected message. <0x2fda5680>
02   04/01/17 8:34:32.347   luup_log:187: ElkPlugin::checkValidUserCode: Valid PIN. <0x2fda5680>
02   04/01/17 8:34:32.347   luup_log:187: ElkPlugin::checkValidUserCode: Valid User. <0x2fda5680>
02   04/01/17 8:34:32.348   luup_log:187: ElkPlugin::checkValidUserCode: waiting for request response. <0x2fda5680>
02   04/01/17 8:34:32.366   luup_log:187: ElkPlugin::checkMessage: length=28(0x1C), message type=LD, data='1174001107250401000717', misc=00, checksum=4B <0x2fda5680>
02   04/01/17 8:34:32.367   luup_log:187: ElkPlugin::readArmRequestResponse: Got unexpected message. Process it and intercept the next one. <0x2fda5680>
02   04/01/17 8:34:32.367   luup_log:187: ElkPlugin::handlerFunc Message type description: Request System Log Data <0x2fda5680>
02   04/01/17 8:34:32.371   luup_log:187: ElkPlugin::Interpretation of Ext Info Field in Log Entry, type 2 <0x2fda5680>
02   04/01/17 8:34:32.372   luup_log:187: ElkPlugin::processElkLog: processing log index 000. <0x2fda5680>
02   04/01/17 8:34:32.388   luup_log:187: ElkPlugin::checkMessage: length=15(0x0F), message type=EE, data='100000000', misc=00, checksum=EF <0x2fda5680>
02   04/01/17 8:34:32.388   luup_log:187: ElkPlugin::readArmRequestResponse: Got unexpected message. Process it and intercept the next one. <0x2fda5680>
02   04/01/17 8:34:32.389   luup_log:187: ElkPlugin::processMessage: Unhandled message type 'EE' <0x2fda5680>
02   04/01/17 8:34:32.405   luup_log:187: ElkPlugin::checkMessage: length=30(0x1E), message type=AS, data='100000003111111100000000', misc=00, checksum=0B <0x2fda5680>
02   04/01/17 8:34:32.406   luup_log:187: ElkPlugin::readArmRequestResponse: Got expected message. <0x2fda5680>
02   04/01/17 8:34:32.407   luup_log:187: ElkPlugin::requestArmMode: SUCCESS: Succesfully changed to the requested arm mode. <0x2fda5680>
50   04/01/17 8:34:32.407   luup_log:187: ElkPlugin::task: SUCCESS: Arm mode succesfully changed. <0x2fda5680>
02   04/01/17 8:34:32.425   luup_log:187: ElkPlugin::checkMessage: length=12(0x0C), message type=AM, data='000000', misc=00, checksum=7F <0x2fba5680>
02   04/01/17 8:34:32.426   luup_log:187: ElkPlugin::handlerFunc Message type description: Alarm Memory Update <0x2fba5680>
02   04/01/17 8:34:32.426   luup_log:187: ElkPlugin::setPartitionState: Set variable 'AlarmMemory1' = '0' for partition 1 (device 188). <0x2fba5680>
06   04/01/17 8:34:32.427   Device_Variable::m_szValue_set device: 188 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: AlarmMemory1 was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2fba5680>
02   04/01/17 8:34:32.428   luup_log:187: ElkPlugin::setPartitionState: Set variable 'AlarmMemory1' = '0' for partition 2 (device 189). <0x2fba5680>
06   04/01/17 8:34:32.428   Device_Variable::m_szValue_set device: 189 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: AlarmMemory1 was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2fba5680>
02   04/01/17 8:34:32.429   luup_log:187: ElkPlugin::setPartitionState: Set variable 'AlarmMemory1' = '0' for partition 3 (device 190). <0x2fba5680>
06   04/01/17 8:34:32.430   Device_Variable::m_szValue_set device: 190 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: AlarmMemory1 was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2fba5680>
02   04/01/17 8:34:32.446   luup_log:187: ElkPlugin::checkMessage: length=30(0x1E), message type=AS, data='000000001111111100000000', misc=00, checksum=0E <0x2fba5680>
02   04/01/17 8:34:32.446   luup_log:187: ElkPlugin::handlerFunc Message type description: Arming Status Report <0x2fba5680>
02   04/01/17 8:34:32.448   luup_log:187: ElkPlugin::getPartitionState: Partition 1 (device 188), got variable 'AlarmMemory' = '0'. <0x2fba5680>
02   04/01/17 8:34:32.449   luup_log:187: ElkPlugin::getPartitionState: Partition 2 (device 189), got variable 'AlarmMemory' = ''. <0x2fba5680>
02   04/01/17 8:34:32.449   luup_log:187: ElkPlugin::getPartitionState: Partition 3 (device 190), got variable 'AlarmMemory' = ''. <0x2fba5680>
02   04/01/17 8:34:32.450   luup_log:187: ElkPlugin::processArmingStatusReport: partition 1, armingStatus=Disarmed, armUpState=1, alarmState=0 <0x2fba5680>
02   04/01/17 8:34:32.451   luup_log:187: ElkPlugin::setPartitionState: Set variable 'ArmMode' = 'Disarmed' for partition 1 (device 188). <0x2fba5680>
06   04/01/17 8:34:32.451   Device_Variable::m_szValue_set device: 188 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ArmMode was: Armed now: Disarmed #hooks: 1 upnp: 0 skip: 0 v:0xc93378/NONE duplicate:0 <0x2fba5680>
07   04/01/17 8:34:32.452   Event::Evaluate 2  scene Test Alarm is true users:1022925 allow:1 <0x2fba5680>
08   04/01/17 8:34:32.452   Scene::RunScene running 14 Test Alarm <0x2fba5680>


« Last Edit: March 31, 2017, 08:54:34 pm by zoot1612 »

Offline Quixote

  • Sr. Member
  • ****
  • Posts: 350
  • Karma: +18/-35
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #563 on: April 01, 2017, 05:54:07 pm »
Ok, thanks.

This log sure spits out a lot of information. I've found what seems to coincide with the arming of the system:

06      04/01/17 17:30:02.588   Device_Variable::m_szValue_set device: 6 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ArmMode was: Disarmed now: Armed #hooks: 0 upnp: 0 skip: 0 v:0xb78f78/NONE duplicate:0 <0x71b0e520>
06      04/01/17 17:30:02.589   Device_Variable::m_szValue_set device: 6 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: DetailedArmMode was: Ready now: Armed #hooks: 5 upnp: 0 skip: 0 v:0xb78fe0/NONE duplicate:0 <0x71b0e520>
07      04/01/17 17:30:02.589   Event::Evaluate 1  scene Alarm Armed Away is true users: allow:1 <0x71b0e520>
08      04/01/17 17:30:02.589   Scene::RunScene running 2 Alarm Armed Away <0x71b0e520>


...and then this further down:

06      04/01/17 17:30:51.296   Device_Variable::m_szValue_set device: 6 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ArmMode was: Armed now: Disarmed #hooks: 0 upnp: 0 skip: 0 v:0xb78f78/NONE duplicate:0 <0x71b0e520>
06      04/01/17 17:30:51.297   Device_Variable::m_szValue_set device: 6 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: DetailedArmMode was: Armed now: Ready #hooks: 5 upnp: 0 skip: 0 v:0xb78fe0/NONE duplicate:0 <0x71b0e520>
07      04/01/17 17:30:51.297   Event::Evaluate 1  scene Alarm Armed Away wrong house mode 2 repeat 0/1 <0x71b0e520>
07      04/01/17 17:30:51.298   Event::Evaluate 4  scene Alarm Disarmed is false repeat 0/0 <0x71b0e520>
07      04/01/17 17:30:51.298   Event::Evaluate 8  scene Alarm Armed Stay is false repeat 0/0 <0x71b0e520>
07      04/01/17 17:30:51.298   Event::Evaluate 9  scene Alarm Armed Stay is false repeat 0/0 <0x71b0e520>
07      04/01/17 17:30:51.298   Event::Evaluate 13  scene Lights out (Exit) is false repeat 0/1 <0x71b0e520>
06      04/01/17 17:30:51.300   Device_Variable::m_szValue_set device: 6 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ChimeEnabled was: 1 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0xb790b0/NONE duplicate:1 <0x71b0e520>


Does any of this shine a light on what's broken with my setup? Let me know if you need more of the log. It was super long, so I tried to pick out the parts that looked relevant.
My "Karma" has been modified by 2 or 3 douchebags that didn't like that I criticized the plugin that they worship. I'm not actually a bad person. (I guess I'm "Chaotic Neutral").

Offline zoot1612

  • Moderator
  • Hero Member
  • *****
  • Posts: 603
  • Karma: +21/-2
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #564 on: April 01, 2017, 09:08:38 pm »
@Quixote
From what I can see this is not a problem with the plugin it is something to do with the scenes.

Without looking at the detail of your scenes I can't really fix your problem :( I suggest you create a new very basic scene with just with a "Disarmed" trigger and see if it is successful in the log. If it works add another trigger and check again.

What other triggers do you have associated with: -
Code: [Select]
07      04/01/17 17:30:51.298   Event::Evaluate 4  scene Alarm Disarmed is false repeat 0/0 <0x71b0e520> if it is just "Disarmed" it should work if like Alarm Armed Away you have house modes associated with the trigger than you need to check that also.

There are probably better equipped people on this forum to help out with this one then me.




Offline jmelia

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #565 on: June 27, 2017, 10:51:08 am »
Two questions:
1. Is there any way of detecting a Elk Keypad Function button press (like F4), and determine which Keypad was used?
2. Is there any way of changing the Elk settings from Vera - I'd like to be able to selectively enable the light in the display of a Elk Keypad that is in a bedroom, and normally has its lights disabled.

Many thanks for all the hard work on this plugin - it's awesome!!

Offline groundwire

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #566 on: July 31, 2017, 09:54:59 pm »
@zoot1612

Mr. Zoot: I recently have come into possession of an Elk M1 system and am getting it all labbed up to learn about how it can interact with a Vera controller.

It appears the version of the plugin available in the app store is several years old and does not appear to work with current versions of firmware on the various devices involved (both Vera Edge and the Elk).

I'm seeing that your git repo is more current (at about 3 months), but when I install things manually (following the instructions you provide) it doesn't create any of the devices. I'm completely ignorant about how I'm supposed to do that myself as the installation wizard does it for me (at least this is what I'm reading) - and documentation appears to be really fragmented.

Do you think it might be time to put the new version up on the app store? Or perhaps setup a completely new app on the store for non-legacy users? I remember reading you were keeping the current one there for legacy purposes, so I completely understand not wanting to break everyone else who is set at a certain version (and stable).

Thank you very much! This plugin does appear to be very awesome, hopefully soon I'll be able to actually use it and be able to say that with authority.  ;D

- Joel

Offline zoot1612

  • Moderator
  • Hero Member
  • *****
  • Posts: 603
  • Karma: +21/-2
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #567 on: August 02, 2017, 07:25:38 pm »
@jmelia
Two questions:
1. Is there any way of detecting a Elk Keypad Function button press (like F4), and determine which Keypad was used?
2. Is there any way of changing the Elk settings from Vera - I'd like to be able to selectively enable the light in the display of a Elk Keypad that is in a bedroom, and normally has its lights disabled.

Many thanks for all the hard work on this plugin - it's awesome!!

While item 1 is available via the ELK M1 serial protocol currently it is not supported by the plugin. If you post the user case I may be able to help either with a solution or change to the plugin.

Item 2 is not supported as far as I can see, if some else knows that it can be done and how I would be happy to hear the solution.







Offline zoot1612

  • Moderator
  • Hero Member
  • *****
  • Posts: 603
  • Karma: +21/-2
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #568 on: August 02, 2017, 07:50:15 pm »
@zoot1612

It appears the version of the plugin available in the app store is several years old and does not appear to work with current versions of firmware on the various devices involved (both Vera Edge and the Elk).

I'm seeing that your git repo is more current (at about 3 months), but when I install things manually (following the instructions you provide) it doesn't create any of the devices. I'm completely ignorant about how I'm supposed to do that myself as the installation wizard does it for me (at least this is what I'm reading) - and documentation appears to be really fragmented.

Do you think it might be time to put the new version up on the app store? Or perhaps setup a completely new app on the store for non-legacy users? I remember reading you were keeping the current one there for legacy purposes, so I completely understand not wanting to break everyone else who is set at a certain version (and stable).

Thank you very much! This plugin does appear to be very awesome, hopefully soon I'll be able to actually use it and be able to say that with authority.  ;D

- Joel

At this point I won't be updating in app store, simply because I don't have the resourcing (time in this instance) to support it and yes documentation to not put to finer word on it is 'crap' for the parts I have done again time is the issue.

As to the plugin not working the first thing to do is check the logs to see what is happening, if you are connected via ethernet and are on the same subnet the plugin should configure itself otherwise back to the log and post issue here. I can't give instant replies but if logging is provided (always ensure that any sensitive info is removed) that I should be able to help.

Offline edentel

  • Newbie
  • *
  • Posts: 7
  • Karma: +0/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #569 on: September 09, 2017, 10:27:29 am »
I've stumbled on this thread after my Vera and Elk stopped talking.  I see the problem was solved and the solution is going straight to Zoot's plugin at github.  I've got the old pluging deleted, the new one added, but can't figure out the device creation semantics.

Could a kind sole offer some guidance as to how to populate the Develop Apps..... Create Device fields?   I've taken a few shots and nothing is getting created.  At best I'm getting "System error : Device: 279. Fail to load implementation file"

ANy pointer would be appreciated!