Bug #932

Post-record value is currently hardcoded

Added by Curtis Hall 9 months ago. Updated 4 months ago.

Status:Resolved Start date:08/26/2011
Priority:Normal Due date:
Assignee:John Brooks % Done:

100%
Category:Server Spent time: -
Target version:2.0.0-beta9.2 Estimated time:2.00 hours
Release Blocker:No Affected Release:
Operating System:

Description

Currently the post-record value for motion detection is hardcoded as 3 clock seconds. This needs to be removed and the server needs to read the value from each device, as each device can have a different post record value.

History

#1
Updated by Curtis Hall 6 months ago

  • Target version changed from 2.0.0-beta9 to 2.0.0-beta9.2

#2
Updated by John Brooks 5 months ago

  • Description updated (diff)
  • Assignee changed from Veaceslav Falico to John Brooks
  • Estimated time changed from 4.00 to 2.00

It appears that we already have columns in Devices for this; buffer_prerecording and buffer_postrecording, defined in seconds with defaults of 0 and 3 respectively.

#3
Updated by John Brooks 4 months ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF