BUG: Contact Sensors Not Triggering Alarm Properly

[indycarbruce]

Bug Description
• I have the Konnected plugin version 1.3.1. I have the following problems:

1. I’m testing two zones on a new Alarm Pro Conversion board with a couple of contact sensors. Temporarily, I set up a 10 sec Exit delay and a 10 sec Entrance delay. After the buzzer does the countdown and the system is armed, if I pull the magnet away to simulate an open window, the sensor DOESN'T trigger the countdown to activate the alarm siren (but does change from "closed" to "open" on my accessories screen). But if I just pull the magnet away momentarily and put it back, then it DOES trigger the countdown to activate the alarm siren. I also tested this with a jumper wire with alligator clips and had the same results.
2. I armed the system for AWAY and did the above same procedure BEFORE the EXIT delay was finished. The Entrance countdown was triggered and the siren sounded.
   This happens every time. I did try deleting my cached accessories and deleting the panel to start over because I had played around with various binary sensors and more zones. After deleting the cache & starting over I set up a single zone with a contact sensor and re-tested. Still having the same problems.

Steps To Reproduce

1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error

Expected Behavior

1. For entrance, if a door or window is opened when the system is alarmed, it should trigger the entrance delay timer, then the siren should sound. This should be regardless of whether the door or window remains open or the person closes it again after entry. Currently, I have to trigger the binary sensor like a momentary push switch.
2. For exit, the alarm siren should not be triggered if a door is opened and re-closed within the specified exit delay time. This is not happening the way it should.

Environment

• Homebridge System:

  • o Node.js Version: v18.12.1
    o NPM Version: (I don’t know where to find this)
    o Homebridge/HOOBS Version: v1.6.0
    o Operating System: Raspian GNU/ Linux Bullseye (11)

• Konnected Panel(s):

  • o Panel Hardware Version: Konnected Pro Conversion Kit/ 1.3.3
    o Firmware Version: 1.0.1-169549
    o Addon Panel(s): N/A
    o Interface Panel(s): N/A

Attach Files to Support Your Experience

Homebridge config.json file:
{
"name": "Konnected",
"advanced": {
"entryDelaySettings": {
"delay": 10,
"pulseDuration": 900,
"pulsePause": 100,
"pulseRepeat": 10
},
"exitDelaySettings": {
"delay": 10,
"audibleBeeperModes": [
"0",
"2",
"1"
]
}
},
"panels": [
{
"name": "Konnected Pro",
"uuid": "8f655392-a778-4fee-97b9-4324d7eba588",
"ipAddress": "192.168.1.31",
"port": 9123,
"blink": true,
"zones": [
{
"enabled": true,
"zoneNumber": "1",
"zoneType": "contact",
"zoneLocation": "Entrance",
"binarySensorSettings": {
"invert": true,
"audibleBeep": true,
"triggerableModes": [
"2",
"1"
]
}
},
{
"enabled": true,
"zoneNumber": "out1",
"zoneType": "beeper",
"zoneLocation": "Utility Room",
"switchSettings": {
"pulseDuration": 900,
"pulsePause": 100,
"pulseRepeat": 10,
"triggerableModes": [
"0",
"2",
"1"
]
}
},
{
"enabled": true,
"zoneNumber": "alarm1",
"zoneType": "siren",
"zoneLocation": "Kitchen",
"switchSettings": {
"triggerableModes": [
"0",
"2",
"1"
]
}
}
]
}
],
"platform": "konnected"
}

homebridge.log.txt

shooting#understanding-where-your-files-are-macos).

Additional Relevant Information
Replace this text with any other context about the problem here.

[indycarbruce]

Mike,
I'm new to all of this. It took some clicking around just to figure out that you moved my issue here. Anyway, what is the process? (I'm not even sure if this is the right way to contact you...)
Thanks

[mkormendy]

This is the correct place! This and Discord which I see you're on now.

[indycarbruce]

Thanks, I was just checking before going back to my woodshop. So is this an actual bug or did I do something wrong on my configuration? Any idea how long to solve this? Days? Weeks? Months? I think I explained problem #1 ok, but did you understand what I meant by the second problem (triggering alarm before Exit delay times out)? If I need to clarify anything let me know. Hope you can help as I'm really looking forward to telling ADT I don't need them any more. :)

[mkormendy]

I would turn off the triggerable modes for any switch type (Alarm Beeper Switches and Alarm Siren Switches in your case). That was an experimental feature and I will be removing that in the future. Try testing with that after.

[mkormendy]

I have tested the first bullet scenario with my setup and I cannot reproduce the same result. I open the sensor and leave it open and the countdown time begins and then proceeds to trigger the alarm siren after the entry delay of 10 seconds is reached. The result of countdown and alarm siren trigger also occurs when the sensor is momentarily opened and closed.

I believe the reason why this is happening is due to you enabling the experimental feature of the triggerable modes for any switch type (Alarm Beeper Switches and Alarm Siren Switches in your case) - disable/stop-using them in the configuration of those switch zones.

What was interesting however, was that I did reproduce the second bullet scenario where a sensor was opened (and also a case where it was subsequently closed) while the exit delay of 10 seconds was occurring and noticed that it still triggers the alarm siren, upon reaching the exit delay completion. This is a bug and I will have to publish a new release.

Time wise, I have no estimate on when this will be fixed. I am travelling for 5 weeks starting Sunday. I will see if I can bring the dev hardware with me so I can work on the software with it but no guarantees until I come back.

[indycarbruce]

Mike, I tried your suggestion (uncheck the boxes for the trigger able modes for and both the alarm beeper switch and alarm siren switch) but the problems are still occurring. I tried rebooting the device and re-re-starting Homebridge too. I also tried changing the exit delay to the default 30 seconds. It still does it.

I'm baffled as to why you're not seeing the problem with scenario #1 and I am. I wonder if I should "delete" the panel in Homebridge and clear the accessories cache and start over. Or reset Homebridge and start over. Konnected is the only Homebridge app I've set up so far. (I have Camera UI too, but noting configured.)

Thanks,
Bruce W

[mkormendy]

What does your config look like? Can you send what it looks like now in discord in the thread I created?

[indycarbruce]

Mike, I played around with it some more and now I'm getting the same results as you are. I had bought some cheap window sensors from Amazon to test the circuit. They have 3 wires to have N.O. and N.C. setups. Anyway, I was using the Normally Open wires and had the binary contact switch for Zone 1 set for "Invert the Sensor Zone State" so Zone 1 would indicate "Open" when the magnet was pulled away. So tonight I unchecked the box, tried again, same problem if I recall correctly. Next I changed wires for "Normally Closed" on my window sensor with the box unchecked for Zone 1. Now it triggers the alarm siren as it should.

But I'm still having the second problem of triggering the alarm before the exit delay times out.

[indycarbruce]

Did more testing, here's my summary (Note: ITSZS= Invert The Sensor Zone State")
N.O. Sensor, ITSZS=True; Problem #1: YES; Problem #2: YES
N.O. Sensor, ITSZS=False; Problem #1: YES; Problem #2: YES
N.C. Sensor, ITSZS=True; Problem #1: NO; Problem #2: YES
N.C. Sensor, ITSZS=False; Problem #1: NO; Problem #2: YES

Goodnight & thank you for all the follow ups!

[mkormendy]

If I remember correctly, there is documentation somewhere on the Konnected website that says that the zones work best if the sensors are set to normally closed.
The following scenarios are unexpected (!) but I don't know how to test for that since I don't have a sensor that works like that on hand:

N.O. Sensor, ITSZS=True; Problem #1: YES;
N.O. Sensor, ITSZS=False; Problem #1: YES;

I think if your sensor can be normally closed,... that's likely the safest bet.

As for Problem #2, that seems to be something I need to review in my own code and test some fixes.

[indycarbruce]

I checked one window and one door sensor on my ADT system and fortunately they're normally closed.

For what it's worth, Konnected recommends normally open for contact sensors, but normally closed for motion sensors. That seems inconsistent to me. Here are the links:

https://help.konnected.io/support/solutions/articles/32000022618-wiring-your-window-and-door-sensors
https://help.konnected.io/support/solutions/articles/32000022628-wiring-your-motion-sensors

[indycarbruce]

Mike, I’m still not sure about using the Github Discord.  Have you made any progress on my Problem #2 of “Contact Sensors Not Triggering Alarm Properly (Issue #33)”? Thanks, Bruce Wolfe

[indycarbruce]

Mike,
I'm not sure if my messages are getting to you. Have you made any progress on Problem #2 of Issue #33?
Thanks,
Bruce Wolfe

[mkormendy]

Hey Bruce, I am receiving your messages. I have not made any progress. I have been placing other personal items in my life ahead of this project.

[indycarbruce]

Thanks for the reply.  I believe this plugin is kind of a side thing from your normal job & life.  So I can understand prioritizing personal matters before this. Anyway,  for now I will try a work-around by putting a timer switch in parallel with the door switch-  hit the timer button, arm the system, exit the door/ close the door.