While messing with my printer the other day, I apparently did something to cause the plugin to repeatedly beep. It seems like this only occurs with the "wait_for_cooldown" option, but I haven't investigated yet.
2021-03-29 18:58:52,782 - octoprint.plugins.DisplayLayerProgress - INFO - Printing stopped. Detailed progress stopped.
2021-03-29 18:58:52,784 - octoprint.plugins.FriendlyBeeper - INFO - Waiting for bed to cooldown
2021-03-29 18:58:53,976 - octoprint.plugins.tracking - INFO - Sent tracking event print_failed, payload: {'origin': 'local', 'file': 'f8fea25321e98a969e487197ef177f2cd1212512', 'elapsed': 58, 'reason': 'cancelled'}
2021-03-29 18:59:11,178 - octoprint.util.comm - INFO - Timeout while in an active heatup, considering heatup to be over.
2021-03-29 19:00:04,683 - octoprint.util.comm - INFO - No response from printer after 6 consecutive communication timeouts, considering it dead.
2021-03-29 19:00:04,765 - octoprint.util.comm - INFO - Changing monitoring state from "Cancelling" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
2021-03-29 19:00:04,804 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2021-03-29 19:00:05,229 - tornado.access - WARNING - 409 GET /api/printer?history=false&limit=0&exclude=sd (127.0.0.1) 18.76ms
2021-03-29 19:00:05,419 - tornado.access - WARNING - 409 GET /api/printer?history=false&exclude=sd,state (127.0.0.1) 8.11ms
2021-03-29 19:00:05,433 - octoprint.plugins.tracking - INFO - Sent tracking event commerror_timeout, payload: {'commerror_text': 'Too many consecutive timeouts, printer still connected and alive?'}
2021-03-29 19:00:07,231 - tornado.access - WARNING - 409 GET /api/printer?history=false&limit=0&exclude=sd (127.0.0.1) 16.42ms
2021-03-29 19:00:08,433 - tornado.access - WARNING - 409 GET /api/printer?history=false&exclude=sd,state (127.0.0.1) 16.64ms
2021-03-29 19:00:09,231 - tornado.access - WARNING - 409 GET /api/printer?history=false&limit=0&exclude=sd (127.0.0.1) 16.33ms
2021-03-29 19:00:11,231 - tornado.access - WARNING - 409 GET /api/printer?history=false&limit=0&exclude=sd (127.0.0.1) 15.66ms
2021-03-29 19:00:11,432 - tornado.access - WARNING - 409 GET /api/printer?history=false&exclude=sd,state (127.0.0.1) 15.69ms
2021-03-29 19:00:13,332 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2021-03-29 19:00:13,374 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 1 port/baudrate candidates: /dev/ttyACM0@115200
2021-03-29 19:00:13,374 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyACM0, baudrate 115200
2021-03-29 19:00:13,376 - octoprint.util.comm - INFO - Connecting to port /dev/ttyACM0, baudrate 115200
2021-03-29 19:00:13,384 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-03-29 19:00:13,394 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-03-29 19:00:13,414 - tornado.access - WARNING - 409 GET /api/printer?history=false&limit=0&exclude=sd (127.0.0.1) 7.92ms
2021-03-29 19:00:14,455 - tornado.access - WARNING - 409 GET /api/printer?history=false&exclude=sd,state (127.0.0.1) 38.78ms
2021-03-29 19:00:14,462 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Operational"
2021-03-29 19:00:14,630 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-03-29 19:00:14,949 - octoprint.plugins.FriendlyBeeper - INFO - Couldn't find printbed temperature
2021-03-29 19:00:21,215 - octoprint.util.comm - INFO - Printer reports firmware name "Prusa-Firmware 3.9.3 based on Marlin"
2021-03-29 19:00:21,919 - octoprint.plugins.tracking - INFO - Sent tracking event printer_connected, payload: {'firmware_name': 'Prusa-Firmware 3.9.3 based on Marlin', 'printer_port': None, 'printer_baudrate': 115200}
2021-03-29 19:00:22,795 - octoprint.plugins.FriendlyBeeper - INFO - Couldn't find printbed temperature
2021-03-29 19:03:15,019 - octoprint.plugins.FriendlyBeeper - INFO - Sent M300 S2250 P200 on event cool_down
2021-03-29 19:03:45,081 - octoprint.plugins.FriendlyBeeper - INFO - Sent M300 S2250 P200 on event cool_down
2021-03-29 19:04:15,161 - octoprint.plugins.FriendlyBeeper - INFO - Sent M300 S2250 P200 on event cool_down
2021-03-29 19:04:45,218 - octoprint.plugins.FriendlyBeeper - INFO - Sent M300 S2250 P200 on event cool_down
2021-03-29 19:04:49,561 - octoprint.util.comm - WARNING - Printer sent 'start' while already operational. External reset? Resetting line numbers to be on the safe side
2021-03-29 19:04:49,567 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-03-29 19:04:56,126 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-03-29 19:05:15,273 - octoprint.plugins.FriendlyBeeper - INFO - Sent M300 S2250 P200 on event cool_down
I ended up just restarting octoprint to get out of that state, but I should still fix this
While messing with my printer the other day, I apparently did something to cause the plugin to repeatedly beep. It seems like this only occurs with the "wait_for_cooldown" option, but I haven't investigated yet.
Logs
I ended up just restarting octoprint to get out of that state, but I should still fix this