rccoleman Posted March 23, 2016 Posted March 23, 2016 I was running a level 3 event trace today to try to capture a weird LampLinc issue and I noticed that I get a lot of seemingly random chatter from my Elk keypads. Lots of stuff like this: Tue 03/22/2016 04:40:03 PM : [ELK 0 0 1] Keypad : Front Door : 75 (113/135/0) Tue 03/22/2016 04:41:16 PM : [ELK 0 0 1] Keypad : Front Door : 74 (113/134/0) Tue 03/22/2016 04:45:16 PM : [ELK 0 0 1] Keypad : Front Door : 75 (113/135/0) Tue 03/22/2016 04:52:12 PM : [ELK 0 0 1] Keypad : Front Door : 73 (113/133/0) Tue 03/22/2016 04:54:20 PM : [ELK 0 0 1] Keypad : Front Door : 72 (113/132/0) Tue 03/22/2016 04:58:19 PM : [ELK 0 0 1] Keypad : Front Door : 73 (113/133/0) Tue 03/22/2016 05:06:19 PM : [ELK 0 0 1] Keypad : Front Door : 74 (113/134/0) Tue 03/22/2016 05:16:26 PM : [ELK 0 0 2] Keypad : Master Bedroom : 72 (113/132/0) Tue 03/22/2016 05:19:22 PM : [ELK 0 0 2] Keypad : Master Bedroom : 71 (113/131/0) Tue 03/22/2016 05:20:26 PM : [ELK 0 0 2] Keypad : Master Bedroom : 72 (113/132/0) Tue 03/22/2016 05:23:04 PM : [ELK 0 0 1] Keypad : Front Door : 75 (113/135/0) Tue 03/22/2016 05:24:08 PM : [ELK 0 0 1] Keypad : Front Door : 74 (113/134/0) Tue 03/22/2016 05:26:32 PM : [ELK 0 0 2] Keypad : Master Bedroom : 71 (113/131/0) Tue 03/22/2016 05:27:20 PM : [ELK 0 0 2] Keypad : Master Bedroom : 72 (113/132/0) Tue 03/22/2016 05:28:07 PM : [ELK 0 0 1] Keypad : Front Door : 75 (113/135/0) Tue 03/22/2016 05:34:31 PM : [ELK 0 0 2] Keypad : Master Bedroom : 71 (113/131/0) These happened while nobody was home, but others have shown up since I've been home and there's no indication of any violation or issue with the panel. I initially thought that it was the system changing back and forth between ready-to-arm and force-arm as I walked past motion detectors, but then I saw these messages when nobody was home. I don't see any interesting information in the Elk log either - just me arming the alarm in the morning and disarming it when I came home. Is there any documentation on what all of the fields mean, either from ISY or from Elk? Thanks, Rob
J_Barrett Posted March 23, 2016 Posted March 23, 2016 I believe that's the temperature from the keypad Jimmy
rccoleman Posted March 23, 2016 Author Posted March 23, 2016 Ah, I hadn't noticed that. So maybe 113 means 'keypad temp', and the middle number is the actual temp+60? I wonder what significance that has. In any case, I'm sure you're correct about the log entries. Thanks!
Chris Jahn Posted March 24, 2016 Posted March 24, 2016 Hi rccoleman, The (113/132/0) in the log entry is (eventType / raw Value / endpoint) - The eventType is one of the events listed below - The raw value is the raw value sent to us from Elk. - The endpoint number indicates which output, key, thermostat this came from. Therefore 113/132/0 is Elk Keypad Temperature with raw value 132 (72 degrees) Here's an informal list of the events Topology Changed 1 Elk Area 2 Elk Area Alarm State 1 Elk Area Arm Up State 2 Elk Area Armed State 3Elk Zone 3 Elk Zone Logical Status 51 Elk Zone Physical Status 52 Elk Zone Voltage 53 Elk Zone Alarm Def 54 Elk Zone Bypass State 55 Elk Zone Temperature 56Elk Keypad 4 Elk Keypad Access Code 101 Elk Keypad Beep Mode 102 Elk Keypad Chime Mode 103 Elk Keypad Key Action 111 Elk Keypad Key Pressed 1 Elk Keypad Key Led 112 Elk Keypad Temperature 113Elk Output 5 Elk Output Status 121Elk System Status 6 Elk System Status Is Connected 156 Elk System Status Is Enabled 157Elk Tstat 7 Elk Tstat Mode 191 Elk Tstat Hold 192 Elk Tstat Fan 193 Elk Tstat Temp 194 Elk Tstat Heatsp 195 Elk Tstat Coolsp 196 Elk Tstat Humidity 197
G W Posted November 21, 2016 Posted November 21, 2016 Chris, Mon 11/21/2016 11:10:33 : [ELK 0 0 2] Keypad : Garage Door : F4 = AC Power LED Off (112/0/4) Mon 11/21/2016 11:10:33 : [ELK 2 0 2] Keypad : Garage Door : (102/0/0) Mon 11/21/2016 11:11:49 : [ELK 0 0 2] Keypad : Garage Door : F4 = AC Power LED On (112/1/4) How can this be read from the REST API so Agave can use this data?
Chris Jahn Posted November 21, 2016 Posted November 21, 2016 Chris, Mon 11/21/2016 11:10:33 : [ELK 0 0 2] Keypad : Garage Door : F4 = AC Power LED Off (112/0/4) Mon 11/21/2016 11:10:33 : [ELK 2 0 2] Keypad : Garage Door : (102/0/0) Mon 11/21/2016 11:11:49 : [ELK 0 0 2] Keypad : Garage Door : F4 = AC Power LED On (112/1/4) How can this be read from the REST API so Agave can use this data? Hi Gary, The only way to get these values is via subscription. The 'get status' REST API for keypads only returns the temperature, not these particular values.
G W Posted November 21, 2016 Posted November 21, 2016 Hi Gary, The only way to get these values is via subscription. The 'get status' REST API for keypads only returns the temperature, not these particular values. Okay. When will the Elk Module be updated? There is so much data available and the Elk Module just doesn't pass it on. B.R.I.A.D.A. Best regards, Gary Funk
Chris Jahn Posted November 21, 2016 Posted November 21, 2016 Okay. When will the Elk Module be updated? There is so much data available and the Elk Module just doesn't pass it on. B.R.I.A.D.A. Best regards, Gary Funk Its not on the radar right now, but the earliest we could start work on it would be after the 5.0.x official release. Just to be clear, using the REST API you can get status for Areas, Zones, Thermostats, Outputs, etc., its only keypads that we'd have to take another look at.
G W Posted November 21, 2016 Posted November 21, 2016 I'm looking to get information on the 400+ events that the M1 can broadcast. Particularly AC Failure and Control Low Battery, as these are critical security issues. B.R.I.A.D.A. Best regards, Gary Funk
Chris Jahn Posted November 21, 2016 Posted November 21, 2016 I'm looking to get information on the 400+ events that the M1 can broadcast. Particularly AC Failure and Control Low Battery, as these are critical security issues. B.R.I.A.D.A. Best regards, Gary Funk In doing an update, we would not limit our changes to just keypads. We would take a look at anything else Elk has added to the API or that we are missing in their current API. The values that you are referencing are available in their new API (System Trouble Status). The common workaround for all of this is to set outputs in Elk when any of these conditions occur, and then use those outputs in programs conditions in the ISY.
G W Posted November 21, 2016 Posted November 21, 2016 Thank you Chris. I will patiently await the new release. B.R.I.A.D.A. Best regards, Gary Funk
Scottmichaelj Posted November 23, 2016 Posted November 23, 2016 I'm looking to get information on the 400+ events that the M1 can broadcast. Particularly AC Failure and Control Low Battery, as these are critical security issues. B.R.I.A.D.A. Best regards, Gary Funk Exactly +1
Recommended Posts
Archived
This topic is now archived and is closed to further replies.