Closed subash774 closed 2 years ago
Have you attempted to use the camera in Raspbian, or connected to a PC or MAC?
On Sun, Mar 15, 2020 at 1:49 PM Subash Poudyal notifications@github.com wrote:
Preliminary Docs
I confirm that I have read the CONTRIBUTING https://github.com/ccrisan/motioneyeos/blob/master/.github/CONTRIBUTING.md guide before opening this issue.
I confirm that I have read the FAQ https://github.com/ccrisan/motioneyeos/wiki/FAQ before opening this issue. motionEyeOS Version
I am running motionEyeOS version: 20190911 Board Model
I am using the following board/model: Raspberry PI 3B+ Camera
I am using the following type of camera: V4L2 USB camera Network Connection
My motionEyeOS unit is connected to the network via: Ethernet THE ISSUE
I was on the same version previously and everything was working perfectly fine. I had a problem with my broadband once and the stream showed still image (didn't update the live feed) so I rebooted the Pi. Ever since, the camera doesn't show up on V4L2 list.
When I try vcgencmd get_camera , I get supported=1 detected=0 and /dev/video0 doesn't exist either. It just suddenly stopped recognising the camera, nothing has changed. I even re-flashed the motioneyeos image onto my SD card and restarted the whole process, no change.
Any help would be appreciated.
Thanks!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2327, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHJVKPWZRCLZGUENWGTRHUILBANCNFSM4LLHB3KQ .
-- Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52" W85° 45' 8.56"
Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?
Yepp, tried and tested, the camera works fine on PC and Mac.
Do you have the ability to SSH to the motionEyeOS Pi, or connect a keyboard and mouse to the Pi? Also, please attach the dmesg and boot logs (under Expert Settings)
On Sun, Mar 15, 2020 at 3:21 PM Subash Poudyal notifications@github.com wrote:
Have you attempted to use the camera in Raspbian, or connected to a PC or MAC? … <#m8342384994715438606> On Sun, Mar 15, 2020 at 1:49 PM Subash Poudyal @.***> wrote: Preliminary Docs I confirm that I have read the CONTRIBUTING https://github.com/ccrisan/motioneyeos/blob/master/.github/CONTRIBUTING.md guide before opening this issue. I confirm that I have read the FAQ https://github.com/ccrisan/motioneyeos/wiki/FAQ before opening this issue. motionEyeOS Version I am running motionEyeOS version: 20190911 Board Model I am using the following board/model: Raspberry PI 3B+ Camera I am using the following type of camera: V4L2 USB camera Network Connection My motionEyeOS unit is connected to the network via: Ethernet THE ISSUE I was on the same version previously and everything was working perfectly fine. I had a problem with my broadband once and the stream showed still image (didn't update the live feed) so I rebooted the Pi. Ever since, the camera doesn't show up on V4L2 list. When I try vcgencmd get_camera , I get supported=1 detected=0 and /dev/video0 doesn't exist either. It just suddenly stopped recognising the camera, nothing has changed. I even re-flashed the motioneyeos image onto my SD card and restarted the whole process, no change. Any help would be appreciated. Thanks! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2327 https://github.com/ccrisan/motioneyeos/issues/2327>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHJVKPWZRCLZGUENWGTRHUILBANCNFSM4LLHB3KQ . -- Thanks Kevin Shumaker Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel N38° 19' 56.52" W85° 45' 8.56" Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?
Yepp, tried and tested, the camera works fine on PC and Mac.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2327#issuecomment-599252816, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHOTU6EBBQGDZQNSCPDRHUTE7ANCNFSM4LLHB3KQ .
-- Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52" W85° 45' 8.56"
Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?
Yeah, I can SSH into it and everything, in terms of OS, all is fine, the only problem is the USB camera that worked fine on the same release of the OS has now stopped recognising the camera.
Can you re-image, and use 20200203? https://github.com/ccrisan/motioneyeos/releases/tag/20200203
On Sun, Mar 15, 2020 at 4:19 PM Subash Poudyal notifications@github.com wrote:
dmesg.log https://github.com/ccrisan/motioneyeos/files/4334998/dmesg.log
Yeah, I can SSH into it and everything, in terms of OS, all is fine, the only problem is the USB camera that worked fine on the same release of the OS has now stopped recognising the camera.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2327#issuecomment-599259227, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHJPPLJDPMO5JPYBXCLRHUZ5NANCNFSM4LLHB3KQ .
-- Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52" W85° 45' 8.56"
Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?
I shall try it tomorrow and let you know, thanks a lot.
@starbasessd Tried with the pre-release image, same result.
dmesg log attached.
Thanks a lot for your help :) dmesg (1).log
At this point, I'm going to have to give up. @ccrisan and @jawas may have more ideas.
On Tue, Mar 17, 2020 at 2:31 PM Subash Poudyal notifications@github.com wrote:
@starbasessd https://github.com/starbasessd Tried with the pre-release image, same result. [image: Screenshot 2020-03-17 at 18 30 16] https://user-images.githubusercontent.com/20229130/76889384-6866f500-687d-11ea-9b12-c369865590af.png
dmesg log attached.
Thanks a lot for your help :) dmesg (1).log https://github.com/ccrisan/motioneyeos/files/4345123/dmesg.1.log
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2327#issuecomment-600230818, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHJ6GCE4NFGGRHYH72LRH66YZANCNFSM4LLHB3KQ .
-- Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52" W85° 45' 8.56"
Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?
That looks like a hardware problem. Check that the camera device actually works on that board.
@ccrisan I also switched the SD Card with MotionEyeOS to another board (3B+ as well), same problem. It's baffling how it was just working absolutely fine and now it's suddenly stopped working and camera is working fine when tested on PC as well as OpenCV python
If you change the board, the video device path might also change. I recommend either manually removing /data/etc/camera*.conf
or flashing the OS image from scratch.
After @starbasessd suggested, I flashed same and different versions of the OS, same result. I am thinking about using MotionEye with Raspbian, see if that works.
I have the same problem
Unfortunately, I haven't been able to solve it yet, do let me know if you find a solution
Turns out the problem for me was that the pi's USB port failed and no keyboard or mouse worked with Raspbian on that board.
Not sure if this is relevant. I have a Pi 3 A.... On a base image of MotionEyeOS... if I set the "Captured Before frames" much higher than 30 (cant give an exact number, though I know Ive tried 90), the camera turns off, its no longer detected/no image is visible, even on a reboot of MotionEyeOS....
I diagnosed by setting up a new SD card image and when I got to that setting, if I set it too high, the camera image is gone.... if I dropped the setting back down to something like 10, the camera image re-appeared/started working again.
It's distinctly possible, that to buffer the last > whatever number of frames, it runs out of resources (memory) and video fails. If I get a chance this weekend, I can test. I can try a Pi3B+ and a Pi4B-4GB and see if there is a significant difference. What say you @ccrisan and @jasaw?
On Fri, May 1, 2020 at 2:05 PM erew123 notifications@github.com wrote:
Not sure if this is relevant. I have a Pi 3 A.... On a base image of MotionEyeOS... if I set the "Captured Before frames" much higher than 30 (cant give an exact number, though I know Ive tried 90), the camera turns off, its no longer detected/no image is visible, even on a reboot of MotionEyeOS....
I diagnosed by setting up a new SD card image and when I got to that setting, if I set it too high, the camera image is gone.... if I dropped the setting back down to something like 10, the camera image re-appeared/started working again.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2327#issuecomment-622496940, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHPR7IFVJZVLHHSOCLLRPMFOZANCNFSM4LLHB3KQ .
-- Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52" W85° 45' 8.56"
Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?
Test Setup #1 RPi3B, Tiga USB Generic USB Webcam, motionEyeOS 20200203-Pi3 8GB SD Card Set Captured Before Frames incrementally from 10 - 100. in steps of 10 Waited for motion triggered recording & pics It recorded, on average, about 3 minuted of video per motion, and a ton of pics at the higher numbers Was unable to reproduce. Please send all your settings, and attach all you logs, and note at what time you noticed the no image issue Also, if you moved the number of Captured Befor Frames back below 10, was the image restored?
On Fri, May 1, 2020 at 2:13 PM Kevin Shumaker kevin.shumaker@gmail.com wrote:
It's distinctly possible, that to buffer the last > whatever number of frames, it runs out of resources (memory) and video fails. If I get a chance this weekend, I can test. I can try a Pi3B+ and a Pi4B-4GB and see if there is a significant difference. What say you @ccrisan and @jasaw?
On Fri, May 1, 2020 at 2:05 PM erew123 notifications@github.com wrote:
Not sure if this is relevant. I have a Pi 3 A.... On a base image of MotionEyeOS... if I set the "Captured Before frames" much higher than 30 (cant give an exact number, though I know Ive tried 90), the camera turns off, its no longer detected/no image is visible, even on a reboot of MotionEyeOS....
I diagnosed by setting up a new SD card image and when I got to that setting, if I set it too high, the camera image is gone.... if I dropped the setting back down to something like 10, the camera image re-appeared/started working again.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ccrisan/motioneyeos/issues/2327#issuecomment-622496940, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEZTUHPR7IFVJZVLHHSOCLLRPMFOZANCNFSM4LLHB3KQ .
-- Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52" W85° 45' 8.56"
Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?
-- Thanks
Kevin Shumaker
Personal Tech Support https://kevinshumaker.wixsite.com/thethirdlevel
N38° 19' 56.52" W85° 45' 8.56"
Semper Gumby “Don't tell people how to do things. Tell them what to do and let them surprise you with their results.” - G.S. Patton, Gen. USA Ethics are what we do when no one else is looking. Quis custodiet ipsos custodes? “There is no end to the good you can do if you don’t care who gets the credit.” - C Powell You know we're sitting on four million pounds of fuel, one nuclear weapon and a thing that has 270,000 moving parts built by the lowest bidder. Makes you feel good, doesn't it?
Mines a Pi3a+... so I think 1/2 the memory of a Pi3B...which Im guessing is the issue in my instance. Personally, I have a happy medium for what I need, though I just thought Id mention it being an issue that seems to kill the camera.
I believe that its motion re-starting after making the change and being unable to allocate enough memory to buffer that many frames (in my case) though thought may be relevant to other people... maybe asking their system to do too much?
When I put the settings too high, my system says:
And then on a refresh, the camera is blank/black/a placeholder
As for settings:
System: Pi3a+ (512mb of Ram) Camera: Pi original camera 1.3 256MB reserved for GPU SSH and FTP are turned OFF Camera is at 1900x1080, rotated and on 30fps Text overlay, scale 4 Streaming set to 25Fps at 50% quality Image resizing+Motion Optimization are OFF Still images are on Manual Only Movies are motion triggered at 75% quality with a max of 120 seconds.
Motion detection.... 0.2% Auto threshold tuning OFF. Auto noise detection ON Light Switch Detection at 50% Despeckle ON Motion Gap 20 Captured BEFORE (What we are discussing, but fine at 10 and ? higher) Captured After 30 Minimum Motion Frames 2 Mask ON and Editable Show Frame changes ON
This is in the dmesg (at the time of changing the settings... I think)
[ 8716.496845] Out of memory: Kill process 24553 (motion) score 749 or sacrifice child
[ 8716.496882] Killed process 24553 (motion) total-vm:296928kB, anon-rss:184404kB, file-rss:0kB, shmem-rss:0kB
[ 8716.527466] oom_reaper: reaped process 24553 (motion), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
And the motion.log
2020-05-02 17:04:52: [motioneye] ERROR: motion failed to start
Traceback (most recent call last):
File "usr/lib/python2.7/site-packages/tornado/web.py", line 1548, in _stack_context_handle_exception
File "usr/lib/python2.7/site-packages/tornado/web.py", line 1756, in wrapper
File "/usr/lib/python2.7/site-packages/motioneye/handlers.py", line 290, in post
File "/usr/lib/python2.7/site-packages/motioneye/handlers.py", line 205, in wrapper
File "/usr/lib/python2.7/site-packages/motioneye/handlers.py", line 522, in set_config
File "/usr/lib/python2.7/site-packages/motioneye/handlers.py", line 373, in set_camera_config
File "/usr/lib/python2.7/site-packages/motioneye/handlers.py", line 507, in check_finished
File "/usr/lib/python2.7/site-packages/motioneye/handlers.py", line 482, in finish
File "/usr/lib/python2.7/site-packages/motioneye/motionctl.py", line 129, in start
Exception: motion failed to start
2020-05-02 17:04:52: [motioneye] ERROR: 500 POST /config/0/set/?_=AAAAAAAAAAAAAAA&_username=admin&_signature=AAAAAAAAAAAAA (192.168.1.248) 2365.79ms
2020-05-02 17:04:52: [motioneye] ERROR: motion not running, starting it
2020-05-02 17:04:54: [motioneye] ERROR: failed to start motion: motion failed to start
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/motioneye/server.py", line 325, in checker
File "/usr/lib/python2.7/site-packages/motioneye/motionctl.py", line 129, in start
Exception: motion failed to start
2020-05-02 17:04:54: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:54: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:54: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:55: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:55: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:55: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:55: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:55: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:56: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:56: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:56: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:56: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:56: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:57: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
2020-05-02 17:04:57: [motioneye] WARNING: Connect error on fd 16: ECONNREFUSED
No comments after more than 60 days. If you are still having issues, please open a new issue.
I can now confirm that version 20200203 https://github.com/ccrisan/motioneyeos/releases/tag/20200203 works with my USB cam (Logitech C310) The latest version did not work for me either. After this hint https://github.com/motioneye-project/motioneyeos/issues/2327#issuecomment-599262623 it works now, thanks for that
its power man.. use a powered switch or powered adapter.
Preliminary Docs
I confirm that I have read the CONTRIBUTING guide before opening this issue.
I confirm that I have read the FAQ before opening this issue.
motionEyeOS Version
I am running motionEyeOS version: 20190911
Board Model
I am using the following board/model: Raspberry PI 3B+
Camera
I am using the following type of camera: V4L2 USB camera
Network Connection
My motionEyeOS unit is connected to the network via: Ethernet
THE ISSUE
I was on the same version previously and everything was working perfectly fine. I had a problem with my broadband once and the stream showed still image (didn't update the live feed) so I rebooted the Pi. Ever since, the camera doesn't show up on V4L2 list.
When I try
vcgencmd get_camera
, I getsupported=1 detected=0
and/dev/video0
doesn't exist either. It just suddenly stopped recognising the camera, nothing has changed. I even re-flashed the motioneyeos image onto my SD card and restarted the whole process, no change.Any help would be appreciated.
Thanks!