tasmota-MQTT turn on from Cura?

ERG · December 16, 2019, 11:18pm

Hi,

I am using the tasmota-MQTT plugin. I think it's a great plugin and works great. I just haven't found a way to automatically turn on my printer when I send a print from Cura.

Basically, if the power is off, Cura with the octoprint plugin sees the printer is disconnected. I can't send gcode until the printer is connected and I can't connect until the power supply is on.

Anyone knows of a way I could make Cura turn on the printer?

My pi is always on but I taped the 3.3v pin on the usb cable because the ender board is whiny otherwise.

thanks!

simpat1zq · December 16, 2019, 11:28pm

Do you want Cura to start the print job as well? Because I know for a fact you can send the GCode to OP without a printer connected or powered off.

jneilliii · December 17, 2019, 5:37am

This has been a challenge to all my power plug plugins. I haven't thought of a good approach to accomplish this yet outside of monitoring the file added event in OctoPrint. Cura will give you an option to queue the file if the printer is powered off and the file upload does complete. The problem is any form of start print job after power on would also have to be taken into account. Maybe Print file on startup - Autostart Autoprint plugin might handle that part, but would have to double-check.

ERG · December 17, 2019, 11:50pm

My goal is to send the print, have the printer power on, octoprint connect, start the print, turn off the printer.

ERG · December 17, 2019, 11:53pm

Hi @jneilliii thanks for the plugin!
I'll look into autostart...

I'll have a look at how Cura plugins work. Maybe MQTT for Cura?

jneilliii · December 18, 2019, 4:48am

Sure, we may be able to coerce @fieldOfView to update the cura plugin with power-on support or an optional api call to be a little more universal since there are so many different ones now. He integrated checks for recognizing the UltimakerFormatPlugin being installed and uploads in that format when it is detected.

simpat1zq · December 18, 2019, 7:30am

I could be wrong, but:

They have plugins that look for a GCode command to turn on a plug. You can put that command into your start GCode.
Then do a wait command in your start GCode. I’m assuming that wait commands exist. Not sure though. The wait command is just for the printer to start up.
Is there a setting in OP that allows you to start a print job even if it’s not connected to the printer? I thought I’ve seen that but I can’t get to my OP instance right now.

fieldOfView · December 18, 2019, 8:25am

I've been coerced before... The plugin also supports the PSUControl plugin:

github.com

fieldOfView/Cura-OctoPrintPlugin/blob/285f977d6cd8d07b065709af098dd64859afb2b1/OctoPrintOutputDevice.py#L378




if self._progress_message:
    self._progress_message.hide()
    self._progress_message = None


self._auto_print = parseBool(global_container_stack.getMetaDataEntry("octoprint_auto_print", True))
self._forced_queue = False


use_psu_control = parseBool(global_container_stack.getMetaDataEntry("octoprint_psu_control", False))


if self.activePrinter.state == "offline" and "psucontrol" in self._plugin_data and use_psu_control:
    self._sendCommandToApi("plugin/psucontrol", "turnPSUOn")
    Logger.log("d", "PSU control 'on' command sent")
    self._psucontrol_timer.start()
    return


elif self.activePrinter.state not in ["idle", ""]:
    Logger.log("d", "Tried starting a print, but current state is %s" % self.activePrinter.state)
    if not self._auto_print:
        # Allow queueing the job even if OctoPrint is currently busy if autoprinting is disabled
        self._error_message = None

jneilliii · December 18, 2019, 2:25pm

Yeah the difference between that one and my plugins is that it's possible to control more than one. That's why I was thinking of a generic api call that could be configured rather than hard coding it. It would be more open ended that way for other use cases as well I suppose.

fieldOfView · January 11, 2020, 12:04pm

I am currently working on supporting the "TP-Link Smartplug", "Orvibo S20", "Tuya Smartplug" and "Tasmota" plugins in the Cura-OctoPrintPlugin. Each of these supports multiple plugs/relays; the Cura plugin will let the user select which one to toggle.

Note that the "Tasmota" plugin is not the "TasmotaMQTT" plugin. The latter does not have a "turn on" api command, only a "toggle". Querying the plugin before toggling is not a hoop I am willing to jump through, so I have submitted a PR for the "TasmotaMQTT" plugin to add "turn on" and "turn off" commands so that plugin can be supported too.

jneilliii · January 11, 2020, 2:34pm

Thanks @fieldOfView, I'm reviewing/testing your PR now.

fieldOfView · January 11, 2020, 2:44pm

Ah, good, then at least one of us has tested it

ERG · January 11, 2020, 2:48pm

That's awesome, thanks!

jneilliii · January 11, 2020, 3:06pm

Works like a champ, thanks for the PR @fieldOfView.