I have had this issue several times, I notice it when my system goes down for its weekly backups and when it comes back up.
The nodect monitor has the RED status indicator and the analysis fps are at 0.00. The monitor creates events that are viewable but it does not write any of the Frames data to the DB. This causes an error when ZMES tries to query the ZM API for the event data and receives an empty 'Frames" structure.
The only way I have found to fix this issue is to manually go to the console, set the nodect monitor to modect and wait until it starts capturing. Once the monitor is capturing again and I can see that it has analysis FPS, I set the monitor to nodect and all is well.
There are no errors in log and as far as ZM is concerned everything is fine and dandy. So its a silent error that only affects the object detection or someone that wants to see the frames data in the console.
Anyone else notice this issue? I have been following the updates and am now on 1.36.10. I have been experiencing this issue since the 'linked monitors' fix was implemented, before it would just stop working as a linked and now its this.
The no frames view ->
1.36.x (since .5) NODECT not capturing
Re: 1.36.x (since .5) NODECT not capturing
Going to need level 3 debug logs.