Closed fdapport closed 1 year ago
s6-rc: info: service base-addon-banner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service base-addon-log-level: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service base-addon-log-level successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service init-nginx: starting s6-rc: info: service init-motioneye: starting backing up /data/motioneye/motioneye.conf s6-rc: info: service init-nginx successfully started s6-rc: info: service init-motioneye successfully started s6-rc: info: service motioneye: starting s6-rc: info: service motioneye successfully started s6-rc: info: service nginx: starting s6-rc: info: service nginx successfully started s6-rc: info: service discovery: starting [12:13:38] INFO: Starting motionEye... configure_logging cmd motioneye: False configure logging to file: None INFO: hello! this is motionEye server 0.43.0 mount error(16): Resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) mount error(16): Resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) mount error(16): Resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) INFO: cleanup started INFO: wsswitch started INFO: tasks started INFO: mjpg customer garbage collector has started INFO: smb mounts started INFO: server started [12:13:46] INFO: Starting NGinx... [12:13:47] INFO: Successfully send discovery information to Home Assistant. s6-rc: info: service discovery successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started
The same thing happened to me. I deleted the cameras that were failing and added them again and then everything was ok.
I have tried as you have sugested, remove the camera and add a new one,, some result,, " Enable to open video device" error
Hi, take a look on the /var/log/motion.log file within the motioneye container, you should find more info about your problem. Regards
Unfortunately I do NOT have knowledge on the commands of HA to have this information,, could somebody help me... Thanks, Franco
After I have update the Operating System 10.1 now also on 0.18.0 NOT working anymore motioneyes!!!, I have update to 0.19.1 but ONLY the rtsp camera still working, somebody could help me to fix this issue, please help
Any NEWS on this issue? I stil have cameras the NOT working anymore after I have update it to 0.19.1
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
Is there any patch for this issue? I have exactly the same problem with IP camera that provides jpeg feed over http. It's working on motion service but it is not working on motioneye 0.19.1. I didn't have a chance to verify it on previous version of motioneye addon.
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
Problem/Motivation
update to 0.19.1 from 0.18.0 and the http camera not working, error: "Enable to open video device"
Expected behavior
Open the video camera and see the video but I see a grey screen... the RTSP cameras works
Actual behavior
when open motioneyes on the https camera I have a grey screen and the error on the top left, "enable to open the video device"
Steps to reproduce
If I comeback to 0.18.0 the camera work again, version HA 2023.04.0, operation system 9.5, frontend 20230411.1 using a Raspberry Pi 4.
Proposed changes