[solved]problem with shell-execute rule, shutdown windows pc

---

hy guys!
i have a problem with a rule that uses shell-execute. i want to shutdown a windows pc with a buttondevice. the command for shutting down the pc works without problems from terminal on my raspberry. if i want to execute the script with a rule in pimatic there are some errors.

1. error [pimatic-shell-execute]: [ShellActionHandler] Error: Command execution failed with exit code 1 (Error: Command failed: sudo: /home/pi/shutdown_pc.sh: Kommando nicht gefunden)
2. error [pimatic]: rule pc-ausschalten error executing an action: undefined
3. error [pimatic]: Error on evaluation of rule condition of rule pc-ausschalten: undefined

i will show you my scripts and lines and hope you can help me

the shutdown script shutdown_pc.sh

#!/bin/bash
sudo net rpc shutdown -f -I 192.168.0.20 -U kev%1234

the device in pimatic

 {
      "id": "PC",
      "name": "PC ausschalten",
      "class": "ButtonsDevice",
      "buttons": [
        {
          "id": "ausschalten",
          "text": "ausschalten"
        }
      ]
    },

the rule to execute the script

{
      "id": "pc-ausschalten",
      "name": "PC ausschalten",
      "rule": "if ausschalten is pressed then execute \"sudo /home/pi/shutdown_pc.sh\"",
      "active": true,
      "logging": true
    },

thanks for help!

you should not need sudo in the script or in the shell execute button as pimatic runs as root

it makes sense to check if the environment in which pimatic will run has the right path setup so that every binary referenced is available, best might be to use absolute paths for the binarys which you can find out with the “which” commoand.

which net

hm okay…
which net shows me "/usr/bin/net"
pimatic is under "/home/pi/pimatic-app/"
and the script under “/home/pi/shutdown_pc.sh”

and what now? what is the correct rule? i dont know what should i do with the path information from above.

#!/bin/bash
/usr/bin/net rpc shutdown -f -I 192.168.0.20 -U kev%1234

    {
      "id": "pc-ausschalten",
      "name": "PC ausschalten",
      "rule": "if ausschalten is pressed then execute \"/home/pi/shutdown_pc.sh\"",
      "active": true,
      "logging": true
    },

could work

you maybe need to also add sh in front of the script file or make it executable chmod +x /home/pi/shutdown_pc.sh

yeah, thx! works great!

@thex said in [solved]problem with shell-execute rule, shutdown windows pc:

/usr/bin/

Strange, however, as “/usr/bin/” is part of the default profile settings on Raspbian. I have just double-checked this using a ShellSensor. @garnett Did you change the profile for user root?

@mwittig no, nothing has been changed at the profile settings

Hi there,
under pimatic 0.9.52 (jessy) I shut down my windows PC with rpc via pimatic. Now I have all updated to 0.9.54 (buster) and node 10, since then the shutdown has not been possible.
Have already tried a little, the problem at the moment is that I do not use a user password (before it worked). See log.

pi@raspberrypi:~ $ net rpc shutdown -f -I 192.168.178.22 -U qwert%
Could not connect to server 192.168.178.22
The username or password was not correct.
Connection failed: NT_STATUS_LOGON_FAILURE
Could not connect to server 192.168.178.22
The username or password was not correct.
Connection failed: NT_STATUS_LOGON_FAILURE

If I set a password it goes immediately
However, does not want to set a password, does not want to add an extra user to shutdown. does anyone have an idea why it used to be and not now?

@wuschel Just a wild guess: Did you try without the trailing ‘%’ sign? It should not make any difference, however, the Samba documentation defines the command option as [-U username[%password]]

yes i tested without% comes a query, i acknowledge this comes the same error.

pi@raspberrypi:~ $ net rpc shutdown -f -I 192.168.178.22 -U qwert
Enter qwert’s password:
Could not connect to server 192.168.178.22
The username or password was not correct.
Connection failed: NT_STATUS_LOGON_FAILURE
Could not connect to server 192.168.178.22
The username or password was not correct.
Connection failed: NT_STATUS_LOGON_FAILURE

does anyone have an idea or a tip?