Can't get motioneye control port web page to work

1,266 views
Skip to first unread message

wally333

unread,
Sep 21, 2017, 1:11:26 PM9/21/17
to motioneye
I've edited /etc/motioneye/motioneye config to make:
motion_control_localhost false

And rebooted.  Still can't connect to the control port page on 7999.

What is the trick?

It works from localhost:7999 but using the chromium on a pizero-W is painful, especially if motioneye is running.

Ultimately I want the pizero-w to be headless.

wally333

unread,
Sep 21, 2017, 7:27:12 PM9/21/17
to motioneye
Seems to be an omission in the documentation, and no apparent way to enable it from the GUI.

To enable the control port you must edit bot /etc/motioneye/motioneye.conf and /etc/motioneye/motion.conf and then reboot.

In  /etc/motioneye/motion.conf  Change  webcontrol_localhost on  To  webcontrol_localhost off

In /etc/motioneye/motioneye.conf Change  motion_control_localhost true  To  motion_control_localhost false 


Now I can pause and restart motion detection with commands from my hard wired alarm system (running on a Beaglebone) based on the alarm enable status with:

wally333

unread,
Oct 3, 2017, 10:11:18 AM10/3/17
to motioneye
I think I can help solve some of the mystery, after having done a few more Motioneye installs.

If you run Motioneye before editing the /etc/motioneye/motioneye.conf to enable non-localhost control you will then have to edit both motioneye.conf and the motion.conf that gets created first time you run Motioneye in order to change form the default.

But if you edit motioneye.conf before ever starting Motioneye the created motion.conf file will reflect your edit.
Reply all
Reply to author
Forward
0 new messages