| Git Clone URL: | https://aur.archlinux.org/motioneye.git (read-only) |
|---|---|
| Package Base: | motioneye |
| Description: | web-based user interface for motion |
| Upstream URL: | https://github.com/ccrisan/motioneye/ |
| Licenses: | |
| Submitter: | nojan |
| Maintainer: | jskier |
| Last Packager: | jskier |
| Votes: | 8 |
| Popularity: | 0.030230 |
| First Submitted: | 2015-07-28 12:31 |
| Last Updated: | 2019-05-01 15:29 |
Breaking update! Updated to RC for motion 4 support. This drops support motion 3.
Reference Calin's update: 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.
@benalexau, done, and pushed to .3, thank you for the heads up.
With update to python2-tornado 5.1.0-1 this package also requires as a dependency python2-futures to overcome error, "pkg_resources.DistributionNotFound: The 'futures' distribution was not found".
Be advised, with .39 and some new changes to ffmpeg, it appears that the motioneye config file needs to be at the latest version, or there will be errors and no display (tested on arm pi cam and x64 web cam). I will look into updating the package to save existing configuration and create a new one.
Will update later tonight.
My testing machine have given up the ghost and I do not have the time at the moment to keep maintaining this package.
I will disown so someone else can take it
@francisuk1989 I had the same problem with motion and my CPU. Installing motion-git from AUR fix the problem for me.
I'm running pure Arch Linux x64. Can't really help you with regards to antergos.
But yeah as ccrisan says, the motion logs will probably hint to an answer ;)
@nojan
1) What distro are you running on Arch? and it is x64 or x86? I am running antergos-17.3-x86_64.
2) Posted the issues im facing at https://github.com/ccrisan/motioneye/issues/471
motion.log
[francisuk1989@archyi7desktop ~]$ nano /var/log/motion.log
GNU nano 2.7.5 File: /var/log/motion.log
[22025536:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motioneye/motion.conf
[22025536:motion] [WRN] [ALL] thread config option deprecated use camera
[22025536:motion] [NTC] [ALL] config_camera: Processing camera config file thread-1.conf
[22025536:motion] [NTC] [ALL] motion_startup: Motion 4.0.1 Started
[22025536:motion] [NTC] [ALL] motion_startup: Logging to syslog
[22025536:motion] [NTC] [ALL] motion_startup: Using default log type (ALL)
[22025536:motion] [NTC] [ALL] motion_startup: Using log type (ALL) log level (WRN)
[1:ml1] [ALR] [NET] netcam_start: Network Camera thread starting... for url (rtsp://10.0.32.66/12)
[francisuk1989@archyi7desktop log]$ sudo pacman -S motion
warning: motion-4.0.1-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) motion-4.0.1-2
Total Installed Size: 0.90 MiB
Net Upgrade Size: 0.00 MiB
The web Interface works fine but adding the IP Camera is an no :(
Motioneye starts upp correctly when I test it here so I don't think it has anything to do with the packaging.
I would open an issue on the motioneye github issue tracker.
https://github.com/ccrisan/motioneye/issues
Pinned Comments
jskier commented on 2019-03-08 15:31
Breaking update! Updated to RC for motion 4 support. This drops support motion 3.
Reference Calin's update: 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.