Internal Commands

Internal commands you put in the at-commands.conf file should be preceded by an '@' character but if echoed to the FIFO port, do not use the '@'. For example, here's some commands to put into the at-commands.conf if you wanted to timelapse something that goes on only in the mornings and evenings on weekdays:

Mon 7:30 "@tl_start 30"
Mon-Fri 7:30 "@tl_hold off"
Mon-Fri 9:00 "@tl_hold on"
Mon-Fri 17:00 "@tl_hold off"
Mon-Fri 18:00 "@tl_hold on"
Fri 18:00 "@tl_end"

So with that you will have a timelapse running off and on all week and will have a video produced in the videos directory Friday night (or Saturday morning if you are on a B+).

Many commands are for interaction with the web page, but some commands likely to be useful in at-command.conf are:

record [on|off]
record_pause
still
tl_start period
tl_hold
tl_end
motion_enable [on|off|toggle]
motion load_regions NAME
motion limits magnitude_limit count_limit

Scripts can also write commands to the FIFO and some commands are specific to a script. For example the timelapse-end script sends inform status that it is converting a mp4 to the FIFO. Later I intend to add a generalized inform interface so scripts can send information to display on the OSD.