Read the statement by Michael Teeuw here.
[octomirror-module] Monitor & Control an OctoPrint 3D Printer Server
-
@citizendevpi said in [octomirror-module] Monitor & Control an OctoPrint 3D Printer Server:
url: “http://192.168.2.141”
Looks like link isn’t complete. Should looks like this http://ip_address/webcam/?action=stream{ module: 'MMM-MotionEye', position: 'top_right', config: { width: "460px", autoHide: false, url: "http://octoprint IP address/webcam/?action=stream", debug: false, user: "pi" } },
I hope this will help you
-
Try open octoprint > go to webcam > then open image in new tab. and copy http address from web browser to your config file in octomirror-module.
-
@michael24h said in [octomirror-module] Monitor & Control an OctoPrint 3D Printer Server:
Looks like link isn’t complete. Should looks like this http://ip_address/webcam/?action=stream
Nope, that shouldn’t be it. He said his stream was working and the
url
parameter is just for the octopi instance, not the stream. The module assumes it needs to add/webcam/?action=stream”
unlessstreamUrl
is provided. -
Just confirming: you are using my version https://github.com/shbatm/octomirror-module not the original, correct?
-
@shbatm let me check and yes u are correct I do have my stream no problem but no info and I would only expect it to give me stats when printing
-
@shbatm yes shbatm/octomirror-module
-
This post is deleted! -
Any help
-
@citizendevpi said in [octomirror-module] Monitor & Control an OctoPrint 3D Printer Server:
Any help
Sorry, I haven’t had a chance to fire up my printer and take a look yet. Going to try in the next few days. They’ve probably updated something in Octoprint that broke it.
One thing I did think of to have you check on: make sure you have Allow CORS turned on in your Octoprint settings.
-
@michael24h @citizendevpi Please update the module to the latest version and give it a try.
Short version: OctoPrint changed the way the API login works.
Long version: The new bundled OctoPrint plugin ForceLogin now requires the API to get a session ID and send it back to the socket before it will send any detailed messages. Detailed here and here.