Security camera based on a Raspberry Pi and Telegram, controllable via smartphone and desktop computer. Key differences to scaidermerns bot are:
- Using ffmpeg for livestreaming and capturing stills with the following benefits:
- Support of Hardware Accelerated h264_omx encoding for both livestream and manual capture of stills and videos.
- Not having to stop motion detection for capturing stills and videos
- Higher livestream resolution and/or fps.
- Added command to record video with custom length
- livestream with nginx rtmp module instead of motion
This is a simple Telegram bot that acts as a security camera. It is intended to run on a Raspberry Pi but may be used on any other Linux system, too. It requires a camera (for example a Raspberry Pi Camera Module v2) and the software motion. It supports livestreaming with ffmpeg over the nginx-rtmp-module, and needs a configured nginx server to run with the default config. Hardware accelerated encoding with H264_omx is supported on the raspberry pi. It can be controlled by any Telegram client, thus supporting many different client platforms such as smartphones (Android, iOS and Windows Phone) and desktop computers (Linux, macOS and Windows).
- Raspberry Pi with Raspbian (recommended, but works on any other Linux system with some adjustments)
- Camera (e.g. Raspberry Pi Camera Module v2)
- Telegram account and a Telegram bot
- python (version 2 or 3):
- RPi.GPIO (optional, for controlling a PIR sensor or buzzer)
- python-telegram-bot
- PyInotify
- nginx server compiled with the nginx-rtmp-module
To install the necessary software on Raspbian, Debian or a similar distribution use the following commands:
- as root:
apt-get install python-rpi.gpio
or for python3apt-get install python3-rpi.gpio
(optional, probably already pre-installed on your Pi)apt-get install python-pip
or for python3apt-get install python3-pip
- as regular user:
pip install python-telegram-bot
or for python3pip3 install python-telegram-bot
pip install inotify
or for python3pip3 install inotify
Edit config.json
. In section telegram
enter your Telegram token
and owner_ids
. See these instructions for obtaining your Telegram user ID. Alternatively just add your Telegram token and a random owner ID, run piCamBot and send a message to your bot. piCamBot will log messages from unknown users and write out their user IDs.
Enable motion.
Note: You can't enable pir
and motion
at the same time. However you can disable both and still use piCamBot to perform manual camera captures.
Check that the pid_file
path is correct. It must match the process_id_file
setting in your motion.conf
. Also check that general
:image_dir
matches your motion.conf
's target_dir
. Edit motion.conf
and adjust rotate
, width
, height
to your camera. Also adjust threshold
and noise_level
to your environment (good luck with that...). daemon
mode must be enabled for piCamBot!
Ideally run motion separately to adjust all these settings until it matches your expected results. Afterwards try to use it with piCamBot.
Especially when using a Raspberry Pi it is a good idea to write captured images to a tmpfs. This increases the lifespan if your sdcard. Using the standard configuration piCamBot writes its captures to /tmp/piCamBot/
. To mount /tmp/
as tmpfs add the following line to your /etc/fstab
:
tmpfs /tmp tmpfs nosuid,size=25% 0 0
After a reboot /tmp/
should be mounted as tmpfs.
Execute python piCamBot.py
. The bot will automatically send a greeting message to all owners if Telegram access is working. For troubleshooting take a look at its log files inside the piCamBot directory. It is recommended to start the bot automatically after boot, e.g. via a crontab entry or init script.
The bot will start with motion-based capturing being disabled.
After enabing motion-based capturing it will either react on the PIR sensor and performs captures whenever a motion is reported. Or it reacts on captures performed by the motion software. In either case, captured images are sent via Telegram to all owners. Afterwards these images are deleted from the disk. You can control this behavior via config option general
:delete_images
.
It supports the following commands:
/begin
: Starts loopback with ffmpeg from /dev/video0 to /dev/video1 for motion and /dev/video3 for capturing stills and videos, also starts the livestream to the nginx rtmp server./stop
: Stops loopback with ffmpeg./arm
: Starts motion-based capturing./disarm
: Stops motion-based capturing. Ifmotion
software is enabled it will be stopped as well./status
: Reports whether motion-based capturing is currently enabled./pic
: Takes a manual capture with the camera./vid n
: Takes a manual video with length n, default is 5s./kill
: Only to be used if motionsoftware is enabled. This kills the software (using SIGKILL) in case it is running and
/disarm` fails to stop it./help
: Displays help text with all commands./list
: Shows a list of commands which can be copy pasted to the BotFathers /setcommands command.