@migue5862 Seems like it is a reporting error of some sort. The issue I have seen needed the logs to be phsically reset fromm the terminal so yours seems different to that. Good idea on keeping an eye on for now. If you feel this is down to the device we can move it. For now let's leave it where it is.