-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Requirement to explicitly call sh to execute shell script : should be in config description #20
Comments
I'm unable to reproduce this. Need logs. |
I'll create them in the morning after 'unfixing :)' |
octoprint.log |
I just added a shell script to run. I did three things:
This worked OK, I did NOT have to give it a .sh extension (running octoprint ubuntu server, using dietpi) Could it be one of these three things I did was forgotten by @edster99 ? OCTO10 executed the script in /usr/local/bin/light (and switched of the light in my enclosre through homeassistant with nodeRed So.... I cannot confirm a bug. |
my OCTO10 gcode command is /usr/local/bin/co.sh the co.sh file is: |
ive been trying for hours and i cant get it to work. So frustrating |
What were you doing?
Wanted to execute code
Iniital error was a 'returned 127'
resolved by adding absolute path to the shell script /home/pi/OctoPrint/OCTO100.sh (execution properties set to all)
Then got an error 2
resolved by adding sh in the gcode system commands to give sh /home/pi/OctoPrint/OCTO100.sh
This then executed successfully.
Version of OctoPrint-GCodeSystemCommands
1.0.1
Operating System running OctoPrint
Raspbian 10 buster
Octoprint 1.4.0
Octopi 0.17.0
Python 3.7.3
Printer moprodel & used firmware incl. version
Link to octoprint.log with octoprnt.plugins.gcodesystemcommands set to DEBUG
The text was updated successfully, but these errors were encountered: