That's good news. Neat looking unit. I suspect in my case I have an overly .... sensitive sensor that could use replacing, but that the old Honeywell system was able to overcome the tolerance issues.
We're considering adding a trigger time feature that would allow you to configure certain zones to trip if they were open for more than a specified amount of time. This may help with these very brief false triggers. Do you think this would resolve the problem?
I troubleshot this morning and found the carport door was staying open when I closed it in home assistant (Hass). I have been doing opens/closes all year and finally this happened. Next, I pulled the switch out to examine it, then I pushed it back in but left it high and closed the door. Hass marked it as closed. I fully recessed it and found it open when performing the test again. Again! Not the fault of Konnected!
Lastly, I put a plastic shim between it which keeps it raised and the door is marked as closed.
I have no experience with servicing these switches. I found them on Amazon and you can get a pack of 5 or more for around $10. Does anyone know if it is best to replace this or design a permanent shim? I wouldn't want to order and replace and it turns out it just needs to be closer to the magnet field.
Nate, thanks for looking into this directly. In my case I never had a false alarm with the Honeywell/Ademco setup ever. Upon moving to Konnected it happened in multiple zones, multiple times. It got to the point where we stopped relying on the system (not good) and then Covid happened so we're essentially always home so this become less of a priority for now.
My view is simple. The false alarms are happening in a way that it's clear that the sensor is "tripping" for literally a moment. If ANY option existed that essentially would allow for setting a sensitivity before triggering, I think that would do it. For example, If a window sensor only goes off for half a second, that's clearly not a break-in. Something else is happening. It'd be great if that could be logged somewhere, but not set off the alarm. If the window sensor triggers and runs for a full second, that may indeed be an issue. Same for a door sensor.
Hi guys... I recently installed the Konnected Alarm Pro system and am having this same problem. See the list of events below:
All these occurred with no windows actually operated. It only occurs with one pair of windows open, in which both sensors are wired in a series to one pair of wires in the zone. Any other windows open in that zone does not trigger this. My electronics engineer friend thinks that when one of those windows is open, that sensor circuit is open and the wire pair essentially become an antenna for any electrical noise induced from any AC wires that it may run near. These would expectedly happen at random and quickly. It would also vary greatly from one installation to another and from one zone to another, depending on how the system wires were routed throughout your home.
My previous system was a PowerSeries PC1616. I noticed in its installation manual that it had an option to enable "Fast Loop Response", which would trigger zone changes within 36 ms. Otherwise, its default is 400 ms. I do see that most of my paired close/open events are under 400 ms. So I suspect I was not seeing these false alarms with the old system due to the default event coalesce timing of 400 ms.
@Nate - Your comment above to add a trigger timing feature for each zone would greatly help with this and mirror the solution other vendors are using.
Until Konnected can fix this, I will create a virtual contact sensor device for that zone in Hubitat and use a rule in Hubitat to collapse the quick events from the real device into a single update on the virtual device.
I've taken to just not setting the alarm due to this -- unless we're literally leaving the house for a period of time. Thankfully, since this became a concern someone has always been here (son living at home).
I am getting false alarms on multiple zones. Has anyone solved this? It's like a sensor is trigged like 8 times less than a second. It's to the point where I don't trust the system. I read through the forum but don't see anything current to address this.
I am using the interface boards.
I had these same problems a few years ago, after installing my Konnected board and integrating the Konnected system with my home automation system. I discovered that on my downstairs window zone, one pair of windows would signal close then open, in quick succession, when one of those windows were open. This would trigger that zone on Konnected to close/open within milliseconds of each other, which would trigger the same on my home automation.
After some research, I suspect the sensor wires for those windows probably ran too closely to line, or even high, voltage wires within the home structure, which placed noise on those sensor wires, which randomly Konnected interpreted as the wire pair going close/open. I contacted Konnected about this and advised they provide a way to "dial-in" the sensitivity on the Konnected board or in their firmware. I thought I saw a future software release even announcing some feature like that, but never saw it show up in the software.
I only use the Konnected board and software to integrate with my home automation. I don't use any other Konnected features. So I ended up working around this problem with my home automation system. In my home automation, I implement the internal downstairs window zone, which is a direct link to the Konnected zone. I also implement an external downstairs window zone, which is used for all automations, announcements, alarms, etc. I then use a rule to watch for changes on the internal zone, and only if no other changes appear within 2 seconds, I set the external zone. If multiple changes happen within that 2 second time slot, I only process the last one. This causes my home automation to throw out the close event, since another open event happens within milliseconds.
Good luck with your solutions.
Thanks Troy. I do wonder if the sensors are close to the line voltage. Although the system worked fine as a standard Honeywell system for many years without issue. Only now because I integrated Konnected am I seeing issues. I am only using the Konnected Interface board with the SmartThings. (Which isn't so smart!)