It doesn't look like the new API yet has the capability to put a monitor in alarm state. I currently use zmtrigger.pl, and my garage door controller tells zm to put both the driveway and garage cameras in an alarm state 5 seconds after the garage door is opened and stay in alarm for 20sec. zmtrigger works, but it crashes after it's used so I run a cron job to monitor for the process and restart it after it's used and subsequently crashes. I'm not worried about fixing that, the cron job isn't graceful but gets the job done. More interested in if the new API will eventually take over this function??
The other bit is checking the current run state of zm. I have another cron job that kicks off a script which checks my wireless system to determine if either of the adults in the house are home (it checks to see if our phones are connected to WLAN). If either of us are connected it changes the state of zm. If we are home it goes into a state which has the inside camera in monitor, if we are both out then the script will put zm in a state which has the inside camera set to modect. Otherwise if we are home I disable motion detection on the inside camera. I'll also be adding a function to my garage door controller that will allow me to put the garage camera in monitor mode from my garage door controllers interface (so I'm not capturing myself tinkering in the garage).
I know there is an API to change the function of the individual monitor, which would do the trick, but it currently has the issue with a cake error viewtopic.php?f=34&t=24306&start=15 So I'm still using run states via script right now.
So here is the list of things I'm doing - curious if there is/will be API support:
- Trigger alarms from external system
- determine current Run State of zm (currently querying db directly)
- Change Run State of zm
Great job on the new web-site btw, excited to see the project evolve.
