Raspberry pi 4 & Motion eye OS

[Afolabi Adekunle]

I installed motion eyeOS on a 32gb SdCard, set up  wpa_supplicant.conf file and inserted the sdcard inside raspberry pi 4, I am unable to connect to my mobile phone access point(it is not discovered)

[StarbaseSSD]

Try it without spaces in the SSID on the phone and in the wpa_supplicant.conf file

Make sure the wpa_supplicant.conf file doesn't have a .txt at the end of the file name.

[StarbaseSSD]

Be sure to use dev20201026 for the version of motionEyeOS for the Pi4.

[Afolabi Adekunle]

Thank you for your prompt response, Its working now, I changed the ssid and also used version 20201026

[Nick P]

I can't find a newer thread that relates to motioneyeOS and the Pi4 than this.

I have tried to get motioneyeOS working on a Pi 4 that I have just managed to obtain, having used it successfully with a Pi ZeroW using motioneyeos-raspberrypi-20200606.img.xz to create a card.

Following the instructions I have used motioneyeos-raspberrypi4-dev20201026.img.xz (and motioneyeos-raspberrypi-dev20201026.img.xz , in case I had misunderstood the instruction to use dev20201026 for the Pi 4), following the steps that I followed to create the Pi zero version. Anyway whichever version of dev20201026 I used to create the card turning the machine on gives me a black screen with some Pi gobbledegook on it.

I have picked out some of the items that I think indicate what the problem may be.

It says

"Firmware Jul 17 2020 11:05:44", "start.elf is not compatible" , and "This board requires newer software".

I have repeated the creating process using different cards and get the same result each time. I am sure I have seen somewhere in passing a reference to just this issue, but cannot now find it again.

Am I doing something wrong, or is there an underlying issue with the OS or the Pi that means I am destined to fail with my Pi4?

Nick P.

[Michael Cooper]

Hello Nick P,

I never use the Dev ever the one that worked for me was https://github.com/motioneye-project/motioneyeos/releases/tag/20200606 and i did it on a the RPi4 - 4 gb model B and it worked fine. I am not sure what your setup is but i ended up installing it on a VM with Ubuntu Server 20.04.6 and it was awesome make sure you have a big storage drive for it I ended up making a NAS and sharing it with the OS and if you need help we can schedule some time I would happy to walk you through it or you can use my article I wrote on it.

Let me know,

Michael

--
You received this message because you are subscribed to the Google Groups "motioneye" group.
To unsubscribe from this group and stop receiving emails from it, send an email to motioneye+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/motioneye/7b1baf05-2136-4030-846a-77f598bf5614n%40googlegroups.com.

--
Michael Cooper
Senior Systems Engneer
Linux Certified
RPi Hobby Blog

[StarbaseSSD]

Nick:

The message you are getting indicates the bootloader is kind of old. The last known good version for motionEyeOS is April 29 2021 and yours is reporting Jul 17 2020. You would want to upgrade it to NO LATER THAN Apr 29 2021. There are several reference documents on the Raspberry Pi site, to update to a specific version. I am not at home, so I can't get you the link right now. Do NOT update to the latest version, either.

More and more people who want to use motionEye on RPi4 are finding it's easier to install RPiOS Buster Legacy Lite (if you need CSI cameras) or RPiOS Bullseye Lite if you only have Network or USB cameras using the install instructions on the right from here:
Buster

or

Bullseye

[Nick P]

Thanks for these suggestions. I will see how I get on with the Bullseye lite method.

Nick P.

[Nick P]

Tried the method for Bullseye (64bit) here https://github.com/motioneye-project/motioneye/wiki/Install-on-Raspbian-Bullseye.

The method given failed as it gave a 404 error for the step 2 "Install Motion".

So after some experimenting, I discovered the instructions there were completely out of date / wrong.

It was clear that the version it was suggesting to wget was hopelessly out of date.

I worked out that the latest version could be found at https://github.com/Motion-Project/motion/releases/release-4.5.1, so I changed the wget and dpkg to suit. (the is no  pi_bullseye_motion_4.5.1-1_arm64.deb, so I went for 
bullseye_motion_4.5.1-1_arm64.deb which seemed to at least approximate to the instructions).

 I tried this.

nick@raspberrypi:~ $ sudo apt-get install libssl-dev libcurl4-openssl-dev libjpeg-dev zlib1g-dev -y

nick@raspberrypi:~ $ sudo wget https://github.com/Motion-Project/motion/releases/download/release-4.5.1/bullseye_motion_4.5.1-1_arm64.deb

nick@raspberrypi:~ $ sudo dpkg -i bullseye_motion_4.5.1-1_arm64.deb

nick@raspberrypi:~ $ systemctl stop motion

nick@raspberrypi:~ $ systemctl disable motion

nick@raspberrypi:~ $ sudo apt-get install python2 python-dev-is-python2 -y

nick@raspberrypi:~ $ sudo curl https://bootstrap.pypa.io/pip/2.7/get-pip.py --output get-pip.py

nick@raspberrypi:~ $ python2 get-pip.py

nick@raspberrypi:~ $ sudo apt-get install libssl-dev libcurl4-openssl-dev libjpeg-dev zlib1g-dev -y

All of which seemed to work fine.

Then I tried.

nick@raspberrypi:~ $ pip2 install motioneye

and it all went wrong.

So I gave up, thinking that life is too short.

Nick P

P.s

nick@raspberrypi:~ $ pip install motioneye also failed with "command not found"...

[StarbaseSSD]

I'm sorry you had that experience.

motion 4.3.2 is the recommended version, as 4.4.x & 4.5.x have had major issues with motionEye.

The pip2 installer should have been run as

sudo python2 get-pip.py

I just ran through the install on a Pi4-4GB Bullseye lite and it all installed correctly. as is.

I am surprised you went out of your way to get the 'latest and greatest' motion, even though it wasn't indicated, but did not complain that you had to install Python 2.7 which EOL'd back in Jan 1 2020... And was on it's way out back in 2014...

[Nick P]

That's OK.

It did complain about the Python 2.7 install, but it did install it anyway.

Oddly. I went back to the motioneyeOS "motioneyeos-raspberrypi4-dev20200606.img.xz" card that I had imaged.

I had read somewhere, not sure where, that someone had some success replacing the fixup4.dat and start4.elf files with those from the latest Raspbian. So I did as well. 

It boots!

And I can log into the web interface.

Just got to get it to recognise my USB webcam now... I may need to go back to the wiki and read the bit about USB cameras.

Nick P.

[David Coe]

I was also able to get a bootable image by replacing those 2 files on  20200606. However now my V2 camera isn't recognized. I tried a new ribbon cable, another camera, pugging it in backwards for giggles. Anyone have an idea?