Couple of bugs with zmtrigger.pl

[asker]

Hi, I have set up zmtrigger to use the HW motion detection algorithm of my foscam cameras instead of ZM doing SW detection. It's working very well, but I have encountered the following bugs:

a) zmtrigger.pl randomly exits with a memory map error - I read other threads and for now, I've fixed it by simply wrapping zmtrigger.pl in a shell script that keeps restarting it

b) the bigger issue is this: Zmtrigger needs monitors to be in nodect. The problem is this: if I switch my camera to motion and then nodect while Zmtrigger is running, it does not seem to recognize this change - it fails trying to find that monitor. The only way I found around it is for me to break out of Zmtrigger and restart it. Is there any other way? I don't want zmtrigger to change state because I have a cron job that switches monitors to motion and nodect and during motion time, I don't want zmtrigger to use the motion recording. So that fact that zmtrigger is not finding the monitors when it switches to monitor is perfect. But I do need it to know when the camera switches back to nodect and that is not working.

thanks

[asker]

Problem solved. I noticed the script has a cache timeout, so I did a reload one time when the monitor is not found to make sure. Works great.