Troubleshooting

Known Issues

• The power indicator is out of sync with the power supply state.

  There are a handful of factors that play into this when using Internal Sensing.
  Use GPIO or System Command Sensing for the best experience.

• Not installing / working on Raspberry Pi 64-bit distributions

  RPi.GPIO currently(04/05/21) does not support 64-bit installations and will fail during install.

• GPIO Sensing not working right and octoprint.plugins.psucontrol - ERROR - [Errno None] Line bias configuration not supported by Kernel version x.xx appears in the log file.

> Linux Kernel version 5.5 or greater is required for internal pull up/down support. Upgrade to Kernel 5.5+ or use [PSUControl-RPiGPIO](https://github.com/kantlivelong/OctoPrint-PSUControl-RPiGPIO) if on a Raspberry Pi.

• GPIO Switching and Sensing using the same pin number does not work.

  Currently there is no way to treat an output as an input. This worked in previous version (<1.0.0) of PSU Control due to a bug which overwrote a sense pin as a switching pin. Support may be added at a later date but until then you can either use Internal sensing or use PSUControl-RPiGPIO if on a Raspberry Pi.

• OSError: [Errno 16] Device or resource busy / Exception while setting up GPIO pin

  Ensure that the configured device/pin are not already in use. You can confirm this by running gpioinfo gpiochip# - See #188

How To Provide Logs

Logs are a critical part of solving bugs. Below are the steps for gathering and providing useful logs.

1. In OctoPrint, go to Settings -> Logging -> Logging Levels.
2. Ensure that octoprint.plugins.psucontrol is listed and set to DEBUG. If you are using a sub-plugin for Switching or Sensing be sure to enable DEBUG logging for that as well. Sub-plugins are generally prefixed with octoprint.plugins.psucontrol ( Example: octoprint.plugins.psucontrol_rpigpio ). If you are not using any sub-plugins but have them installed be sure that they are disabled or uninstalled.
3. Serial logging may also be helpful depending on the issue. You may skip this step if desired but be ready to provide this starting from step 1 should it be requested.
   To enable go to Settings -> Serial Connection -> Serial Logging. From there you can check Log communication to serial.log.
4. Restart OctoPrint
5. Note the time and reproduce the issue.
6. Go to Settings -> Logging.
7. Download octoprint.log and depending on step 3 download serial.log
8. Review the log for any helpful information that might solve the issue.
9. Attach the log files to the ticket and provide as much information as possible including the times noted and anything helpful you found when reveiwing the logs.