@andritolion had a great suggestion for adding the ability to suppress M300 commands so that they could use a GPIO passive buzzer instead of the active buzzer built into their printer. I added a setting for this, but did not tie it to the enablement of a hardware buzzer (GPIO) so that, in theory, you could also just disable the handling of M300 commands on your printer altogether.
I also noticed a bug when settings are saved, options get updated to the old settings instead of the new changes. This has been mitigated, making it easier (less confusing?) to test the M300 suppression changes.
[x] verified settings now apply properly when saved. E.g. when disabling or enabling the software buzzer, it takes effect immediately after saving the settings
[x] verified that when the new "Suppress M300 command passthrough" option is checked, no M300 commands show as sent in the octoprint console, but the software buzzer still handles and plays the tones
[x] verified that when the new "Suppress M300 command passthrough" option is unchecked, M300 commands show as sent in the octoprint console (forwarded on to the printer as they were previously), and the software buzzer handles and plays the tones
Description
@andritolion had a great suggestion for adding the ability to suppress M300 commands so that they could use a GPIO passive buzzer instead of the active buzzer built into their printer. I added a setting for this, but did not tie it to the enablement of a hardware buzzer (GPIO) so that, in theory, you could also just disable the handling of M300 commands on your printer altogether.
I also noticed a bug when settings are saved, options get updated to the old settings instead of the new changes. This has been mitigated, making it easier (less confusing?) to test the M300 suppression changes.
Screenshot
Test Plan
These changes can be tested by installing the plugin from: https://github.com/stealthmonkey99/OctoPrint-PWMBuzzer/archive/suppress-m300.zip