Option to add cameras now gone has this happened to anyone?

Mike Johnson

unread,

Nov 28, 2021, 10:34:48 AM11/28/21

to motioneye

Hi gang,

I was wondering if anyone else ran into this snag.

I've got motion eye set up on 6 pi zero w's as well as a hub (which is a raspberry Pi 4 4g) which i keep in the house. I use the hub as a central location to access all the camera at the house. The 6 pi zero w cameras are all set at "fast network cam" .

Everything was working smoothly, I was able to add cameras with no problem.

Then all of a sudden yesterday I go to add another camera and the option to "ADD Cameras" is no longer avail on my hub.

I thought maybe it was a limit thing since I already had 6 attached.

So I deleted one of the cameras that was already attached to the hub and now I can't bring it back in either.

(See attached grab of what i'm seeing. )

What is also super weird is that on my remote cameras I can't add and additional cameras to them either.

Any thoughts? Has anyone experienced this? is there a fix?

Screen Shot 2021-11-28 at 10.31.06 AM.png

StarbaseSSD

unread,

Nov 28, 2021, 10:40:22 AM11/28/21

to motioneye

motionEye or motionEyeOS?

Looks like you are logged in as User, not Admin.

Mike Johnson

unread,

Nov 28, 2021, 2:52:08 PM11/28/21

to motioneye

Im logged in as an admin for sure on motionEye

Mike Johnson

unread,

Nov 28, 2021, 2:54:03 PM11/28/21

to motioneye

here is another grab

On Sunday, November 28, 2021 at 10:40:22 AM UTC-5 StarbaseSSD wrote:

Screen Shot 2021-11-28 at 2.52.46 PM.png

StarbaseSSD

unread,

Nov 28, 2021, 2:56:11 PM11/28/21

to motioneye

Then something got corrupted, possibly motioneye.conf, or motion.conf, or, doubtful but possible, one of the python modules.

StarbaseSSD

unread,

Nov 28, 2021, 2:58:17 PM11/28/21

to motioneye

If you were to change any of the PiZeros from Fast Network Camera back to normal, you should be able to add other cameras to it, but you'd quickly overload it. FNC removes all the other options other than streaming.

StarbaseSSD

unread,

Nov 28, 2021, 3:01:00 PM11/28/21

to motioneye

Also, on any Pi4 you want to use dev20201026, not 20200606. There are a lot of issues with 0606 that don't show up in the dev version.

Mike Johnson

unread,

Nov 28, 2021, 7:27:49 PM11/28/21

to motioneye

Pi 4 now on dev20201026 and it worked i can now add cameras, however my Pi Zero cameras are on 20200606 and now the pi 4 isn't recognizing them as supported cameras...does that mean all of them should be on dev20201026?

StarbaseSSD

unread,

Nov 28, 2021, 8:01:44 PM11/28/21

to motioneye

It helps.

Mike Johnson

unread,

Nov 30, 2021, 4:51:16 PM11/30/21

to motioneye

So I got around to attempting my Pi Zero 2W to dev20201026. after several attempts of getting the color screen. I tried the zero version (didn't work) tried the Raspberry pi 2 version (didn't work) the tried the Raspberry pi 3 img on my Pi Zero 2W and it booted but it goes into a panic boot mode and not sure what to do as none of the other img files work.

see attached. (any thoughts)

20211130_104803 attached.jpeg

StarbaseSSD

unread,

Nov 30, 2021, 5:37:13 PM11/30/21

to motioneye

@jawsper (contributor) has an image for the PiZero2W at https://github.com/jawsper/motioneyeos/releases/tag/20211113 that seems to work, but is not part of the 'official' releases yet.

Each image is very chipset specific. The closest an official image comes is dev20201026 for the Pi3, but it has the wrong wireless chip. There are a bunch of hoops you can try and jump through (os.conf, set networkless to true, to bypass the no network panic reboots. then copy the dtbo's and blobs for the ZeroW2 to it).

You can use the Bullseye Lite and install instructions from the motionEye wiki, but the CSI (ribbon cameras) are broken in Bullseye with the older software packages like motionEye.

Reply all

Reply to author

Forward