Ajout caméra MotionEye RPI zero dans MotionEye Docker

motioneye-project / motioneye

A web frontend for the motion daemon.

GNU General Public License v3.0

3.98k stars 653 forks source link

Ajout caméra MotionEye RPI zero dans MotionEye Docker #2101

Open GBaud opened 3 years ago

GBaud commented 3 years ago

Hello everyone, I have been driving myself crazy for days now: I have been trying in vain to get a remote motioeye camera into the motioneye running in a docker on my QNAP. This camera is installed on a MotionEye running on a RpiZero at the address: 192.168.0.61:8765, the video stream port is 8082. It works very well. In the docker, I can only add a camera if I put the address 192.168.0.61:8765, and set the MotionEye without a password. But even if I do that, the screen where the mage should appear remains empty. I have tried a lot of URLs, but without success.

I don't know what I'm missing... If you have any ideas... I thank you in advance.

starbasessd commented 3 years ago

Do you have multiple motionEye streams on the PiZeroW? If not, then the port you need is 8081, not 8082.

GBaud commented 3 years ago

Thank you for your answer. I tried that too and it didn't change anything unfortunately.

GBaud commented 3 years ago

If it helps, here are my port redirects in the docker that should gather all the streams.

starbasessd commented 3 years ago

AFAIK (As Far As I Know) you can't have duplicate port forwarding in Docker. motionEye is TCP. RTSP cameras can be UDP.

GBaud commented 3 years ago

I just changed the ports, and nothing changes. Still the black square with the search circle that rotates in the middle of the image.

starbasessd commented 3 years ago

Unfortunately. beyond that, I don't know. I can and have used docker for motionEye on PiOS, Ubuntu, Debian, etc, with no issues. I run it for production on a M73 TFF with Ubuntu. I have lots of Pis I can toss a build on for testing, but no NAS (QNAP or other) that supports docker. I haven't had much luck with portainer, of HomeAssisstant, either. I'll leave it here for others to see, maybe some one has experience. Google searching wasn't very helpful.

GBaud commented 3 years ago

Thank you very much for your messages. I came to the same conclusions as you after searching on Google... On Qnap, the client called "container" looks a lot like Portainer indeed. I will try to put motionEye in a VM to see if the problem can come from this form of simulation...

GBaud commented 3 years ago

I come back to this discussion for those who will come across this problem. I tested installing motioneye in a ubuntu VM and it worked right away. So I have two hypotheses:

either there was a port forwarding issue on the docker.
either it's the containerisatoin under Debian that can cause more problems than Ubuntu.

I can't check further than that for the moment. There will surely be other participants much better than me to correct my words.

starbasessd commented 3 years ago

Works fine under Debian, and all it's derivatives like Ubuntu & RaspberryPiOS. The issues come when you use 'portainer', or HomeAssistant wrappers. Somewhat depressing that I can't get it to work there. I have even successfully built it from source with buildroot and thingos.