Closed Gonioul closed 2 years ago
Can the PC ping the mobile? Or the Pi?
Can the PC ping the mobile? Or the Pi?
I re-flashed SD card and changed IP rather than DHCP sorting it and now all is fine. Thanks very much.
The new image worked without issue on my new pi zero 2 W. All the hard work by those involved is much appreciated. Thanks
Thank you so much, I also confirm that the new image worked for me. FWIW, I noticed that the /boot partition is mounted read-only, whereas both / and /data are mounted read-write. Amazing work, very much appreciated!
@starbasessd @wpa-3 What did you exactly do as i hit the same issue with that last screenshot of "panic: rebooting in xx sec (caused by network)". I tried looking up the manual setup work but not sure what you mean by that. Too noob i guess :P
@sobo82 When you image the SDCard how are you doing it? What OS and app are you creating it on? Windows 10? MacOS? Linux? In Windows 10, Using Balena Etcher? Win32DiskImager? RaspiImager? In MacOS RaspiImager or something else? In Linux RaspiImager or writeimage.sh or something else? Do you have a valid wpa_supplicant.conf file? Do you place it in the first partition (named 'boot') of the SDCard prior to ejecting it? Can you post with the ssid and psk info redacted? It should look something like this: /-/-/-/-/- ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 country=US
network={ ssid="ssid" psk="password" key_mgmt=WPA-PSK }
@starbasessd i put my SD card in my windows pc format it with SD Card Formatter by Tuxera Go to https://github.com/jawsper/motioneyeos/releases/tag/20211113 and download that image Boot my Balena Etcher and let it do its magic
I have no idea how to access that conf file, all i see from a windows system is my e: like this: And an empty F: (cant read it like usual) which are both that same SD card but different partition
Follow this guide: https://github.com/ccrisan/motioneyeos/wiki/Wifi-Preconfiguration Continue with step 5 in the Windows section.
Do make sure you enable file extensions else it'll become wpa_supplicant.conf.txt
which will not work (see here for instructions on enabling file extensions
You would copy the wpa_supplicant.conf file to your E: drive before moving it over to your PiZeroW2. You need to create the file with something like NotePad++ (not notepad or wordpad or Word)
The wiki recommends using Notepad++, you can install that from here https://notepad-plus-plus.org/
Thanks all!
https://github.com/ccrisan/motioneyeos/wiki/Wifi-Preconfiguration and https://github.com/jawsper/motioneyeos/releases/tag/20211113 totally did it for me!
I'll see how i can fix the camera as it worked on the normal Raspberry os but not here, yet! Its the WS-10299 by Waveshare Electronics but i bet i'll find it somewhere along the pages. If not i'll just find a post to see if someone had the same issue.
@jawsper @jasaw @ccrisan Might want to check out this thread: https://github.com/Motion-Project/motion/issues/1434 There are issues with the MMAL cameras and Bullseye due to RPiFoundation ripping out raspivid and raspistill (and the supporting software) in favor of PiCamera and libcamera. This breaks motion. There are some 'work arounds' but nothing promising at this point for legacy software.
Thanks all!
https://github.com/ccrisan/motioneyeos/wiki/Wifi-Preconfiguration and https://github.com/jawsper/motioneyeos/releases/tag/20211113 totally did it for me!
I'll see how i can fix the camera as it worked on the normal Raspberry os but not here, yet! Its the WS-10299 by Waveshare Electronics but i bet i'll find it somewhere along the pages. If not i'll just find a post to see if someone had the same issue.
This worked for me too. Followed the installation instruction from the wiki with jawsper's image.
Hi,
Pi Zero 2 W is supposed to be Pi 3 compatible in Pi Zero format.
Has someone tested it with motioneyeos?
Regards,
Hi,
Pi Zero 2 W is supposed to be Pi 3 compatible in Pi Zero format.
Has someone tested it with motioneyeos?
Regards,
I am not able to boot PI zero 2 with motioneyeos. I also put the correct wpa_supplicant. But it works fine with the Raspbian.
@jawsper has done an update to motionEyeOS to enable the PiZeroW2. Be careful of which RaspberryPiOS you use, do not use Debian BullsEye / RPiOS Bullseye due to issues with the change from raspivid/Picamera to libcamera and no python support for libcamera
Hi,
Pi Zero 2 W is supposed to be Pi 3 compatible in Pi Zero format.
Has someone tested it with motioneyeos?
Regards,
I have no led light and no sign of life.
Using the motionEyeOS from here for Pi or P3 isn't working. If you grab the build listed here: https://github.com/ccrisan/motioneyeos/issues/2827#issuecomment-967737252 I've tested on Pi3B+ and it works, but I don't have a PiZeroW2 to test with. Other users report it working.
Hi,
On 21/11/20 12:06PM, pdesimonee wrote:
I have no led light and no sign of life.
I had the same symptoms, which were fixed by using the image mentioned in the previous post. Just flash your SD card with it using your favorite tool and you should hopefully be good to go.
You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/ccrisan/motioneyeos/issues/2827#issuecomment-974704685
I confirm jawsper build seems to work fine, except I failed to disable led at boot with /boot/config.txt. But echo 255 > /sys/class/leds/led0/brightness does the trick in /data/etc/userinit.sh Restoring motioneye config also works quite fine, but I had to do it twice, maybe I missed something.
Well it seems, echo 255 or 0 depends on /boot/config.txt dtparam=act_led_activelow=off or on, but I don't know how to default the led to off without a script.
A big thankyou to @jawsper =) I've been wanting to give Motion Eye OS a run on my Zero 2W from the first day I got it. I used the official Raspberry Pi imager on my Windows 10 PC. Then notepad++ for my wpa_supplicant.conf. Booted up and connected to my WIFI no problem.
I also have motioneye running on Zero2 after having downloaded the update image. I have issue with email notification but I will open a thread on this
@viaprenestina When you open a ticket, in addition to the other info asked for, include the email server, port, use tls, and timespan settings, please.
Build works great, Thank you.
Just my camera is causing a reboot... "Camera Module Automatic IR-Cut Sensor Day/Night Vision Video Webcam HD 5MP 1080P OV5647 Adjustable Focus with IR Sensor LED Light" Will check power and on a standard W
@jawsper , any chance that you merge your changes into the original project?
EDIT Thanks for your work, by the way! (and happy 2022)
@rogierlommers unfortunately, @jawsper doesn't have the access to merge it to the project. I don't know who, besides CCrisan, does. I don't, either, I just do support & documentation.
Ok, @starbasessd thanks for the info. One other question: I have the NOIR camera (the one from raspberry pi itself) connected to my rpi zero 2W. I have motioneyeOS running now, but for some reason I don't have any incoming video. What type of camera should work?
Local mmal camera, and it should be auto-discovered on startup. Run the command vcgencmd get_camera if it shows 0 for supported and discovered, there's either an issue with the cable or the camera. The blue side should be close to the black lock for the cables at both ends.
Local mmal camera, and it should be auto-discovered on startup. Run the command vcgencmd get_camera if it shows 0 for supported and discovered, there's either an issue with the cable or the camera. The blue side should be close to the black lock for the cables at both ends.
I have this output:
[root@meye-f7425028 tmp]# vcgencmd get_camera
supported=1 detected=0
Does this mean that no camera has been detected? That's quite strange, because I had this setup running before with the original rpi os. There I could use raspistill
to make a photo and use raspivid -o - -t 0 -hf -w 640 -h 360 -fps 25 | /usr/bin/cvlc -vvv stream:///dev/stdin --sout '#rtp{sdp=rtsp://:8554}' :demux=h26
to make a stream.
Are you using @jawsper s image? It looks like something isn't quite right. RPiOS (especially the 20211005 Buster, 20211030 Bullseye, and 20211202 Legacy) images have full support for RPiZero2W built in. The last 2 'official' images of motionEyeOS came out a year before the PiZero2W was released. Jawsper forked to another image. I'd like to help, but my PiZero2W is still on back order.
Are you using @jawsper s image? It looks like something isn't quite right. RPiOS (especially the 20211005 Buster, 20211030 Bullseye, and 20211202 Legacy) images have full support for RPiZero2W built in. The last 2 'official' images of motionEyeOS came out a year before the PiZero2W was released. Jawsper forked to another image. I'd like to help, but my PiZero2W is still on back order.
Yeah, I'm using release 20211113
: https://github.com/jawsper/motioneyeos/releases
Basically I did the following:
vcgencmd get_camera
is like this:[root@meye-f7425028 tmp]# vcgencmd get_camera
supported=1 detected=0
When I put the original raspberry os on the same device, then I can use raspistill to make a photo. So I don't think something is wrong with the device and/or the cables. Should I somehow "enable" the camera connection using a raspi-config alike tool?
@rogierlommers Is that the first or second version of the NoIR camera? I have a first gen NoIR camera somewhere, if I can find it, I will test that one...
@rogierlommers Is that the first or second version of the NoIR camera? I have a first gen NoIR camera somewhere, if I can find it, I will test that one...
It's the Raspberry Pi NoIR Camera V2
.
@jawsper If V1 works, V2 should work.
@jawsper If V1 works, V2 should work.
Yeah I would expect the same, but unfortunately it's not the case.
I do have a regular V2 camera somewhere, which should be the exact same hardware as the NoIR (apart from the filter), but it's probably hidden away in an unknown box currently...
@jawsper if you can find it, please do me a favour and try. I'm running out of options here. I just confirmed that everything works when I use the original raspberry pi os:
pi@raspberrypi:~ $ vcgencmd get_camera
supported=1 detected=1
UPDATE: after a clean install of motioneyeos (the same release from @jawsper ), it all works out of the box! How strange! I always thought computers were deterministic machines :).
Happy to hear you fixed the issue :smile:
Happy to hear you fixed the issue 😄
Thanks for your help. Hopefully your changes will be incorporated in the official release soon. Let me know if I can help with something.
Any sufficiently advanced technology is indistinguishable from magic.
-- A. C. Clarke
Great to hear.
Just my camera is causing a reboot... "Camera Module Automatic IR-Cut Sensor Day/Night Vision Video Webcam HD 5MP 1080P OV5647 Adjustable Focus with IR Sensor LED Light" Will check power and on a standard W
Sorry, forgot to check and reply. Works fine when connected to a decent power source.
Hey, I've been following the posts here for a while. Unfortunately, due to language barriers, I have not yet fully understood what I am doing with the ZIP archive that I downloaded from Jasper's repository. Is there an ISO file that I can download? Or can I build an ISO file from the ZIP archive so that I can flash it to my SD card? I would be happy if someone could help me.
There is an img file in the zip. You can 'burn' the img file to an SDCard the same as any other RaspberryPi image. I use Win32Disk Imager from Windows, but there are also the Raspberry Pi imager and Balena Etcher programs (available for Win 10, MacOS, RPiOS, and Linux). There are dozens, if not hundreds of You Tube videos, instructions all over the place including on the RaspberryPi.com website (under Software) on how to use the tools to get it on the SDCard.
If you are using Windows, you can use 7zip to extract the .img file from https://github.com/jawsper/motioneyeos/releases/download/20211113/motioneyeos-raspberrypi3.img.gz MacOS and most Linux can extract the file natively.
Thank you very much. I've downloaded the wrong files. Now i've got it ^^
@Jawsper was kind enough to try to create an image since none of the 'official' images support the PiZero2W.
@jawsper , since we have your attention now 😀. Do you know if it's technically possible to manually install motion/motioneye on a Rpi zero 2 W? (see here: https://github.com/ccrisan/motioneye/issues/2263)
@rogierlommers Yes. Please follow the appropriate set of instructions (Buster or Bullseye) and use motion 4.3.2.
@rogierlommers Yes. Please follow the appropriate set of instructions (Buster or Bullseye) and use motion 4.3.2.
Thanks; will do that. What exactly is the benefit of running montioneyeOS then? (if you can install it yourself)
Hi,
Pi Zero 2 W is supposed to be Pi 3 compatible in Pi Zero format.
Has someone tested it with motioneyeos?
Regards,