mirror of
https://github.com/motioneye-project/motioneye.git
synced 2026-03-02 22:57:06 -05:00
Motioneye can't connect to raspberry pi motion camera #207
Labels
No labels
Android app
Arch Linux
CI/CD
CSS
FreeBSD
HTML/HTTP
Home Assistant addon
JavaScript
Python
Raspberry Pi
Stale No Activity 60 Days
bug
code format
dependencies
dev branch
docker
documentation
duplicate
enhancement
feature
help wanted
i18n/l10n
invalid
legacy motionEye
meta
motion
motionEyeOS
notourproblem
python update
question
question
security
troubleshooting
wontfix
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/motioneye#207
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jcherndon on GitHub (Jun 11, 2016).
I have a raspberry pi with motion (3.2.12+git20140228) installed (via apt-get) and can verify works by going to ports 8080 and 8081.
I have motioneye 0.31.5 running on a centos7 box.
When I try to connect from motioneye to the raspberry pi i get a "not valid" error in the gui and a log of
ERROR: failed to list remote cameras on http://192.168.2.7:8080: Not Valid
DEBUG: 200 GET /config/list/?_=1465662158611&scheme=http&host=192.168.2.7&port=8080&path=%2F&username=admin&password=&proto=motioneye&_username=admin&_signature=3a86ea4e4749cea1353f44a95288ecaf22217711 (192.168.2.184) 20.80ms
Ideas?
@Oxize commented on GitHub (Jun 12, 2016):
Did you select local camera and then the camera which is connected to the RPI?
@ccrisan commented on GitHub (Jun 12, 2016):
It looks like you're trying to add a remote motionEye camera but you provided the URL to a MJPEG stream. You'll probably want to specify port 80 (or none) instead of 8080.
@jcherndon commented on GitHub (Jun 12, 2016):
But the motion software on the pi is listening on 8080 and 8081 (verified with netstat).
Maybe I don't have a library installed on the pis? I was able to connect a pi installed with the motioneyeos to my motioneye (centos7) box.
I haven't done much with the motion.conf on the pis, just enabled remote admin and deamon processing.
@jcherndon commented on GitHub (Jun 12, 2016):
Do I need motioneye running on pis along with motion in order to connect with a different motioneye server?
@jcherndon commented on GitHub (Jun 12, 2016):
new to github, don't know why I closed this.
@ccrisan commented on GitHub (Jun 12, 2016):
I thought you were running motionEye on your PI as well. If you only run motion on your PI, then add the camera as a network camera (as opposed to Remote motionEye Camera).
@jcherndon commented on GitHub (Jun 12, 2016):
ok, that worked. Will I be able to control the motion (pi) though the motioneye (centos), i.e. change parameters and such?
@ccrisan commented on GitHub (Jun 12, 2016):
Nope.
@jcherndon commented on GitHub (Jun 12, 2016):
so then If I was to change motion parameters I'll need to install motioneye on the pis as well? Or is that something that doesn't get done?
@Oxize commented on GitHub (Jun 12, 2016):
Why dont you just access (motionEye) the PI from any box webbased (either its windows, linux) Why you want within Centos from Motion to MotionEye PI? I guess you have the camera connected on your PI?
@ccrisan commented on GitHub (Jun 12, 2016):
@jcherndon I thought that was obvious :)
@jcherndon commented on GitHub (Jun 12, 2016):
So maybe it'll help if I mentioned what I want to do.
I have 1 box that is accessible from the internet, the centos box.
I want to see all my pis videos through that one interface, motioneye.
I thought I could have the one motioneye centos that had multiple motion pis video streams on it.
I though that through the centos motioneye I could alter settings on the moiton pis if I wanted to.
@jcherndon commented on GitHub (Jun 12, 2016):
OK, I got things working though I'm not sure how correct it is. What would be the correct layout for what I mentioned above. 1 server hosting a web page for multiple pi cameras?
@ccrisan commented on GitHub (Jun 12, 2016):
@jcherndon just install motionEyeOS or motionEye + Raspbian on your PIs and use your existing central motionEye from the centox box to control them.
@jcherndon commented on GitHub (Jun 12, 2016):
okie doke, I'll close this, thanks!
@DonGrego617 commented on GitHub (May 26, 2017):
Hi,
Love the app. Fabulous. But, I'm having a problem connecting MotionEye on Pi #1 to the Camera on MotionEye on Pi #2 on my local network. I try to add remote motioneye camera on PI #2, I enter the "http://192.168.1.22" address, leave the password "admin", leave the password blank (i have no password on my MotionEye on Pi #2...) but the error I receive is: Failed to cennect to 192.168.1.22 port 80: Connection refused.
I have a standard, out-of-the box Noobs installation of Raspian, with SSH running. That's it. There is nothing else I did to this box (ie: no other services, servers, firewall changes, etc.) Is there something where I have to open the port? Thanks in advance!!!
