You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it looks like there is a problem with the Working Schedule feature. It does not matter what i configure there, the Cam is always in Motion Detection Mode (also records files).
While testing, the working schedule was set to only MoDect on Monday during 08:00 - 23:59. Serverdate and time is correct.
Python: 3.10.5
Motioneye: 22.4.1
Motion: 4.3.2
2022-08-26 13:11:31: [motioneye] DEBUG: motion detection is disabled for camera with id 1
2022-08-26 13:11:34: [motioneye] DEBUG: creating mjpg client for camera 1
2022-08-26 13:11:34: [motioneye] DEBUG: mjpg client for camera 1 connected on port 9081
2022-08-26 13:11:34: [motioneye] DEBUG: no authentication _on_connect
2022-08-26 13:11:35: [motioneye] DEBUG: Already finished
2022-08-26 13:11:35: [motioneye] DEBUG: Already finished
2022-08-26 13:11:41: [motioneye] DEBUG: Already finished
2022-08-26 13:11:41: [motioneye] DEBUG: motion detection is disabled for camera with id 1
2022-08-26 13:11:42: [motioneye] DEBUG: executing preset2 action for camera with id 1: "/etc/motioneye/preset2_1"
2022-08-26 13:11:42: [motioneye] DEBUG: 200 POST /action/1/preset2/?_=1661512302017&_username=<schnipp>&_signature=<schnipp> (10.0.2.2) 3.86ms
2022-08-26 13:11:43: [motioneye] DEBUG: preset2_1: command has finished
2022-08-26 13:11:43: [motioneye] DEBUG: Already finished
2022-08-26 13:11:44: [motioneye] DEBUG: received relayed event start for motion camera id 1 (camera id 1)
2022-08-26 13:11:44: [motioneye] DEBUG: marking motion detected for camera with id 1
2022-08-26 13:11:44: [motioneye] DEBUG: 200 POST /_relay_event/?_username=<schnipp>&event=start&motion_camera_id=1&_signature=<schnipp> (127.0.0.1) 1.94ms
2022-08-26 13:11:50: [motioneye] DEBUG: _garbage_collector checking camera. id: 1
2022-08-26 13:11:51: [motioneye] DEBUG: motion detection is disabled for camera with id 1
2022-08-26 13:12:00: [motioneye] DEBUG: _garbage_collector checking camera. id: 1
2022-08-26 13:12:01: [motioneye] DEBUG: motion detection is disabled for camera with id 1
As you can see, the Logs are confirming that MoDect was disabled for Cam1. But at timestamp 13:11:44 Motioneye detected a motion on Cam1.
Before switching to motioneye.eo i had motioneye 0.42.1 running with python2. Same Config - no problem. (Config was manually redone via WebUI, not migrated).
The text was updated successfully, but these errors were encountered:
Hi,
it looks like there is a problem with the Working Schedule feature. It does not matter what i configure there, the Cam is always in Motion Detection Mode (also records files).
While testing, the working schedule was set to only MoDect on Monday during 08:00 - 23:59. Serverdate and time is correct.
As you can see, the Logs are confirming that MoDect was disabled for Cam1. But at timestamp 13:11:44 Motioneye detected a motion on Cam1.
Before switching to motioneye.eo i had motioneye 0.42.1 running with python2. Same Config - no problem. (Config was manually redone via WebUI, not migrated).
The text was updated successfully, but these errors were encountered: