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

Offline bucko

  • Hero Member
  • *****
  • Posts: 637
  • Karma: +26/-7
    • Travel and Living in China
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #585 on: December 11, 2017, 05:48:19 am »
Now for 1 more issue. Clicking Troubleshoot in the Alarm Panel Plugin returns  "setCpanelContent is not defined"

Before in UI5 this would display any trouble conditions in my ELK. So what variable do I need to add to pull a trouble list? Everything else is working.
Vera 3, 40+ Fibaro relays & dimmers, IPUX cams, Elk M1 Gold, M1XEP, M1SP, XVOR, M1RB, Elk124, Monoprice HDMI matrix & 6 zone amp, Denon AVR, Panasonic A8000, BI DV,On Controls

Offline bucko

  • Hero Member
  • *****
  • Posts: 637
  • Karma: +26/-7
    • Travel and Living in China
Pin code error solved?
« Reply #586 on: January 25, 2018, 10:32:41 pm »
The ongoing Pin code  "invalid pin code" , has it been solved at this point for UI7?

After extensive testing my Vera this error is causing my Vera to reload DURING a disarm only. Result is that although the Elk does disarm, no Pleg actions get fired because Vera is reloading.

Funny enough ARMING with this error does not crash Vera and everything does work fine.

But no doubt DISARM is disrupting things from happening other than the Elk panel disarming fine.

Any cure yet to make this error go away?
Vera 3, 40+ Fibaro relays & dimmers, IPUX cams, Elk M1 Gold, M1XEP, M1SP, XVOR, M1RB, Elk124, Monoprice HDMI matrix & 6 zone amp, Denon AVR, Panasonic A8000, BI DV,On Controls

Offline GregM123

  • Newbie
  • *
  • Posts: 4
  • Karma: +1/-0
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #587 on: March 05, 2018, 11:21:10 am »
Hi @zoot1612. My apologies for the delay in posting the logs. I tried digging into it my self but am not sure where to start. My gut feel is that there are two issues.

1) Some of the devices need configuration changes:
  • The PLC lights controlled by the Elk it to present with an On/Off and/or dimmer control in the app.
  • The thermostat data is all in the Vera. I think they made a change at some point at time and it does not show correctly in the user interface. If I request the data in a browser window via the following URL, I can see that all the info looks correct. http://192.168.100.227:3480/data_request?id=status&output_format=xml&DeviceNum=61
2) The message going to the Elk to turn the lights on and off is correct. The response however is not being mis-interpreted.


The following is from making a web request for xml data regarding one of the thermostats via the url above.

<root Using_2G="0" LoadTime="1519887624" DataVersion="887632573" UserData_DataVersion="887624162" TimeStamp="1519926778" lights_on="0" lights_off="2" doors_locked="1" doors_unlocked="0" sensors_tripped="0" sensors_not_tripped="17" failed_devices="0" visible_devices="103" partitions_active="0" partitions_notactive="1" ZWaveStatus="1" Mode="1" LocalTime="2018-03-01 10:52:58 D">
<Device_Num_61 PendingJobs="0" status="-1">
<states>
<state id="139" service="urn:upnp-org:serviceId:HVAC_FanOperatingMode1" variable="Mode" value="ContinuousOn"/>
<state id="140" service="urn:upnp-org:serviceId:HVAC_UserOperatingMode1" variable="ModeStatus" value="HeatOn"/>
<state id="141" service="urn:upnp-org:serviceId:TemperatureSensor1" variable="CurrentTemperature" value="19"/>
<state id="142" service="urn:upnp-org:serviceId:TemperatureSetpoint1_Heat" variable="CurrentSetpoint" value="20"/>
<state id="143" service="urn:upnp-org:serviceId:TemperatureSetpoint1_Cool" variable="CurrentSetpoint" value="27"/>
<state id="144" service="urn:micasaverde-com:serviceId:HaDevice1" variable="Commands" value="hvac_off,hvac_auto,hvac_cool,hvac_heat,heating_setpoint,cooling_setpoint,fan_auto,fan_on"/>
<state id="145" service="urn:micasaverde-com:serviceId:HaDevice1" variable="ModeSetting" value="1:;2:;3:;4:"/>
<state id="146" service="urn:micasaverde-com:serviceId:HaDevice1" variable="LastUpdate" value="1519926402"/>
<state id="147" service="urn:micasaverde-com:serviceId:HaDevice1" variable="Configured" value="0"/>
</states>
<Jobs/>
<tooltip display="0"/>
</Device_Num_61>
<alerts>...</alerts>
</root>


Here are some clips from the log.

Turning an Elk Output on. Works great everytime.

01   03/01/18 10:26:32.761   sbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfo <0x72fc9520>
08   03/01/18 10:26:32.761   JobHandler_LuaUPnP::HandleActionRequest device: 38 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x72fc9520>
08   03/01/18 10:26:32.761   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=38 <0x72fc9520>
08   03/01/18 10:26:32.761   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:SwitchPower1 <0x72fc9520>
08   03/01/18 10:26:32.762   JobHandler_LuaUPnP::HandleActionRequest argument action=SetTarget <0x72fc9520>
08   03/01/18 10:26:32.762   JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=1 <0x72fc9520>
08   03/01/18 10:26:32.762   JobHandler_LuaUPnP::HandleActionRequest argument rand=0.26124631544908716 <0x72fc9520>
02   03/01/18 10:26:32.763   luup_log:12: ElkPlugin::setTarget: Turn on control output/task/plc 14 (device 38). <0x72fc9520>
02   03/01/18 10:26:32.763   luup_log:12: ElkPlugin::sendCommand: Send command: '0Ecn0140000000D5'. <0x72fc9520>
02   03/01/18 10:26:32.788   luup_log:12: ElkPlugin::checkMessage: length=10(0x0A), message type=CC, data='0141', misc=00, checksum=E3 <0x72dc9520>
02   03/01/18 10:26:32.789   luup_log:12: ElkPlugin::handlerFunc Message type description: Output Change Update <0x72dc9520>
02   03/01/18 10:26:32.789   luup_log:12: ElkPlugin::processOutputReport: Output 014 is On. <0x72dc9520>
06   03/01/18 10:26:32.789   Device_Variable::m_szValue_set device: 38 service: urn:upnp-org:serviceId:SwitchPower1 variable: Status was: 0 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0x126e938/NONE duplicate:0 <0x72dc9520>
04   03/01/18 10:26:36.208   <Job ID="1362" Name="pollnode #4 1 cmds" Device="7" Created="2018-03-01 10:26:36" Started="2018-03-01 10:26:36" Completed="2018-03-01 10:26:36" Duration="0.107335000" Runtime

Turning on a light controlled by the elk. The light turns on and off reliably but the status does not update correctly. Can only be done via web interface.

01   03/01/18 10:31:12.371   sbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfo <0x737c9520>
08   03/01/18 10:31:12.371   JobHandler_LuaUPnP::HandleActionRequest device: 134 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x737c9520>
08   03/01/18 10:31:12.372   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=134 <0x737c9520>
08   03/01/18 10:31:12.372   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:SwitchPower1 <0x737c9520>
08   03/01/18 10:31:12.372   JobHandler_LuaUPnP::HandleActionRequest argument action=SetTarget <0x737c9520>
08   03/01/18 10:31:12.372   JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=1 <0x737c9520>
08   03/01/18 10:31:12.372   JobHandler_LuaUPnP::HandleActionRequest argument rand=0.6247034521985222 <0x737c9520>
02   03/01/18 10:31:12.373   luup_log:12: ElkPlugin::setTarget: Turn on control output/task/plc 20 (device 134). <0x737c9520>
02   03/01/18 10:31:12.373   luup_log:12: ElkPlugin::sendCommand: Send command: '09pnB0400B3'. <0x737c9520>
02   03/01/18 10:31:12.432   luup_log:12: ElkPlugin::checkMessage: length=11(0x0B), message type=PC, data='B0401', misc=00, checksum=94 <0x72dc9520>
02   03/01/18 10:31:12.433   luup_log:12: ElkPlugin::handlerFunc Message type description: PLC Change Update <0x72dc9520>
01   03/01/18 10:31:12.433   luup_variable_set interface 0x12bd548 no Status/(null) <0x72dc9520>
02   03/01/18 10:31:12.434   luup_log:12: ElkPlugin::plcChangeUpdate: House Code B, Unit 4 set too 1 <0x72dc9520>
01   03/01/18 10:31:33.263   sbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfo <0x73fc9520>
08   03/01/18 10:31:33.264   JobHandler_LuaUPnP::HandleActionRequest device: 134 service: urn:upnp-org:serviceId:SwitchPower1 action: SetTarget <0x73fc9520>
08   03/01/18 10:31:33.264   JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=134 <0x73fc9520>
08   03/01/18 10:31:33.264   JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:SwitchPower1 <0x73fc9520>
08   03/01/18 10:31:33.265   JobHandler_LuaUPnP::HandleActionRequest argument action=SetTarget <0x73fc9520>
08   03/01/18 10:31:33.265   JobHandler_LuaUPnP::HandleActionRequest argument newTargetValue=0 <0x73fc9520>
08   03/01/18 10:31:33.265   JobHandler_LuaUPnP::HandleActionRequest argument rand=0.7573343415294562 <0x73fc9520>
02   03/01/18 10:31:33.266   luup_log:12: ElkPlugin::setTarget: Turn off control output/task/plc 20 (device 134). <0x73fc9520>
02   03/01/18 10:31:33.266   luup_log:12: ElkPlugin::sendCommand: Send command: '09pfB0400BB'. <0x73fc9520>
02   03/01/18 10:31:33.313   luup_log:12: ElkPlugin::checkMessage: length=11(0x0B), message type=PC, data='B0400', misc=00, checksum=95 <0x72dc9520>
02   03/01/18 10:31:33.313   luup_log:12: ElkPlugin::handlerFunc Message type description: PLC Change Update <0x72dc9520>
01   03/01/18 10:31:33.314   luup_variable_set interface 0x12bd548 no Status/(null) <0x72dc9520>
02   03/01/18 10:31:33.314   luup_log:12: ElkPlugin::plcChangeUpdate: House Code B, Unit 4 set too 0 <0x72dc9520>
04   03/01/18 10:31:36.213   <Job ID="1372" Name="pollnode #4 1 cmds" Device="7" Created="2018-03-01 10:31:36" Started="2018-03-01 10:31:36" Completed="2018-03-01 10:31:36" Duration="0.111534000" Runtime="0.111001000" Status="Successful" LastNote="" Node="4" NodeType="ZWaveDimmableLight" NodeDescription="Lamp"/> <0x765c9520>
02   03/01/18 10:31:36.213   Device_Basic::AddPoll 7 poll list full, deleting old one <0x765c9520>
06   03/01/18 10:31:36.214   Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:HaDevice1 variable: PollRatings was: 5.00 now: 5.00 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x765c9520>
06   03/01/18 10:31:36.214   Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: LastPollSuccess was: 1519925346 now: 1519925496 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x765c9520


Let me know how I can help. I have done some basic messaging with my Elk system and understand the portocol.


Greg

Offline Quixote

  • Sr. Member
  • ****
  • Posts: 287
  • Karma: +10/-32
Re: Elk M1 (and M1 M1EZ8) Alarm Panel Plugin
« Reply #588 on: April 22, 2018, 05:37:19 pm »
Without digging through logs just yet, are there any known issues with triggering scenes using the Elk automation tasks?
I'm a little stumped as to why they aren't working when it seems that everything else is just fine.

Thanks in advance.
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.