I am running the latest docker from ghcr.io/motioneye-project/motioneye:edge under Debian. I also have an old 0.42 direct install on an old raspi running fine (motion is 4.4.0+git20211023-2645d67).
All worked so far after a bit of tweaking. However one strange issue occurs that I can't really explain.
I added an cheap PTZ cam with rtsp://IP:554/onvif1 - works fine. (user name and pw are in the conf file ...)
On the old 0.42 all worked fine with below "extra options".
netcam_high_url rtsp://IP:554/onvif1
However when I add this on the 0.43 docker the stream just stops. Which is strange as the option should only be used when motion is detected. It works fine on other cams on the same docker.
Any ideas? Might be a motion issue after all?
docker logs motioneye
configure_logging cmd motioneye: False
configure logging to file: None
INFO: hello! this is motionEye server 0.43.1b2
INFO: cleanup started
INFO: wsswitch started
INFO: tasks started
INFO: mjpg customer garbage collector has started
INFO: server started
ERROR: mjpg client timed out receiving data for camera 8 on port 9088
motionEye Version: 0.43.1b2
Motion Version: 4.7.0
OS Version: Linux 6.1.0-25-amd64
Hi,
I am running the latest docker from ghcr.io/motioneye-project/motioneye:edge under Debian. I also have an old 0.42 direct install on an old raspi running fine (motion is 4.4.0+git20211023-2645d67).
All worked so far after a bit of tweaking. However one strange issue occurs that I can't really explain. I added an cheap PTZ cam with rtsp://IP:554/onvif1 - works fine. (user name and pw are in the conf file ...) On the old 0.42 all worked fine with below "extra options".
netcam_high_url rtsp://IP:554/onvif1However when I add this on the 0.43 docker the stream just stops. Which is strange as the option should only be used when motion is detected. It works fine on other cams on the same docker. Any ideas? Might be a motion issue after all?