Adding a netwerk camer results in a green screen (few seconds) followd by a grey screen

[adriaan]

Greetings Once More

When adding a new camera to motioneye on an Ubuntu 20.04 system, the URL specified (in my case http://192.168.2.30:2733) is recognized as an "MJPEG Network camera" but the streaming video does not show in motioneye. Instead of that a few seconds a green screen followed by a grey screen with the text "connection to camera lost"

The streaming camera device works fine when looked at with a browser (http://192.168.2.30:2733 , I did this on more than one computer to double check) so the streaming of video is actually working.

The streaming camera device is a raspberry pi zero W with motioneye os (202006060) and works fine when having a look at that device itself with the URL http://192.168.2.30.

The reason that i would like to connect the raspberry PI as a " MJPEG Network Camera" instead of "Remote Motioneye Camera" is that i would like to execute motion detection and all actions that are triggered by it, on my ubuntu system and not on the PI.

Any thoughts that might help connecting a motioneyeos PI to an Ubuntu motioneye system as a " regular" network camera?

Thanks BTW for all good answers I already received in this forum...

[StarbaseSSD]

Did you turn on Fast Network Camera?

If you did, did you try the http://192.168.2.30 or http://192.168.2.30:8081 URLs?

[adriaan]

Yes i did use the Fast Network Camera option and _that_ works.

However, I have one simple reason to try without the Fast Network Camera option and that is the "Automatic Brightness" that is available when the camera on the PI is configured without the Fast Network Camera option but not available otherwise.

It appears after a few days of running the PI this way the Automatic Brightness option does a rather good job during evening and night etc...

And yes I did try the URL with and without port number.

When configuring a network camera the port number must be included in the URL or motioneye shows the message "not a supported network camera"

When configuring a Remote Motioneye Camera the port number must NOT be includes in the URL as you mentioned before.

Switching to Fast Network Camera is indeed my option to get this system up and running at the cost of not having automatic brightness adjustment.

I recall reading a few articles (a few year ago) about re-configuring motion (not motioneye BTW) for day or night operation based on day of year, time, longitude, latitude and that kind of stuff. that appeared to my as rather complex stuff, would like to avoid that when possible :-)

[StarbaseSSD]

You can find the line and modify or add the line:

auto_brightness on

to

/data/etc/camera-1.conf

to turn it on, and test. Most functionality is available in the config files, even if the WebGUI doesn't offer a toggle button for it.

Can't hurt to try...

[adriaan]

> auto_brightness on

Just done that, reboot and I will have a look this evening and night...

[StarbaseSSD]

[fingers crossed]