Wrong time on "back in range" - ok on Jan 19th, bad on Jan 21st and since

[Milan Sreckovic]

At some point last week, the time stamp on the "back in range" event started being wrong for me (see the attached image.)  The "out of range" is at the correct time, and once the tag is back in range, the duration for the out of range interval is correct.  But, the time on the "back in range" event actually predates the "out of range" one.

The "back in range" time stamp used to be equal to the "out of range" time plus the duration.  Now, not so much.

This is a problem with grace period at the default 4 minutes, as well as set to "immediately notify".

Any clues?