I wanted to try setting up my Raspberry Pi-camera, and I wanted to integrate it with Domoticz.
I did some manual labor for setting up a dedicated IP-cam from scratch, but after searching around I found MotionPie ( https://github.com/ccrisan/motionPie ).
No point re-inventing the wheel, so I loaded it up according to the installation manual, and got it up network-wise.
The following is needed to be configured in order for Domoticz to work:
IP Address: <ipaddress>
If you create a dummy switch in Domoticz, you can have motionpie activate that switch using Motion Notifications:
Enable running of commands, and insert the following command:
Where <IP-to-domoticz> is self-explanatory, and <IDX> is the ID-number for the switch.
Don’t forget to edit the switch so it’s a motion sensor, and set a custom off-delay.
MotionPie won’t trigger it “off” for you.
I wanted to setup a tiny timelapse-rig using raspberry pi and the official addon-camera.
A quick search returned MotionPie ( https://github.com/ccrisan/motionPie ), and after setting it up using the supplied wiki-pages and some initial configuration I had a feed to watch.
I plugged in a USB-drive (make sure it has a partition and a filesystem MotinoPie can read (ext4 f.ex.)) and under the admin-menu, and “File Storage” you should be able to select the external storage.
In order to create a timelapse you have to save snapshots at regular intervals, this is done under “Still Images”, select “Interval Snapshots” under “Capture Mode” and insert a interval.
Remember 30 pictures per second for a movie equalls 1800 pictures per minute of video.
Dont exagerate your interval, or you will have a very long (and boring?) timelapse.
15s interval over 3 days is 10 minutes of video and 18 000 pictures.
Now the tricky part was that I wanted to create the timelapse outside of MotionPie, and therefore I needed the pictures in sequence, and not using the default file naming.
There was no real legend with variables that I wanted (I wanted to use unix time) – so some quick googling led me to this handy site ( http://www.cyberciti.biz/faq/linux-unix-formatting-dates-for-display/ ) – and that site had this handy table:
||a literal %
||locale’s abbreviated weekday name (e.g., Sun)
||locale’s full weekday name (e.g., Sunday)
||locale’s abbreviated month name (e.g., Jan)
||locale’s full month name (e.g., January)
||locale’s date and time (e.g., Thu Mar 3 23:05:25 2005)
||century; like %Y, except omit last two digits (e.g., 21)
||day of month (e.g, 01)
||date; same as %m/%d/%y
||day of month, space padded; same as %_d
||full date; same as %Y-%m-%d
||last two digits of year of ISO week number (see %G)
||year of ISO week number (see %V); normally useful only with %V
||same as %b
||day of year (001..366)
||hour ( 0..23)
||hour ( 1..12)
||locale’s equivalent of either AM or PM; blank if not known
||like %p, but lower case
||locale’s 12-hour clock time (e.g., 11:11:04 PM)
||24-hour hour and minute; same as %H:%M
||seconds since 1970-01-01 00:00:00 UTC
||time; same as %H:%M:%S
||day of week (1..7); 1 is Monday
||week number of year, with Sunday as first day of week (00..53)
||ISO week number, with Monday as first day of week (01..53)
||day of week (0..6); 0 is Sunday
||week number of year, with Monday as first day of week (00..53)
||locale’s date representation (e.g., 12/31/99)
||locale’s time representation (e.g., 23:13:48)
||last two digits of year (00..99)
||+hhmm numeric timezone (e.g., -0400)
||+hh:mm numeric timezone (e.g., -04:00)
||+hh:mm:ss numeric time zone (e.g., -04:00:00)
||numeric time zone with : to necessary precision (e.g., -04, +05:30)
||alphabetic time zone abbreviation (e.g., EDT)
So then it was just a matter of replacing anything under “Image File Name” with “pics/%s” – and everything will be jolly good.