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

Offline lowway

  • Sr. Newbie
  • *
  • Posts: 20
  • Karma: +0/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #540 on: March 13, 2017, 02:11:57 am »
@Zoot1612
I've attached a log for the first 3 minutes of restart.  Hopefully there is enough info for you to track any issues and appreciate the effort in advance!!

Offline zoot1612

  • Moderator
  • Hero Member
  • *****
  • Posts: 574
  • Karma: +16/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #541 on: March 13, 2017, 07:07:43 pm »
@lowway
Can you try the latest in git and post the output?

Thanks

Offline Video321

  • Sr. Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #542 on: March 16, 2017, 04:49:25 pm »
I'm having an issue that I can't resolve...

I recently updated my Vera 2 to UI5. My M1 can be controlled and zone status is read, but scenes are ignored and it seems that I can't create or edit them based on alarm status anymore. I was using v1.01 of the Elk plugin so I upgraded to zoot's latest from 3-13-2017 and now all I get is "Startup Lua Failed" on the alarm panel.

Any help is appreciated!

Offline zoot1612

  • Moderator
  • Hero Member
  • *****
  • Posts: 574
  • Karma: +16/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #543 on: March 16, 2017, 08:55:54 pm »
@Video321
Can you provide log details at LUUP startup?

Offline Video321

  • Sr. Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #544 on: March 16, 2017, 09:49:43 pm »
@Video321
Can you provide log details at LUUP startup?

01   03/16/17 21:34:10.021   LuaInterface::CallFunction_Startup-1 device 10 function elkStartup failed attempt to call a nil value <0x402>

01   03/16/17 21:34:10.022   LuImplementation::StartLua running startup code for 10 I_ElkAlarmPanel1.xml failed <0x402>

Not sure what you needed from the log. LMK if that doesn't help and I can add more.
Thanks, zoot!

Offline zoot1612

  • Moderator
  • Hero Member
  • *****
  • Posts: 574
  • Karma: +16/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #545 on: March 17, 2017, 01:26:43 am »
@Video321

Going to need more  :) the more the better.

Offline lowway

  • Sr. Newbie
  • *
  • Posts: 20
  • Karma: +0/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #546 on: March 17, 2017, 03:05:48 am »
@lowway
Can you try the latest in git and post the output?

Thanks

@Zoot1612

New Git version installed and logs attached!!  Still the same result unfortunately.  Zone triggers viable and working, outputs won't switch and alarm panel won't operate for arm, etc.  Won't store passcode.
« Last Edit: March 17, 2017, 07:06:09 am by lowway »

Offline zoot1612

  • Moderator
  • Hero Member
  • *****
  • Posts: 574
  • Karma: +16/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #547 on: March 19, 2017, 07:56:13 pm »
@lonwway
Output supplied is cutoff before either a successful/unsuccessful start. I need to see output until that point. Also need to see output from log when each of the activities that you perform to see why they do not succeed.



See below for successful startup. Most of the log has been removed in the example for brevity but it would be required in your case.

Code: [Select]
02      03/20/17 7:37:31.889    luup_log:500: ElkPlugin::checkConnectionType: No IP address trying auto configuration <0x2bc23680>

02      03/20/17 7:37:32.094    luup_log:500: ElkPlugin::checkConnectionType: ipAddress = 192.168.0.251, port = 2101. <0
.
.
.
.

02      03/20/17 7:37:36.090    luup_log:500: ElkPlugin::Elk Plugin Startup SUCCESS: Startup successful. <0x2bc23680>
02      03/20/17 7:37:36.116    luup_log:500: ElkPlugin::checkMessage: length=25(0x19), message type=KC, data='0300000000000000000', misc=00, checksum=15 <0x2e623680>
02      03/20/17 7:37:36.116    luup_log:500: ElkPlugin::handlerFunc Message type description: Keypad KeyChange Update <0x2e623680>
02      03/20/17 7:37:36.117    luup_log:500: ElkPlugin::setPartitionState: Set variable 'ChimeEnabled' = '0' for partition 1 (device 501). <0x2e623680>
06      03/20/17 7:37:36.117    Device_Variable::m_szValue_set device: 501 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ChimeEnabled was: 0 now: 0 #hooks: 0 upnp: 0 v:0xb00928/NONE duplicate:1 <0x2e623680>
02      03/20/17 7:37:36.117    luup_log:500: ElkPlugin::setPartitionState: Set variable 'ChimeEnabled' = '0' for partition 2 (device 502). <0x2e623680>
06      03/20/17 7:37:36.118    Device_Variable::m_szValue_set device: 502 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ChimeEnabled was: 0 now: 0 #hooks: 0 upnp: 0 v:0xb00928/NONE duplicate:1 <0x2e623680>
02      03/20/17 7:37:36.118    luup_log:500: ElkPlugin::setPartitionState: Set variable 'ChimeEnabled' = '0' for partition 3 (device 503). <0x2e623680>
06      03/20/17 7:37:36.118    Device_Variable::m_szValue_set device: 503 service: urn:micasaverde-com:serviceId:AlarmPartition2 variable: ChimeEnabled was: 0 now: 0 #hooks: 0 upnp: 0 v:0xb00928/NONE duplicate:1 <0x


Successful "On" and "Off" for output
Code: [Select]
08      03/20/17 7:45:15.321    JobHandler_LuaUPnP::HandleActionRequest device: 518 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x30d90680>
08      03/20/17 7:45:15.322    JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=518 <0x30d90680>
08      03/20/17 7:45:15.322    JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:SwitchPower1 <0x30d90680>
08      03/20/17 7:45:15.323    JobHandler_LuaUPnP::HandleActionRequest argument action=SetTarget <0x30d90680>
08      03/20/17 7:45:15.323    JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=1 <0x30d90680>
08      03/20/17 7:45:15.323    JobHandler_LuaUPnP::HandleActionRequest argument rand=0.5307768690290101 <0x30d90680>
02      03/20/17 7:45:15.324    luup_log:500: ElkPlugin::setTarget: Turn on control output/task/plc 16 (device 518). <0x30d90680>
02      03/20/17 7:45:15.325    luup_log:500: ElkPlugin::sendCommand: Send command: '0Ecn0160000000D3'. <0x30d90680>
.
.
.
02      03/20/17 7:45:15.357    luup_log:500: ElkPlugin::checkMessage: length=10(0x0A), message type=CC, data='0161', misc=00, checksum=E1 <0x2e623680>
02      03/20/17 7:45:15.357    luup_log:500: ElkPlugin::handlerFunc Message type description: Output Change Update <0x2e623680>
02      03/20/17 7:45:15.358    luup_log:500: ElkPlugin::processOutputReport: Output 016 is On. <0x2e623680>
06      03/20/17 7:45:15.358    Device_Variable::m_szValue_set device: 518 service: urn:upnp-org:serviceId:SwitchPower1 variable: Status was: 0 now: 1 #hooks: 0 upnp: 0 v:0xa95e48/NONE duplicate:0 <0x2e623680>
.
.
.

08      03/20/17 7:45:24.493    JobHandler_LuaUPnP::HandleActionRequest device: 518 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x30d90680>
08      03/20/17 7:45:24.495    JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=518 <0x30d90680>
08      03/20/17 7:45:24.495    JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:SwitchPower1 <0x30d90680>
08      03/20/17 7:45:24.495    JobHandler_LuaUPnP::HandleActionRequest argument action=SetTarget <0x30d90680>
08      03/20/17 7:45:24.495    JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=0 <0x30d90680>
08      03/20/17 7:45:24.495    JobHandler_LuaUPnP::HandleActionRequest argument rand=0.9053201377407433 <0x30d90680>
02      03/20/17 7:45:24.496    luup_log:500: ElkPlugin::setTarget: Turn off control output/task/plc 16 (device 518). <0x30d90680>
02      03/20/17 7:45:24.497    luup_log:500: ElkPlugin::sendCommand: Send command: '09cf01600D7'. <0x30d90680>

02      03/20/17 7:45:24.528    luup_log:500: ElkPlugin::checkMessage: length=10(0x0A), message type=CC, data='0160', misc=00, checksum=E2 <0x2e623680>
02      03/20/17 7:45:24.529    luup_log:500: ElkPlugin::handlerFunc Message type description: Output Change Update <0x2e623680>
02      03/20/17 7:45:24.529    luup_log:500: ElkPlugin::processOutputReport: Output 016 is Off. <0x2e623680>
06      03/20/17 7:45:24.530    Device_Variable::m_szValue_set device: 518 service: urn:upnp-org:serviceId:SwitchPower1 variable: Status was: 1 now: 0 #hooks: 0 upnp: 0 v:0xa95e48/NONE duplicate:0 <0x2e623680>

Unsuccessful "Arm" due to lack of pin.
Code: [Select]
08      03/20/17 7:50:49.877    JobHandler_LuaUPnP::HandleActionRequest device: 502 service: urn:micasaverde-com:serviceId:AlarmPartition2 action: RequestArmMode <0x2fd90680>
08      03/20/17 7:50:49.878    JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=502 <0x2fd90680>
08      03/20/17 7:50:49.878    JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:micasaverde-com:serviceId:AlarmPartition2 <0x2fd90680>
08      03/20/17 7:50:49.878    JobHandler_LuaUPnP::HandleActionRequest argument action=RequestArmMode <0x2fd90680>
08      03/20/17 7:50:49.879    JobHandler_LuaUPnP::HandleActionRequest argument State=Armed <0x2fd90680>
08      03/20/17 7:50:49.879    JobHandler_LuaUPnP::HandleActionRequest argument rand=0.5768327532747151 <0x2fd90680>
02      03/20/17 7:50:49.880    luup_log:500: ElkPlugin::requestArmMode: Request to arm partition 2 (device 502) to state 'Armed'. <0x2fd90680>
50      03/20/17 7:50:49.880    luup_log:500: ElkPlugin::requestArmMode: ERROR: PIN code required. <0x2fd90680>
50      03/20/17 7:50:49.881    luup_log:500: ElkPlugin::task: PIN code required.

Please note that PIN will be lost after luup restart as it is not stored, even if you use the "Store" button you need to re-enter PIN. This is not a bug.