Jump to: navigation, search

Purging...please explain the math

Hi, With regard to Purging, can someone explain the math, in the documentation?


The scheduler has facilities for removing old files automatically. There are two mechanisms which are both checked and used at each Management_Interval. First the 3 PURGE_HOURS (one per file type) are checked and any file older than this is removed. So if PurgeVideo_Hours is set to 98 then any video captured more than a week ago will be removed. Setting the values to 0 disables this .

  • How is the PurgeVideo Hours implemented?
  • is it 98 total video hours?
  • or example above, is it 7 days * 24 = 168 hours...but 168 hours is significantly more than 98 hours. I don't understand the above statement if a video captured more than a week ago, with the variable set to 98....Wouldn't it be set to 168?

Thanks for the help!

IoT Maker DSM (talk)20:34, 19 November 2017

Where is the main html page

Hi, I want to edit the main html file, but i dont find it, please help me! Thanks

Francescom (talk)05:57, 20 July 2017

Did you see this note in the installation section:

IMPORTANT NOTE: If you need to change any files then you need to do these in the run time version (e.g. in the /var/www/html folder or /etc/raspimjpeg). Changing files in the RPi_Cam_Web_Interface folder has no immediate effect. These are just copies used during the install.

Wmat (talk)06:00, 20 July 2017

Ok but I do not find in the / var / www / html folder the file that is displayed when you access the interface from the browser

Francescom (talk)06:19, 21 July 2017

Can't you just use grep to find some text from the page?

Do something like:

$grep -ri "some string from the webpage that's unique" .

That will turn up any files that contain the string "some string from the webpage that's unique".

Wmat (talk)08:55, 21 July 2017

Thank you, I will try to do as you say

Francescom (talk)02:24, 22 July 2017

Example of automated video email?

All, I have the RPi Cam Web up and working and now moving onto tidying up the install. I installed, configured and verified that ssmtp and mpack are able to send emails/attachments from pi@raspberrypi prompt.

I need a second set of eyes or someone to verify this is the proper approach:

1. nano /var/www/macros/

2. add:

  1. !/bin/bash

list=( $1*.th.jpg )


mpack -s subject /var/www/media/thumb

[save and exit nano]

3. sudo chmod a+x /var/www/macros/

4. sudo chown www-data:www-data /var/www/macros/

Does this look correct? is there a more elegant way or method that I overlooked?

Guidance and help are appreciated! Brian

IoT Maker DSM (talk)08:34, 23 March 2017

Any way to change size of preview on webpage? Any way to make the min/simple the default page?

First, I want to thank you for creating this. For noobs like me tinkering around with a raspberry pi, this is exactly what I was looking for for a project I had in mind.

Is there a way to make the view on a webpage bigger than the default size, other than clicking on it while viewing? I looked through and couldn't find any settings to change, and inspecting the source of the webpage while viewing it is where I saw the "onclick" to toggle full screen. So is there a way to have the page load with a bigger version of the preview by default.

Also, is there any way to make the min.php the default page that loads? I'm looking to make it so viewers can't control the camera or make changes to settings. I understand that I can direct them to the min.php, but was hoping there was a way to make that the default landing. I tried changing the min.php to index.php (and changing index to something else), but the full page kept loading with all the controls.

Thank you for any help in advance.


Ericsura (talk)11:49, 5 March 2017

No idea, sorry. I think you'd have better luck on StackOverflow or the RPi forums.

Wmat (talk)16:22, 5 March 2017

Changing contents of Preview stream

So, I am having fun with my RPi and cameras, getting the preview from many into a single web page, into a Python script and into OBS. What I cannot seem to do is change the content of the preview to be the same as the captured image. Is there a way to do this. The preview seems to contain only the centre of the image captured by the camera module. Any ideas please.

All the feeds come from http://<RaspberryPi IP>/cam_pic_new.php?

BlueBerry (talk)15:01, 19 November 2016

I'm sorry, I don't know. I haven't played with that stuff at all. You should try the RPi forums.

Wmat (talk)15:37, 19 November 2016

So here it is all along, right in front of me!

Use the Camera Settings option, Resolutions. Setting to any of the Load Presets other than the first or last (HD ...) gives a mode that includes a full size preview - perfect for my needs.

As someone once said - WONDERFUL!

BlueBerry (talk)05:52, 21 November 2016

Awesome, glad you got your answer.

Wmat (talk)05:58, 21 November 2016

Amount changed pixels in the camera annotation ?


Is there a way to see the amount of changed motion pixels and show the in the camera name(Annotation)?

I use external motion and the manual only describes the internal motion, so %c and %f do not work..... The version that I use is RPi Cam Control v6.0.37

Perhaps it would be also nice for a user setting for change the position of this text. (left right up down in the camera picture)


Alexhouben (talk)01:39, 27 April 2016

Problem with RPi B, Debian Jessie (new) und Apache2

I cannot get the Cam-Web-interface to work with the latest Debian Jessie with Apache 2. I would appear that Apache 2 looks into /var/www/hmtl/index.hmtl and execute that hmtl file. Replacing the index.hmtl with yout index.php creates just a white screen. Here is a note from Apache 2

Debian's Apache2 default configuration is different from the upstream default configuration, and split into several files optimized for interaction with Debian tools. The configuration system is fully documented in /usr/share/doc/apache2/README.Debian.gz. Refer to this for the full documentation. Documentation for the web server itself can be found by accessing the manual if the apache2-doc package was installed on this server.

The configuration layout for an Apache2 web server installation on Debian systems is as follows: /etc/apache2/ |-- apache2.conf | `-- ports.conf |-- mods-enabled | |-- *.load | `-- *.conf |-- conf-enabled | `-- *.conf |-- sites-enabled | `-- *.conf

• apache2.conf is the main configuration file. It puts the pieces together by including all remaining configuration files when starting up the web server. • ports.conf is always included from the main configuration file. It is used to determine the listening ports for incoming connections, and this file can be customized anytime. • Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/ directories contain particular configuration snippets which manage modules, global configuration fragments, or virtual host configurations, respectively. • They are activated by symlinking available configuration files from their respective *-available/ counterparts. These should be managed by using our helpers a2enmod, a2dismod, a2ensite, a2dissite, and a2enconf, a2disconf . See their respective man pages for detailed information. • The binary is called apache2. Due to the use of environment variables, in the default configuration, apache2 needs to be started/stopped with /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not work with the default configuration.

Document Roots

By default, Debian does not allow access through the web browser to any file apart of those located in /var/www, public_html directories (when enabled) and /usr/share (for web applications). If your site is using a web document root located elsewhere (such as in /srv) you may need to whitelist your document root directory in /etc/apache2/apache2.conf.

The default Debian document root is /var/www/html. You can make your own virtual hosts under /var/www. This is different to previous releases which provides better security out of the box.

Reporting Problems

Please use the reportbug tool to report bugs in the Apache2 package with Debian. However, check existing bug reports before reporting a new bug.

Please report bugs specific to modules (such as PHP and others) to respective packages, not to the web server itself.

Bonzadog (talk)08:00, 1 October 2015

script examples please

I would be great if there were python, javascript, or PHP examples of how to take an image at a given interval outside of the time-lapse feature. why? when you enable time-lapse the user interface is disabled. I want the ability for anyone to take a photo but I also want to store a time-lapse of an image every 30 minutes to one hour.

Sensorware (talk)14:05, 7 May 2015

Pi-Pan tilt implementation

I am not able to move the pi-pan severs from the Cam-web-interface. The servos work fine from the command line and the buttons appear on the web interface but they do not activate the servos from the interface. I am using a safari web browser on a mac and have tried a chrome browser with the same result. It seems related to the script for the pi-pan control. Has anyone had a similar problem and/or solution.

Thanks, Gary

Idahospud (talk)10:13, 18 April 2014

Links to the information web pages...

How about adding links to the information pages in the index.html so it's easy to get help...

for example add:

<a href="">Help on configuring Web Service</a>

<a href="">Forum Thread on RPi Cam Web Interface</a>

after </table> and before </center>. /Jaix

JaixBly (talk)00:39, 21 March 2014