Skip to content

Monitoring Commands

Bortek edited this page Aug 15, 2017 · 3 revisions

What Are Monitoring Commands?

Starting with version 0.32, motionEye can be configured to overlay monitoring information on top of a camera frame. The information is gathered by running a command and capturing its output. These commands can be configured on a per-camera basis and are usually shell scripts provided by the user.

Monitoring commands can be used to watch system parameters such as the system load, the CPU temperature or the network transfer rate.

Enabling A Monitoring Command

motionEye will look inside its configuration folder for executable files named monitor_[cameraid], where cameraid is the id of the camera on top of which the monitoring info will be displayed.

For example, on a setup using the default configuration, the presence of the executable file /data/etc/monitor_1 will determine motionEye to run the script every 1 second (by default), to read its standard output and to display it on top of the first camera frame.

Execution (Refresh) Rate

By default, all monitoring scripts are called every 1 second. If a script wishes to explicitly reschedule its next execution, it should simply write the delay, in seconds, to its standard error.

A Few Remarks

  • When adding or removing these scripts, you need to reload the application in your browser for the changes to take effect.
  • Make sure the file is executable and has no extension.
  • Monitoring command files can be symlinks, as long as they point to an executable file.
  • No arguments are passed when executing the file; if you need to pass arguments to your commands, create a shell script as a wrapper around your command.
  • The command must return immediately (i.e. should not block).
  • NOTE: To see the overlayed text you must click on the image which will show the frame around the and the text will be shoes on the bottom left corner. Look at the image in this Issue.


The following monitoring script can be used to display the temperature of a system every 10 seconds:


cpuTemp0=$(cat /sys/class/thermal/thermal_zone0/temp)
cpuTempM=$(($cpuTemp2 % $cpuTemp1))
echo CPU Temp"="$cpuTemp1"."$cpuTempM""
echo 10 1>&2
You can’t perform that action at this time.