If I have a monitor with its function set to Modect and enabled, and set its Function to "Monitor" or Enabled to 0 using the API, it still produces alarms and records events even though I can see it set to Monitor or disabled in the web console. If I re-enable and then disable it, or set it to Modect and then back to Monitor, using the web interface, it disarms as expected.
It's the same whether I curl the API directly or use ZMninja.
Enabling a disabled Modect monitor, or changing a monitor from Monitor to Modect using the API works as expected. I can change a monitor from Monitor to Modect and back to Monitor again using the API, and afterwards it will behave as if it's in Modect.
It seems like the web console will terminate zma when switching from Modect to Monitor, or Enabled to Disabled, but the API won't.
Can anybody reproduce this? Running ZM 1.30.4.
Monitors still producing alarms when set to Monitor or disabled through API
- knight-of-ni
- Posts: 2406
- Joined: Thu Oct 18, 2007 1:55 pm
- Location: Shiloh, IL
Re: Monitors still producing alarms when set to Monitor or disabled through API
When you change modes in the web console, the monitor is stopped and then started for when you hit save.
If you change the mode from the API, If I recall you have to send a restart command. It does not restart automatically.
Looks like this thread applies:
viewtopic.php?t=23459
If you change the mode from the API, If I recall you have to send a restart command. It does not restart automatically.
Looks like this thread applies:
viewtopic.php?t=23459
Visit my blog for ZoneMinder related projects using the Raspberry Pi, Orange Pi, Odroid, and the ESP8266
All of these can be found at https://zoneminder.blogspot.com/
All of these can be found at https://zoneminder.blogspot.com/