Read the statement by Michael Teeuw here.
weird problem with mm and motion(noob inside)
-
i cant understand it either thats why i need help :).I test the whole thing now that i have some spare time (kids sleeping).I killed pm2,cleardump it and closed the daemon just to get it out of the way.I start Motion daemon and works normally streaming my cam.Then i ~cd /MagicMirror and npm start to open my mirror , and i get this which is my camera.I quit that,stop Motion by sudo service motion stop and then i restart my mirror (~cd /MagicMirror and npm start) and my mirror starts normally. So…if Motion is running i cant start MM.If i stop Motion I can start MM and then start Motion and all ok.I cant understand it.I think i have to find a way to first start MM wait a few seconds and then start Motion.
-
@costascontis well. Motion is streaming on port 8080, and mm wants to use same port, but can’t.
Change the motion config to use a different port, or don’t stream
-
nope my motion streams at 8081.
-
Well it’s coming out on mm, which is using 8080 normally
-
i changed the motion ‘Stream_port’ to 8181 but its still coming out on mm
edit: but motion’s webcontrol port was at 8080 so i changed it and now its ok .Thnx for the idea mate .
-
@costascontis said in weird problem with mm and motion(noob inside):
i changed the motion ‘Stream_port’ to 8181 but its still coming out on mm
edit: but motion’s webcontrol port was at 8080 so i changed it and now its ok .Thnx for the idea mate .
I am just chiming in to confirm that I had the same issue and to provide a clear resolution for future reference.
The problem was that Motion was creating a webcontrol element on the same port as Magic Mirror. This resulted in a black screen (the motion HTML file) showing the camera top of my monitor display instead of Magic Mirror.
To fix this, edit /etc/motion/motion.conf and change the 8080 port entry to something else, like 8181.
-
@phario or 0 to disable that function in motion
