Odd “Medical” alarm

[Keith Belt]

We have a motion sensor very near the door.  The motion is set to interior-instant (also tried in perimeter-instant, got same issue).  Sometimes when entering the door and during the entry-delay period before the disarm code is entered, the motion sensor gets accidentally triggered.   Going into the ELKConnect app it properly indicates “Burglar alarm”, but when this happens, the keypad displays “Medical alarm”.

Keith

[Michael Burrell]

Keith,

Can you let me know the firmware version in the AEKP.

Thanks,

Mike

[Keith Belt]

KP-HWID_110001E0

FW-00.02.37

[Michael Burrell]

Keith,

Please update the firmware to AEKP 0.2.40. Although I am not 100% certain this will resolve the issue, there are many improvements between the version you have and the current one.

Please check your control firmware version as well to ensure it is updated. The current version is 0.5.22.

Additionally, can you share the current zone type and the options you have selected within the zone? Also, can you tell me what the history shows for the alarm event?

If possible, I would like to test and see if I can recreate this at the office.

Thanks,

Mike

[Keith Belt]

It’ll ave to update firmware later today, but in the meantime, here are the zone settings:

BURG INTERIOR (same effect if set to BURG  PERIM INST).  I had accidentally set it as a perimeter device originally, which I discovered when getting the “medical alarm” message (I thought maybe I had fat-fingered the wrong setting).  But I stillget that message now that its properly set as an interior (motion) zone.

Parameters enabled:

Bypassable

Force Arm

Interior follow

Report Alarms

Report Troubles

[Keith Belt]

Could not perform firmware update:

Went to update firmware following instructions in knowledge center.  Using the ELKConnect app on my phone, I downloaded the files, went to “system settings”, pressing the “i” icon, got what appeared to be a blue button saying “Update Firmware”. But the button doesn’t “push”.  It doen’t get screen focus or display any kind of toggle visual.  Its like its just a background image.  Nothing happens when I try to click on it.  Nothing happens in app. Nothing happens on panel.

Keith

[Michael Burrell]

Keith,

Please confirm you are connecting to the control via the local network. Since you stated you see a blue button seems to me that you are have utilized the Local Discovery option after you login to the app.

If you have connected locally, then close the app and connect again to refresh the link with the panel.

You should get a pop up on the screen when you click the blue “Update Firmware” button that will confirm it is about to restart the control. When you click yes, it will restart the panel in to the boot loader mode. This will allow you to update it.

Can you provide the firware and bootloader version currently in the control?

Thanks,

Mike

[Michael Burrell]

Also- Please let me know what version of the ElkConnect app you are utilizing. You can verify this from the “About” page of the app when not connect to a panel.

[Michael Burrell]

In reference to the Motion Zone setting. I will conduct some testing Monday to confirm this. “Interior Follow” option on the zone should prevent an alarm for that zone during entry and exit delays. Interior follower is enabled by default on the burg interior zone definition. The function of the “Interior Follow” option is to ignore activity from the zone/sensor during the entry and exit timers.

We will run some tests to Monday to confirm this is functioning as intended.

[Michael Burrell]

We conducted some testing in reference to the Interior Follower functionality. Our testing shows that this is working as intended in control firmware 0.5.22. During entry or exit delay times, activity from the Interior zone is ignored when Interior Follower is enabled.

In an effort to explain the issue you’re experiencing with the false trigger of the interior motion, is it possible that the motion detector is seeing the movement of the door and activating before the entry door is triggered? I have seen this in some rare cases with certain detectors.

 

[Keith Belt]

The motion detector is not in a position to see any doors.  After seeing this a couple of times when going in and out of the garage door (which is farther away), I did a test at the front door (where the keypad is and the suspect motion detector is just around the corner), so that I could observe the keypad while selectively triggering items.  It was very repeatable and clearly triggers a medical alarm during an entry delay.  I did not check what happens when the motion is triggered during an exit delay, or by itself when the system is armed, or try with a different motion detector.  I can do those tonight and those might provide additional clues.

PS.  Since interior follower is enabled by default, I wasn’t thinking about that issue, but you’re right, the motion sensor should essentially be ignored.  So I guess its two things — 1) why isn’t it being ignored, and 2) why is it causing a medical alarm?

Responses to above questions:

I assume I’m connecting via the local network. I’m connecting via the app on my phone.  The E27 is ethernet hardwired and my phone is connected to WIFI, but they’re the same router.

I don’t really have to use the “Local Discovery” feature since the E27 is already “discovered” and showing as a panel selection to pick from as soon as the app opens (its the only E27 panel I have right now).  I have tried logging out, force stopping the app, and rebooting the phone, to start everything from scratch, but no change in behavior.

Current (un-updated):  Panel:  Hardware version: 0.1.4,   Firmware version: 0.4.73,  Bootloader version: 0.2.23,    ELKConnect:  version 0.12.179, build: 179

 

[Michael Burrell]

Keith,

I appreciate the detailed response.

Medical Alarm Display Issue: Control Version 0.5.73 is causing the mismatch where the Burg Alarm on the App/Control is displaying as a Medical Alarm on the keypad. In version 0.2.37 of the keypad firmware and in version 0.4.82 of the control, we updated the alarm priority display list. Since you have an older version of control firmware with a newer version of keypad firmware, they are out of sync. Without getting too deep into the weeds here, the control has a priority list that informs the keypad what to display on the “top line” of the keypad. The keypad screen is divided into two display lines. The top line can show messages like BURG ALARM, FIRE ALARM, or FIRE TROUBLE. These top-line messages are fixed and not editable by the installer. The bottom line is the variable line that shows zone names, etc. The display of these top-line messages is based on a “Priority Byte” sent to the keypads during an event. Essentially, the Control is sending the priority number which it thinks is for a BURG ALARM, but the Keypad has an updated priority number list that shows that as a MEDICAL ALARM. So, it displays that. In this case, your keypad has the updated list, but the control has older firmware and the out of date list. For a keypad with 0.2.37 or higher firmware to display properly, you will need to update the control to 0.4.82 or higher. I suggest 0.5.22 as there are many improvements.

Panel Firmware Update: You have to use Local Discovery to connect to the panel if you want to update firmware. Clicking on the Local Discovery button will present you with a local discovery panel list. This is how you connect locally. If you use the “cloud list” that shown on the page with the “Start Local Discovery” button, it will create a remote connection via the cloud and block firmware updating. We currently do not allow firmware to be updated when connected via the cloud list. The local discovery function works differently than M1; you can use this when you are on the same network as the control to connect for configuration. Certain settings in the control are not allowed while remote, such as updating firmware and disabling the cloud connection (0.5.22).

Here is a link to the firmware notes: https://www.elkproducts.com/alarm-engine-support/ae-update-info/

There are major improvements from 0.4.82 control firmware and up. Please look over the release notes linked above. Also, please update the keypad as well. There are many user improvements in keypad firmware 0.2.40 based on field feedback.

We addressed several issues related to zone behavior by doing a full rework of the zone attributes in 0.4.82 control firmware. I recommend updating to 0.5.22 and test to see if it resolves the issue with the interior follower.

I apologize for the need to update firmware, I realize this is burdon to do this, but it is our only means of addressing these issues when they are reported. We are working towards remote updating of firmware to remove the requirement for being onsite with the control.

Thanks,
Mike

 

 

 

[Keith Belt]

Glad you found an explanation.  Will update everything at first opportunity.

K.

[Author]

Posts