fmalekpour / octoprint-gpioshutdown Goto Github PK

There is a typo (well 2 actually) in the template file GPIOShutdown_settings.jinja2 which disable the use of GPIO 4
<option value="4>GPIO 4</option>
Should be
<option value="4">GPIO 4</option>

(the current version is missing a quote in both GPIO 4 options)

More of a question than a bug report, I think. Have two printers with OctoPrint running on Pi 4s. Installed GPIO Shutdown on the first one yesterday and everything went as advertised. This morning I installed it on the 2nd printer but can't seem to make it work. It is grayed out in plug in manager and will not turn on.
Both printers and OctoPrint installations are pretty much identical, any ideas?

I am using the Octoprint Shutdown to trigger a timer to turn off my power supply (which supplies the Pi). Right now, the timer is set for 15 seconds, which is adequate time for the Pi to fully shut down. I have a shell script that turns on Pi pin 27, which triggers the timer, and then shuts down the Pi and printer power supply. It works fine when I shut down Octoprint using the Octoprint shutdown.

Unfortunately, when I use this plugin and the push button to shut down Octoprint, the author has hard-coded the shutdown command within the plugin. This makes it impossible to activate the shell script.

A useful modification to this plugin would be to have the shutdown command as an input variable in the setup screen like Octoprint has. Alternatively, if there was some way to get access to the python code in the Pi, I could change the variable to my shell script.

Does anyone have any ideas? I don't know Python very well, and I don't know if it worth forking off from the plug-in and making the modifications, or having the author do it. If he did, I would buy him two beers.

Steve

I am unsure about how the debounce stabilization delay works. I changed it to 2000 ms but there doesn't seem to be any change in operation. I expected it to mean that the button needs to be held down and the GPIO signal to be 'stable' for at least 2000 milliseconds as confirmation before it begins the shutdown. But that isn't the behavior I see: I quickly press and release the button and it shuts down anyway. I have also implemented a 1k ohm pull up resistor on the GPIO pin to 3V3 to be more resilient to noise.

Or is it waiting 2000 ms after the button is released? If so I don't understand why it is needed. Generally you put in debounce on both the press and the release of the button to eliminate 'multi-press' glitches when counting button presses.

Hi
would it be possible to add a check mark to support shutdown while printing.
I am using your plugin with a touch button to turn off my homemade Sisyphus table.
Best regards Jubaz

Is it possible to get an option for a second button to restart the pi?

Plugin installed, for the 1st time, no errors, after reloading the UI there is NOT setup/UI in the settings, just an empty page, like this:

Thank you :-)!

Is the LED turned off stated reliable, i.e., when it's off, it's ok to power off the RPi?

I noticed that the LED turns off immediately and takes around 1 second before the "Server is Offline" Octoprint message is displayed.

This seems a little overkill code-wise, when the same thing can be achieved by adding dtoverlay=gpio-shutdown (defaults to placing a switch between gpio3/pin5 and GND/pin6) and dtparam=pwr_led_gpio=27 to your /boot/config.txt... Am I missing something?

I select the number pin ( bcp expected)

but it select the physical number

example: GPIO 23 is Gpio 11

Hi, I'm new to your plugin and I'm happy to use it.

I want to know why gpio3 isn't available in the drop down? GPIO3 is the logical pin to use as a shut down button as it's also the pin which powers the pi on. Making the button an on/off button by virtue.

A side now I can't get the led to work for some reason. Seems straight forward enough. Nothing in the logs.

Ideally the shutdown should not be processed while the printer is actually printing.

on starup of octopu the LED goes on for a moment then off. is there a dependency on octopu fully loading OK? My camera isnt configured properly - does that affect this plugin

Probably an obvious question, but I just wanted to confirm. The switch should be momentary on?

Hi,

would it be a lot of work to add a second "LED" which turns on when a print started and off when the print finishes?

I like to use it to turn additional lightning on for the camera and also a green "printing" sign.

Regards
Ringo

I have the switch that is configured to GPIO18, and I have tested that it is grounding on make. but there is no other action. Where are the logs to be found please?

When I installed Octolight, a simple on/off switch plugin for an LED strip, GPIO Shutdown using different GPIO pins stopped working. It would be great to have both working at the same time. Any idea how to fix this?

Hi,
I have used the plugin "GPIO Shutdown" for a while, it did run well. Thanks alot for this useful plugin.
Used Pins: Shutdown GPIO17, LED=GPIO27.

Now I have activated in addition the Octoprint Plugin LED Strip Control.
Used Pins: Red Pin=16=GPIO23, White Pin = 12 = GPIO18. Green and blue pins=0, unused.

If I have both plugins activated, LED Strip Control works, GPIO Shutdown neither lits the LED nor shuts down when triggered with a "0" at the Shutdown pin.

I do not know which of the two plugins need a code correction.

It would be nice if the problem could be solved.
Of course, I will run tests if necessary.
If you suspect the error on the other side, I can add the issue there.

Greetings,
mcmusic2

Would you please clarify if a pull up resistor is required when wiring the momentary ON switch? The GPIO pins have software configurable pull ups but you don't mention if these are activated or not. I tried the code tonight on my Pi 3B+ and found the shutdown pin to be very sensitive to touch suggesting the pull up is not configured or it is very weakly pulled up internally. I do not want to activate a shutdown pin if a casual touch of the switch will shut it down--especially in the middle of a print.