This is strange ... if you check the recent history of that master bedroom sensor, do you see it closing and opening again at the same time of the intrusion detection?
It does actually, any idea as to why? I’ve left the window open and haven’t touched it at all over the past two to three days. It didn’t have this issue the first night either.
Actually now that I’m looking at it, it seems like a lot of sensors on my third board, which I’ve reserved for upstairs, are having this issue. The loft window hasn’t been touched in a while either but history shows that it was closed and reopened within one minute. Could there be an issue with my konnected board?
If it's very hot, then it needs to be replaced and will probably completely fail soon. This happens sometimes.
See this article for steps to request a replacement: https://help.konnected.io/support/solutions/articles/32000023767-device-is-not-responsive-and-gets-hot
Anyone find an answer to the false alarms? I’m getting several intrusion notifications on SHM for wired sensors on two different doors. Open/close sensors show open and close at the exact same time on two different doors (not all three) wilhich trigger the notification in SmartThings. Neither door was open at the time. Any ideas appreciated.
False alarms are not expected and only a very, very small number of users have reported problems like this. We assume that false alarms are caused by problems related to aging sensors or wiring. Use a multimeter to measure the resistance on the sensor loops -- it should be near 0. If you measure more than a few ohms of resistance on the line, that may indicate a failing sensor or wire.
FYI -- debouncing would not help this problem. Konnected software already limits one state change per 200ms. Debouncing means to collapse multiple back-to-back state changes into one. It would not help in this case because the first open/close would still be reported.