With standard RPi-Cam-Web-Interface installation and using external motion detection settings then the http api supported by motion is used to retrieve the /etc/motion/motion.conf data and display it in the motion.php table. The api is also used to modify values. motionPars.json doesn't come into it.ScheissSchiesser wrote:Can somebody help me figure out why my motionPars.json file is not getting populated with the motion settings? This causes me to be unable to view/change the motion settings via the web interface.
I am having trouble determining which part of the RPi-Cam-Web-Interface code is responsible for doing that. It is probably something in the motion.php file, but I am having trouble understanding it. It might help to debug this problem if I could figure that out.
As it stands now, motionPars.json is an empty file. Bringing up the motion.php page via clicking on the "motion settings" button shows a blank page (no table), presumably because the motionPars.json file contains no data.
Any help/hints would be appreciated.
In /etc/motion/motion.conf there is a section that controls the API called HTTP based control. The installer should set that up to be
This means queries are done on port 6642, only requests from same host are allowed, and responses are in a plain text format.