As this seems a common question I added a trouble shooting section to end of pdf with motion detection as first topic.ianj wrote:Has anybody had recent trouble with motion not triggering captures? Working with a Pi B, brand new install of Raspbian and the latest btidey version 4.4.2R.
-If I haven't clicked the motion capture button, going to edit motion settings page results in "Motion not running. Put in detection state"
-Going to edit motion settings after clicking motion detection start will bring me to a page after lots of waiting, with nothing on it. Just blank space. Takes a good 1-2 minutes.
-The log shows "motion detection started and stopped" as per the button clicking
-Set the schedule to AllDay
Motion doesn't seem to fire off a record. Sending video record commands (ca 0, 1) via console works, hitting the record video button works.
However, I am not sure it is going to deal with your problem which seems a bit strange.
First going to the motion page and getting that message is quite normal. The settings are retrieved and saved via a web control interface in motion itself so it only works if motion is running. I have only ever seen a virtually immediate response to the request to get settings so something is wrong there.
manually motion config (sudo nano /etc/motion/motion.conf)
Check that control_port 6642 and control_html_output off
Change control_localhost to off and save the file
Stop and restart motion (turn off motion detection and back on again
Now browse to http://yourcamIP:6642/0/config/list This accesses the motion control port and asks for a full list of settings. You should get back a text page with all the motion parameters.
If you do not get this then there is something seriously wrong with the motion install.