Bot releases are visible (Hide)
What's new:
motion.service
is now disabled by motioneye_init
execution: #2980 @MichaIngPublished by MichaIng 10 months ago
What's new:
Published by ccrisan over 4 years ago
What's new:
nvenc
(credits go to @HawtDogFlvrWtr).What's new:
Published by ccrisan about 5 years ago
What's new:
vcgencmd
(thanks @kleini)/usr/bin/env bash
shebang is now used (thanks @phaethon)threshold_maximum
and threshold_tune
Motion optionsPublished by ccrisan about 5 years ago
Published by ccrisan over 5 years ago
What's new:
mjpeg://
URLs (thanks @Queuecumber)note 1: Starting with motionEye 0.40, Motion 3.x versions are no longer supported. Please upgrade to Motion 4.x.
note 2: Starting with motionEye 0.40, the new Motion 4.x directives are used in configuration files. You can either remove and re-add all your cameras or you can use the migrateconf.sh script to convert your configuration files:
for file in /etc/motioneye/{motion,thread-*}.conf; do /usr/local/lib/python2.7/site-packages/motioneye/scripts/migrateconf.sh $file; done
What's new:
note 1: Starting with motionEye 0.40, Motion 3.x versions are no longer supported. Please upgrade to Motion 4.x.
note 2: Starting with motionEye 0.40, the new Motion 4.x directives are used in configuration files. You can either remove and re-add all your cameras or you can use the migrateconf.sh script to convert your configuration files:
for file in /etc/motioneye/{motion,thread-*}.conf; do /usr/local/lib/python2.7/site-packages/motioneye/scripts/migrateconf.sh $file; done
What's new:
note 1: Starting with motionEye 0.40, Motion 3.x versions are no longer supported. Please upgrade to Motion 4.x.
note 2: Starting with motionEye 0.40, the new Motion 4.x directives are used in configuration files. You can either remove and re-add all your cameras or you can use the migrateconf.sh script to convert your configuration files:
for file in /etc/motioneye/{motion,thread-*}.conf; do /usr/local/lib/python2.7/site-packages/motioneye/scripts/migrateconf.sh $file; done
What's new:
note 1: Starting with motionEye 0.40, Motion 3.x versions are no longer supported. Please upgrade to Motion 4.x.
note 2: Starting with motionEye 0.40, the new Motion 4.x directives are used in configuration files. You can either remove and re-add all your cameras or you can use the migrateconf.sh script to convert your configuration files:
for file in /etc/motioneye/{motion,thread-*}.conf; do /usr/local/lib/python2.7/site-packages/motioneye/scripts/migrateconf.sh $file; done
What's new:
note 1: Starting with motionEye 0.40, Motion 3.x versions are no longer supported. Please upgrade to Motion 4.x.
note 2: Starting with motionEye 0.40, the new Motion 4.x directives are used in configuration files. You can either remove and re-add all your cameras or you can use the migrateconf.sh script to convert your configuration files:
for file in /etc/motioneye/{motion,thread-*}.conf; do /usr/local/lib/python2.7/site-packages/motioneye/scripts/migrateconf.sh $file; done
What's new:
mjpeg://
URLs (thanks @Queuecumber)note 1: Starting with motionEye 0.40, Motion 3.x versions are no longer supported. Please upgrade to Motion 4.x.
note 2: Starting with motionEye 0.40, the new Motion 4.x directives are used in configuration files. You can either remove and re-add all your cameras or you can use the migrateconf.sh script to convert your configuration files:
for file in /etc/motioneye/{motion,thread-*}.conf; do /usr/local/lib/python2.7/site-packages/motioneye/scripts/migrateconf.sh $file; done
Published by ccrisan over 6 years ago
What's new:
cifs-utils
packagePublished by ccrisan over 6 years ago
What's new:
Published by ccrisan over 6 years ago
What's new:
server_name
config setting (thanks to @hobbyquaker)Published by ccrisan over 6 years ago
What's new:
webcontrol_parms
option to enable motion HTTP API on motion 4.1 or laterPublished by ccrisan almost 7 years ago
What's new:
What's new: