One more question: did this happen with the original firmware, or it happened after 2.1.8(4)? We have just released 2.1.8(4) today and haven’t even announced it yet, curious how you knew about 2.1.8(4)? If it didn’t happen with the previous firmware, I suppose this is a software problem. Otherwise, if this happened with previous firmware as well, then it’s a hardware problem (likely real-time clock).