Without millisecond accuracy on the timestamps, it’s hard to know, but it seems either the open/closed events are opposite of what they should be, or the last close event is missed in a series of opening and closing the door during one period of time.
EDIT: try turning on logging for the contact sensor and have a look at that too. Also, if you have a laptop or tablet, try opening/closing the sensor while watching the Device Details for the contact, to see if any events are getting missed / doubled.
Regarding the bounce, it is in fact registering twice. I was able to see it from inside the closet. When the contact is about an inch away, it triggers, then when the door goes fully closed, the contact triggers again. Whew, glad we got that out of the way. Now, why is this happening.
This contact sensor came from ST, has been in use in the same location doing the same thing for over a year
If you can believe it, the lag that comes from ST cloud-executed code may have been covering up that extra trigger of the contact sensor as the door closes. In any event, re-posititioning one side of the contact may help get rid of that extra trigger.