Releases: motioneye-project/motioneye
0.43.1b2
What's new:
- Restored authentication with surveillance user: #2944 @zagrim
- Conflicting
motion.service
is now disabled bymotioneye_init
execution: #2980 @MichaIng - Turkish language added: #2965 @ToramanO (I hope the GitHub account is correct 😉)
- Restored working schedule functionality: #2987 @zagrim
- Optimised camera button display, allowing up to 16 action buttons: #2903 @sevimuelli
0.43.1b1
What's new:
- BREAKING: motionEye requires now Python 3.7 or later and does not support Python 2 anymore.
- Multi-language support has been added. You can contribute to translations on Weblate.
- Support for motion 4.4 - 4.6 has been added: #2462
Remember to update your custom options in case: https://motion-project.github.io/motion_config.html#Configuration_OptionsAlpha - Support for WebDAV uploads has been added: #1743
- Support for S3 uploads has been added: #2376
- A long list of larger and smaller enhancements and bug fixes, too many to list them here.
0.42.1
0.42
What's new:
- Added RTMP support (thanks @mcd1992)
- Added movie passthrough option support (thanks @wmig)
- Adjusted validations for various fields (thanks @jwheeler91)
- Added h264 V4L2 M2M support (Odroid XU4 hardware accelerated encoding)
- Additional options are now hidden when surveillance user is logged in
- (Hopefully) fixed erroneous fps reporting
0.41
What's new:
- Fixed video streams not working on Chrome 76+ (thanks @rajendrant)
- Dockerfile: fixed path to
vcgencmd
(thanks @kleini) - Fixed issues when using unicode in notification hooks (thanks @zagrim)
- Added more validations on the UI side (thanks @zagrim)
- More general
/usr/bin/env bash
shebang is now used (thanks @phaethon) - Fixed Google Drive upload cleanup issue (thanks @chiastic-security)
- Current value is now shown while adjusting sliders (thanks @zagrim)
- Fixed Clean Cloud bug with leading/trailing slash in path (thanks @bob-lee)
- Various Google Photos upload improvements (thanks @bob-lee)
- Added support for
threshold_maximum
andthreshold_tune
Motion options - Credentials are no longer embedded in the URL when using simple MJPEG cameras
- Removed advanced options flag
- Added required headers to prevent caching of streaming frames
- Fixed smart mask sluggishness description
0.41rc1
0.40
What's new:
- autocapitalization for usernames and passwords is now disabled (thanks @timmo001)
- better masked out area color (thanks @19grad).
- added support for
mjpeg://
URLs (thanks @Queuecumber) - added experimental support for removing old media files from Google Drive (thanks @bob-lee)
- removed compatibility with Motion 3.x
- added support for Motion 4.2
- all V4L2 video controls can now be adjusted from the UI
- added a migration script to help converting from old Motion formats to Motion 4.2
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
0.40rc5
What's new:
- fixed streaming image corruptions due to HTTP headers misuse
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
0.40rc4
What's new:
- fixed MJPG client when using streaming authentication with Motion
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
0.40rc3
What's new:
- MMAL cameras don't have V4L2 controls
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