Multiple installations and VM operation

[macdr...@gmail.com]

Is it ok to have two different machines running motioneye?

Is running motioneye on a virtual machine a viable option?

Can both access the same cameras?

[StarbaseSSD]

Yes, at times I have 3, one iron, 2 VMs. Testing I might have 4-5 machines running, the one iron, the rest VMs or Pis.

Yes, I test all the alternate OSs on VMs. I have a 14TB NAS I use for storage so no issues for space, YMMV.

Absolutely, if the cameras allow multiple connections concurrently. I share the USB cameras from the iron machine too, with no issues.

Good questions.

[StarbaseSSD]

Oh, and BTW, the PIs might be running motionEye on Raspbian, or motionEyeOS, they play nice together too.

[StarbaseSSD]

One other note:

if set up correctly with multiple motionEyes, one can be a master and the others slaves, to manage all the cameras from a single instance, even if local detection and recording is not used.

[macdr...@gmail.com]

Ok, thanks.

[macdr...@gmail.com]

Got around to adding a camera to the newly created Debian 11 install which is on a VM.

It apparently finds the camera, but I just get a grey rectangle.

I can ping the camera from the VM terminal window.

On my other install, which is on it's own PC, same camera works fine.

[StarbaseSSD]

what camera is it? does it support multiple connections?

what options did you pick when picking the camera?

what do you have selected for resolution and frame rate? is it the same as the iron install?

[StarbaseSSD]

Also, can you connect to the iron machine (ip address:8081 if only camera) and remote motioneye camera type?

[macdr...@gmail.com]

It is a hardwired Foscam GJ4.

I selected the same as the iron. network camera, rtsp, same resolution and FR.

The iron has two cameras, connection to 8081 says connection refused.

[StarbaseSSD]

Using the correct username (admin) and password for admin?

On the iron machine, do you have streaming enabled for that camera?

If it is, it shows three links, on is streaming. click on it and paste into new camera on the other.

For example one of mine is 

http://192.168.2.19:8081

and I can paste that into another motioneye as a simple mjpeg camera and it works.

[macdr...@gmail.com]

I can set up the VM to stream the camera from the iron motioneye.

I tried to connect with the camera (rtsp) with the iron shutdown, it finds the camera (at least I assume it wouldn't create the camera if it didn't), but just gets a grey screen (as noted earlier).

[StarbaseSSD]

I would copy the /etc/motioneye/camera-1.conf file from the working machine to the vm to test.

[macdr...@gmail.com]

I copied the working conf file to the VM. It works.

The diff of the files is below. The left the working, the right not working.

It appears I didn't provide a password...when I created the camera on the VM.

Is this the issue? (Embarrassing.)

[StarbaseSSD]

It very well could have been. Glad it's working.

[macdr...@gmail.com]

Now I need to find the password... :(

[StarbaseSSD]

password for what?

[macdr...@gmail.com]

The camera, in the last post the image shows a password line in the conf file for the working camera.

[StarbaseSSD]

Well, theoretically, username for the camera is dcam and the password is dcamm+c (at least on my setups)

[macdr...@gmail.com]

Ah...I was reading the .conf file and thinking that was something it wasn't.

[StarbaseSSD]

Were you able to get the stream from the iron?

[macdr...@gmail.com]

Yeah, it wasn't working. I suspect it was because my dhcp server had rebooted, the rest of the irn on my net seemed to be fine.

In my flailing to get the streaming camera working, I realized after I posted that, I had selected the wrong type of camera.

So, I deleted the post.

All good now.