Sryously wrote: ↑
Tue Sep 24, 2019 2:44 pm
ras07 wrote: ↑
Tue Sep 24, 2019 6:04 am
Sryously wrote: ↑
Tue Sep 24, 2019 5:52 am
It's not immediate, it's a few mins after running the camera, viewing or recording, the camera and Pi are still powered but not responding. Hmmm, I guess your right about burning Raspbian though, seeing as I can just give it commands for an hour and it runs normally, so it should be something going on with RPi Cam Web Interface installation then? Apache couldn't be causing it, could it? Is there recommended install settings for a Pi Zero W or something?
Apache defaults should work fine. Check the connections. I've had very sporadic weird stuff happen with flaky camera cable connections.
Shoot, it was working fine for over an hour last night disconnecting and reconnecting the camera cable! Then I stopped the camera on the web interface. This morning I enable camera and again it works, but for 5 minutes, then nothing. Unplug power and reconnect, works again. Play with picture settings and stuff for like an hour, see how bright I can get the picture and then...I turn on the lights and it's gone again? Did turning on the lights make it do that or just coincidence? LOL I'm using a 2.5Amp power adapter, I have a heatsink on the Zero W. One thing I was noticing, I mentioned I had tried MotionEye before, the address ended with /admin/ instead of /html/ but both still work?
Edit: Forget I mentioned traces of MotionEye seeming to be left over after 3 formats, I think it was Android loading showing a page that wasn't there.
Mate, I've been banging my head against a brick wall for the past two weeks with this zero wh I bought to do the exact same thing you are, and with the same results.
The bottom line is that sooner or later, usually sooner, when recording video with raspivid, something is causing the BCM2835 driver to crash, and given this controls a bunch of important stuff around memory, interrupts and even the USB stack, it being hosed either totally locks up the system, or even more weirdly for me leaves things completely inconsistent.
What I did, after reading through the following thread, is void my warranty and over voltage the unit (over_voltage=4 and force_turbo=1 to /boot/config.txt) and having done that, I've now been running RPi Cam Control and MotionEye without issue for a couple of days.
The thread I got this info: https://www.raspberrypi.org/forums/view ... 4AtKmxIqmc
The more important question for me is whether:
a) a small bunch of units are not quite fabbing up to spec and exhibit issues, possibly with power supply which we know is a sensitive issue with these Pi given overvoltaging seems to help in many cases
b) all Pi 0 have the issue and many/most just move on when it doesn't work and implement a different solution, or perhaps, there's just not that many people using Pi 0's for security camera functionality
c) It's an issue distinct to the Raspbian Jessie/Buster releases, and MotionEye, which uses BuildRoot to build the base operating system
I'd love to investigate this further and try and find an answer, at this point I consider the 0w unsuitable for camera duty, and have purchased several 3a's, as my 3B setup worked for years without so much as a keystroke of attention in the exact same setup.