Hi, I’m seeing some strange behavior in my system, and have a question regarding “latest” system state vs what I see in my IDE event logs.
I have a contact that exhibits bounce on a garage door, and I am seeing the wrong state be reported to my smartapps (triggering incorrect notifications). When I look at the IDE event log, the “order” of reported state is wrong, although the timestamps seem to be correct. To clarify (look @ log example below), when the door closed the last IDE log’s “close” timestamp 5:56:19.498 is shown BEFORE the “open” timestamp 5:56:19.493 – i.e. out of order. Also the current state of the contact in IDE is shown as “open”, which is wrong.
So I’m guessing that events “close” together (100’s of ms) may be incorrectly handled by the ST system? Can anyone confirm this or give me suggestions on a workaround (other than getting a different physical device)? If it matters, I’m using the Xiaomi Door/Window Sensor as DTH. Maybe I can customize it somehow to add a debounce feature internal to the DTH?