[DSF Extension] Exec On MCode (was: Shutdown SBC)

wilriker

@oozebot I think that primarily this depends on when execonmcode is started relative to startup of DCS. Or maybe DCS will even delay accepting API clients until a certain amount of startup tasks have been processed. @chrishamm should be able to give more insights on that.

chrishamm

@wilriker If ExecOnMCode is installed as a DSF plugin (will be officially supported in 3.3), it's started by DuetPluginService which is started by multi-user.target. Note that v3.3 will introduce /sys/dsf-config.g as well which is executed as soon as all the enabled plugins have been started.

Previously plugins were started by DCS, so by basic.target AFAIR.

@oozeBot Either move your custom codes to dsf-config.g if you're on pre-3.3 and/or add a delay to the end of your config file to make sure ExecOnMCode has been fully started before they're executed.

oozeBot

@chrishamm @wilriker - thank you both. We are just about to begin testing the 3.3 betas. This may need to be postponed until after it is released.

wilriker

@chrishamm As of right now ExecOnMCode is a simple API client just connecting to the socket. It is not yet converted to an official plugin. It will be started by a user-provided systemd unit (or arbitrary other means) completely independent of DCS.

CrazyCreator

@wilriker
I once wrote you a PM in German. because I don't know if you understand what I am writing via google translator

@All
I would like to send an http command using the Mxxxx command.

Let's assume I've installed everything as shown in the video linked here.

What do I have to enter where and how around this line:

http://IP.Adrresse.Of.Shelly/relay/0?turn=off

to be able to send?

P.S or edit or next step
i installed the ExecOnMCode with help of the two videos. but the shutdown (poweroff) with M7722 don't work for me.
The Service is running:
Bildschirmfoto 2021-05-18 um 22.03.40.png

but in DWC i see this message:
M7722
Warning: M7722: Command is not supported

And the Raspi is still working/running.

On Terminal (connected with Raspi) i see:
pi@CCC:~ $
2021/05/18 22:24:53 Connection to DCS closed
2021/05/18 22:24:53 EOF
pi@CCC:~ $

wilriker

@crazycreator So, if you want to make a simple HTTP/GET call I'd say you need a cURL or wget command:

execonmcode -mCode 1234 -command 'wget -O /dev/null "http://IP.Adrresse.Of.Shelly/relay/0?turn=off"'

If you want to put that into the ExecStart line of a systemd unit you have to deal with systemd's escaping syntax. That will be a bit ugly but doable. Otherwise you could move the wget call into a simple bash-script and call that - one for on and one for off.

CrazyCreator

Ok .. sounds good.

But actually the script is not running correct ... the error popup on web-gui is the only reaction when I send M7722. The Raspi don't shut down or restart after this M7722 command.

the terminal show what you see on my terminal screen in my last posting

pi@CCC:/usr/local/bin $ sudo ./execonmcode -mCode 7722 -command "poweroff"
2021/05/19 20:47:59 Connection to DCS closed
2021/05/19 20:47:59 EOF

I think that's the problem. But i have no idea how to fix this.
I did the installation exactly as shown in the video.

CrazyCreator

nobody answer me?

when i try the command in terminal, connected with the Pi, with additional parameter
i see this output

pi@CCC:~ $ sudo /usr/local/bin/execonmcode -mCode 7722 -command poweroff -debug -trace
2021/05/20 15:54:21 7722: poweroff 
2021/05/20 15:54:21 [DEBUG] <Recv> {"version":11,"id":20}
2021/05/20 15:54:21 [DEBUG] <Send> {"Mode":"Intercept","Version":7,"InterceptionMode":"Pre"}
2021/05/20 15:54:21 [DEBUG] <Recv> {"success":true}
2021/05/20 15:54:21 [DEBUG] <Connect> Connection established

but the Pi don't reboot or shut down ... no reaction
on dwc the same ... no reaction

wilriker

@crazycreator Can you check if the command poweroff does work on your system in the first place?

Also please check execonmcode version (parameter -version). It looks to me as if you are using an older version.

CrazyCreator

@wilriker said in [DSF Extension] Exec On MCode (was: Shutdown SBC):

Can you check if the command poweroff does work on your system in the first place?

How can i do this?

@wilriker said in [DSF Extension] Exec On MCode (was: Shutdown SBC):

Also please check execonmcode version (parameter -version). It looks to me as if you are using an older version.

pi@CCC:~ $ sudo /usr/local/bin/execonmcode -version
2021/05/20 16:20:43 0x24142bc
pi@CCC:~ $

wilriker

@crazycreator said in [DSF Extension] Exec On MCode (was: Shutdown SBC):

How can i do this?

Run sudo poweroff and check what that does.

pi@CCC:~ $ sudo /usr/local/bin/execonmcode -version
2021/05/20 16:20:43 0x24142bc
pi@CCC:~ $

That looks like a bug in previous version and it may be that DCS is rejecting this client. Please get the version 5.2.0 of execonmcode from GitHub and try again.

CrazyCreator

@wilriker I used 5.1 so that I could imitate the tutorial 100%. now I'm back on 5.2

sudo poweroff

pi@CCC:~ $ sudo poweroff
Connection to ccc.local closed by remote host.
Connection to ccc.local closed.

Versionscheck

pi@CCC:~ $ sudo /usr/local/bin/execonmcode --version
5.2.0

Debug and Trace

pi@CCC:~ $ sudo /usr/local/bin/execonmcode -mCode 7722 -command -poweroff -debug -trace
2021/05/20 16:35:27 7722: -poweroff 
2021/05/20 16:35:27 [DEBUG] <Recv> {"version":11,"id":21}
2021/05/20 16:35:27 [DEBUG] <Send> {"Mode":"Intercept","Version":10,"InterceptionMode":"Pre","Channels":["HTTP","Telnet","File","USB","Aux","Trigger","Queue","LCD","SBC","Daemon","Aux2","AutoPause","Unknown"],"Filters":["M7722"],"PriorityCodes":false}
2021/05/20 16:35:27 [DEBUG] <Recv> {"success":true}
2021/05/20 16:35:27 [DEBUG] <Connect> Connection established

put the M7722 command in DWC Console ... show me this in terminal

2021/05/20 16:35:58 Connection to DCS closed
2021/05/20 16:35:58 [DEBUG] <Close> Closing connection
2021/05/20 16:35:58 EOF

wilriker

@crazycreator said in [DSF Extension] Exec On MCode (was: Shutdown SBC):

pi@CCC:~ $ sudo /usr/local/bin/execonmcode -mCode 7722 -command -poweroff -debug -trace

At least this time you used -poweroff which most likely is not a valid command.

CrazyCreator

@wilriker
but in shutdownsbc.service is used and in the video tutorial too.

What should I write / use that instead?

What else can I try to get the script to work?

wilriker

@crazycreator Just remove the dash from the start of poweroff then it should work.

CrazyCreator

@wilriker
you mean so:

pi@CCC:~ $ sudo /usr/local/bin/execonmcode -mCode 7722 -command poweroff -debug -trace
2021/05/20 18:47:03 7722: poweroff 
2021/05/20 18:47:03 [DEBUG] <Recv> {"version":11,"id":80}
2021/05/20 18:47:03 [DEBUG] <Send> {"Mode":"Intercept","Version":10,"InterceptionMode":"Pre","Channels":["HTTP","Telnet","File","USB","Aux","Trigger","Queue","LCD","SBC","Daemon","Aux2","AutoPause","Unknown"],"Filters":["M7722"],"PriorityCodes":false}
2021/05/20 18:47:03 [DEBUG] <Recv> {"success":true}
2021/05/20 18:47:03 [DEBUG] <Connect> Connection established

CrazyCreator

@wilriker
When I send M7722 in the DWC Console I get the familiar popup with the message:
M7722
Warning: M7722: Command is not supported

But the Raspberry does not switch off or restarts!

When I send the M7722 command in the DWC console, I see the following lines in the terminal:

2021/05/20 18:47:47 Connection to DCS closed
2021/05/20 18:47:47 [DEBUG] <Close> Closing connection
2021/05/20 18:47:47 EOF

oozeBot

@crazycreator One note that I've found is that when rebooting or powering off the SBC from a custom mCode, DCW will report "Command not supported" as the API immediately shuts down. See this thread:

https://forum.duet3d.com/topic/20968/3-2-final-execonmcode-warning-issue

CrazyCreator

@oozebot
thanks for the hint. I've already read that while looking for a solution to my problem.

if execonmcode would run, then the message would be pretty irrelevant to me;) ... but unfortunately I can't do that

wilriker

@crazycreator TBH I have no idea why it does not work for you. Can you please post the output of

sudo journalctl -eu duetcontrolserver

after you sent M7722 and execonmcode reported EOF?

Also another idea, please try the absolute path to poweroff, i.e. /usr/bin/poweroff.