Default
Default: Not defined
Default: off
Default: 0 (disabled)
Default: 0 (disabled)
Default: Not defined
Default: on
- Motion reads the configuration file motion.conf from the beginning of the file going down line by line.
- If the option "thread" is defined in motion.conf, the thread configuration file(s) is/(are) read.
- Motion continues reading the rest of the motion.conf file. Any options from here will overrule the same option previously defines in a thread config file.
- Motion reads the command line option again overruling any previously defined options.
Command Line Options
In Motion 3.2.1 and forward most command line options have been removed and replaced them by an option to specify location to motion.conf and a few options related to setting up motion. There are now only few command line options left and they are basically all new.
SYNOPSIS
motion [ -hns ] [ -c config file path ] [ -d level ] [ -p process_id_file ]
Config File Options
These are the options that can be used in the config file. All number values are integer numbers (no decimals allowed). Boolean options can be on or off. Some configuration options are only used if Motion is built on a system that has the matching software libraries installed (MySQL, PostgreSQL and FFMPEG). MySQL- mysql_db, mysql_host, mysql_user, mysql_password
- pgsql_db, pgsql_host, pgsql_user, pgsql_password, pgsql_port
- ffmpeg_cap_new, ffmpeg_cap_motion, ffmpeg_filename, ffmpeg_timelapse, ffmpeg_timelapse_mode, ffmpeg_bps, ffmpeg_variable_bitrate, ffmpeg_video_codec
Options in Alphabetical Order.
The table below lists all the Motion options in alphabetical order. Click on the option name to see a longer description of each.| Option | Range/Values Default |
Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| area_detect | Values: 1 - 999999999 Default: Not defined |
Detect motion center in predefined areas. A script (on_area_detected) is started immediately when motion center is detected in one of the given areas, but only once during an event even if there is motion in a different configured area. | ||||||||||||
| auto_brightness | Values: on, off Default: off |
Let motion regulate the brightness of a video device. Only recommended for cameras without auto brightness | ||||||||||||
| brightness | Values: 0 - 255 Default: 0 (disabled) |
The brightness level for the video device. | ||||||||||||
| contrast | Values: 0 - 255 Default: 0 (disabled) |
The contrast level for the video device. | ||||||||||||
| control_authentication | Values: Max 4096 characters Default: Not defined |
To protect HTTP Control by username and password, use this option for HTTP 1.1 Basic authentication. The string is specified as username:password. Do not specify this option for no authentication. This option must be placed in motion.conf and not in a thread config file. | ||||||||||||
| control_html_output | Values: on, off Default: on |
Enable HTML in the a you run 'make install' this file gets copied to the /usr/local/etc directory.
The configuration file needs to be renamed from motion-dist.conf to motion.conf. The original file is called motion-dist.conf so that your perfectly working motion.conf file does not accidentally get overwritten when you re-install or upgrade to a newer version of Motion.
If you have more than one camera you should not try and invoke Motion more times. Motion is made to work with more than one camera in a very elegant way and the way to do it is to create a number of thread config files. Motion will then create an extra tread of itself for each camera. If you only have one camera you only need the motion.conf file. The minute you have two or more cameras you must have one thread config file per camera besides the motion.conf file.
So if you have for example two cameras you need motion.conf and two thread config files. Total of 3 config files.
An option that is common to all cameras can be placed in motion.conf. (You can also put all parameters in the thread files but that makes a lot of editing when you change a common thing).
An option that is unique to a camera must be defined in each thread file.
It is often seen that people copy the entire motion.conf into the thread config files and change a few options. This works but it not recommended because it is more difficult to maintain and overview. Keep all the common options in motion.conf and the few unique only in the thread config files
The first camera is defined in the first thread file called from motion.conf. The 2nd camera is defined in the 2nd thread file called from motion.conf etc.
Any option defined in motion.conf will be used for all cameras except for the cameras in which the same option is defined in a thread config file.
Motion reads its configuration parameters in the following sequence. If the same parameter exists more than one place the last one read wins.
Command Line Options In Motion 3.2.1 and forward most command line options have been removed and replaced them by an option to specify location to motion.conf and a few options related to setting up motion. There are now only few command line options left and they are basically all new.
SYNOPSIS
motion [ -hns ] [ -c config file path ] [ -d level ] [ -p process_id_file ] Config File OptionsThese are the options that can be used in the config file. All number values are integer numbers (no decimals allowed). Boolean options can be on or off. Some configuration options are only used if Motion is built on a system that has the matching software libraries installed (MySQL, PostgreSQL and FFMPEG). MySQL
Options in Alphabetical Order.The table below lists all the Motion options in alphabetical order. Click on the option name to see a longer description of each.
|