-
Notifications
You must be signed in to change notification settings - Fork 548
FAQ
A: The place to ask these questions will be either on the IRC channel #motion or on the motion-user mailing list which can be subscribed here. It is important to use the mailing list for these questions rather than the github issues in order to gain the experience of a wider audience who may be able to address your question.
A: The first thing to do is to review the Motion guide. Next, would be to discuss the situation/issue on the IRC channel #motion or on the motion-user mailing list which can be subscribed here. Once it is confirmed that Motion is not working as intended, a bug or enhancement request may be appropriate for reporting in the github issue log.
Q: I am using application XXXX which is a front-end application for Motion and it is not working. How do I fix my issue?
A: Please keep in mind that the Motion developers do not use any front-end application. You will need to set up and use Motion as a stand-alone application and validate that the issue remains. Questions and answers from the Motion team will be framed with respect to how to configure Motion rather than the front end application.
A: The developers will need to know some key information in order to replicate, validate and ultimately resolve the issue. First, you will need to validate that the issue occurs on the most recent release as posted here or was built from the current github master branch. Next, we will need a full log from startup to shutdown at the NTC log level. Finally, we'll need the motion.conf and any applicable camera.conf files. It is recommended that the logs and config files be edited to mask any camera IP address or usernames/passwords to preserve your privacy. The preferred location for posting these files is on gist with only the link posted in the issue.
A: Not for the foreseeable future. In addition to the technical complexities and legal implications(covert recording of audio is not permitted in many countries), the maintainer believes in making sure the application keeps the focus on its core functionality of video.
A: First, the application may also be prepackaged into your distribution so check the version there. Next, if the distribution packaged version is too old and you need a newer version, you can get the latest release packages here. Finally, if you need all the latest fixes, you can obtain the source code from the repo and follow the instructions here.
The work on the Motion application is expected to be seasonal. From January of each year to September, one of the maintainers is only able spend minimal time working on the application. During this time, issues/pulls may not be able to be immediately addressed.
The Motion application is intended to be a small core component with many configuration options. Other applications can choose to wrap around the Motion application to provide a GUI interface. This allows users the choice of whether they need the overhead associated with the GUI or only need the core functionality that the Motion application provides.
The Motion application is used across a extremely wide set of platforms. In order to support all of these platforms and hardware needs the Motion application is written only in C. This is believed to provide the most flexibility without requiring additional libraries or specialized developers.
log in remotely (via SSH/putty) or use a monitor+keyboard
stop motionEye: /etc/init.d/S85motioneye stop
run motion manually: cd /data/etc ; motion -c motion.conf -d 5 -n
The easiest way to see a tiled page of all cameras that are running Motion is to create a very simple html page. Open up your favorite text editor and paste the following in, revise ipaddress:portnumber and then save as motionview.html Finally, open the file in a web browser.
<html>
<body bgcolor=000000>
<img src=http://ipaddress1:portnumber/ border="0" width=25%></a>
<img src=http://ipaddress2:portnumber/ border="0" width=25%></a>
<img src=http://ipaddress3:portnumber/ border="0" width=49%></a>
</body>
</html>
The archive of older FAQ is here