Timeout on missing closure message is not always respected

[denis-stepanov]

Observed once:

17:49:55: (79) Mailbox 1 door opened; battery 46%
17:49:59: (80) Mailbox 1 closed after 2 seconds; battery 46%
17:51:33: Lost 1 message(s)!
17:51:33: (37) Mailbox 2 door opened; battery 0%
-->(missing timeout in the log: XX:XX:XX: Mailbox 2 door closure event timed out)<--
18:11:46: Alarm "Door opened NOW" acknowledged via Telegram by Denis

The timer should have kicked in 35 s after opening, written the message in the log and moved the state machine to "Door left open". None of this happened, meaning under some condition the timer might not work.

Code study did not reveal a particular issue, so no action for now; to monitor for another occurrence.

[denis-stepanov]

This has been observed at least one more time, but remains a rare event.

Note that since the release 2.2.2 the timer implementation has been changed, which might resolve this issue as well. Monitoring to be continued...