New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to retrieve result for object_detector - Frame is 2.8047475814819336 seconds old. Discarding #686
Comments
In your config you have both darknet and edgetpu object detector for camera_2, which can lead to unexpected results. Only one will be setup successfully (the other should show an error in the log on restart) I suggest removing one of them and see if the issue persists |
Thank you for the suggestion, I removed darknet entirely and restarted viseron.
|
Thanks, seems the EdgeTPU stops functioning for some reason, could be a power issue perhaps. There is another open issue on a similar case, cant find it right now tho. |
Thank you for feedback. |
Hmm, not that i can think of. |
Hello,
after some time running viseron fine and everything seems to work nicely I noticed that I have to restart it every few days because it stops detecting (and recording on object detection).
Mostly the issue happens after about 2-3 days after (re)start of viseron. I tried to log everything to find the cause but am unsuccessful to find an obvious problem.
I thought, maybe it is because the connection to the camera was interrupted, but no, even if I interrupt the connection to the camera on purpose (after a restart of viseron), the connection is re-established again, so this seems not to be the issue.
What could be the reason, that it suddently stops detecting objects and seemingly runs in that loop not detecting objects anymore?
current configuration (commented lines removed):
log with last successfull recording - after that, the log shows only those failed and old frame messages for days, no matter if there is movement or not:
The text was updated successfully, but these errors were encountered: