Closed donvipre closed 5 years ago
motionEye does not yet work with motion 4.2
ok, I'll be patient. Thank you for the fast response :)
I'm not sure this is related to motioneye - that log mentions DNS resolution failures.
so this could be related to motion 4.2 and DNS? ;) As the hostname is existing and resolvable on the machine. Thanks very much for the hint.
That's my thoughts, those log messages look like they originate from motion
motionEye does not yet work with motion 4.2 Oh, that's why I am having issues!
I can only see one (local) motion cam out of 6 (3 on the Pi3 running motionOS and 3 on an Orange Pi PC+). Motion does not show any of the PC+ cams until I pkill motion on the local Pi3 running motionOS, weird? One of the "dependencies" was not installed before I had motion running (before I installed motionOS) and I'm using "daemon OFF" for motion.conf, because "ON" doesn't work for me (I'm using systemctl to manage motion, but have "daemon ON" for motionOS (as per this guide). I'm using the latest motion Debian repo and the October 2018 RPi desktop OS.
Very promising application! ;)
use gdebi
to automatically install missing motion 4.2 dependency libmicrohttpd12
. It works for me but not helps much. motion 4.2 deprecated a lot of configuration parameter names and generates a lot of warnings. It also remove stream_motion
which slows down the stream when no motion detected. In a word it breaks things.
Hello, Is there still a problem with motion 4.2 and motioneye? Thank you
https://github.com/ccrisan/motioneye/releases/tag/0.40rc1 adds support for Motion 4.2.
I have a CentOS 7.5 machine running motioneye and motion 4.1 since a year now.
I started to build motion from here https://github.com/Motion-Project/motion
After now upgrading from 4.1 to 4.2 the live camera in motioneye does not work anymore. I noticed also some errors in the log of my systemd unit motioneye
A rollback to motion 4.1 got the live camera working again.