PSU Control with Octoprint 1.5.0RC - settings don't save

What is the problem?

After installing Octoprint 1.5.0 RC2 (this was the first 1.5.0 RC I tried. I was on 1.4 2 previously) The PSU Control plugin does not save settings. Settings like Switching Method, revert to default after a restart of Octoprint.

Problem exists with 1.5.0 RC3 too

What did you already try to solve it?

Looked through the code but got lost. Not sure where/when settings are stored/retrieved

Have you tried running in safe mode and if so did it solve the issue?

No

Complete Logs

octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support! Not log excerpts, complete logs.)

octoprint.log (2.0 MB) serial.log (148 Bytes)

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

Octoprint 1.5.0 RC3
Octopi Version 0.18.0, running on Raspberry Pi 4 Model B Rev 1.4

SYSTEM INFO
browser.user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36 Edg/86.0.622.69
connectivity.connection_check: 8.8.8.8:53
connectivity.connection_ok: true
connectivity.enabled: true
connectivity.online: true
connectivity.resolution_check: octoprint.org
connectivity.resolution_ok: true
env.hardware.cores: 4
env.hardware.freq: 1500
env.hardware.ram: 8140840960
env.os.bits: 64
env.os.id: linux
env.os.platform: linux
env.plugins.pi_support.model: Raspberry Pi 4 Model B Rev 1.4
env.plugins.pi_support.octopi_version: 0.18.0
env.plugins.pi_support.throttle_state: 0x0
env.python.pip: 20.2.4
env.python.version: 3.7.3
env.python.virtualenv: true
octoprint.safe_mode: false
octoprint.version: 1.5.0rc3

I've pinged @kantlivelong about this, but real life is currently taking precedence on his part. Maybe I'll find time to look into it from my end. So far have not seen another report on this though. Btw, please always give feedback like this in the feedback ticket, that's what it's there for. Or better yet, do that and open a bug report. This almost got missed because I'm pretty focused on the feedback ticket during RC phases and have less time to monitor the forums.

Hi,
I am also having this issue since upgrading to OctoPrint 1.5.0
PSU Control loses setting as soon as OctoPrint is restarted.

browser.user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.67 Safari/537.36 Edg/87.0.664.47
connectivity.connection_check: 8.8.8.8:53
connectivity.connection_ok: true
connectivity.enabled: true
connectivity.online: true
connectivity.resolution_check: octoprint.org
connectivity.resolution_ok: true
env.hardware.cores: 4
env.hardware.freq: 1500
env.hardware.ram: 4041732096
env.os.bits: 32
env.os.id: linux
env.os.platform: linux
env.plugins.pi_support.model: Raspberry Pi 4 Model B Rev 1.2
env.plugins.pi_support.octopi_version: 0.17.0
env.plugins.pi_support.throttle_state: 0x0
env.python.pip: 20.3
env.python.version: 3.7.3
env.python.virtualenv: true
octoprint.safe_mode: false
octoprint.version: 1.5.0

Can you please share your logs as well?

Absolutely...
octoprint.zip (187.9 KB)

Anything that will help. :slight_smile:
If you need anything else, please let me know.

Appreciate your time.

You should enable the serial logging.

I didn't know it needed to be enabled, I will do so, then send that log.

Same issue here after the update.

Also, i'm confused why the Plugin's GitHub Repo has an issue template, but the issues feature is disabled… almost makes the repo feel kinda dead…

Here is my serial.logserial.log (182.9 KB)

So I've poked at both log files and in both cases other plugins are enabled. Can we start by disabling all other 3rd party plugins and then recapture fresh debug logs?

So far I'm unable to reproduce on a fresh install of 1.5.0 w/ Python 3.6.

Also to touch on the repo issue tracker... I usually will enable it around releases but won't keep it on. I get way too many reports (for my taste anyway) which turn out to be user error, asking for help. :slight_smile:

Was actually able to reproduce it on my printer just now. Poking at it now...