Triggers when print ends about octoprint-cooldownnotification HOT 6 CLOSED

LOL, I did the same thing but went one step further and grabbed the type as well. It looks like when you change the threshold from the default (40), it saves it as a string instead of an integer. I'll have a fix published soon.

2020-05-29 12:40:56,812 - octoprint.plugins.CooldownNotification - INFO - Print Ended, Watching Heatbed Temp
2020-05-29 12:40:56,816 - octoprint.plugins.CooldownNotification - DEBUG - Heatbed Temp: 65.0
2020-05-29 12:40:56,817 - octoprint.plugins.CooldownNotification - DEBUG - Heatbed Temp Reached Threshold
2020-05-29 12:40:56,818 - octoprint.plugins.CooldownNotification - DEBUG - Heatbed Temp: 65.0 Type: float
2020-05-29 12:40:56,819 - octoprint.plugins.CooldownNotification - DEBUG - Heatbed Temp: 38 Type: str

from octoprint-cooldownnotification.

Same for me, triggers right after print end. Seems like its reading not the actual temp, but maybe a SET temp ?

from octoprint-cooldownnotification.

I set up debug logging in OctoPrint, and this is what is reported. Again, the threshold is set to 30.

2020-05-29 15:43:40,727 - octoprint.util.comm - INFO - Changing monitoring state from "Finishing" to "Operational"
2020-05-29 15:43:40,978 - octoprint.plugins.CooldownNotification - INFO - Print Ended, Watching Heatbed Temp
2020-05-29 15:43:40,988 - octoprint.plugins.CooldownNotification - DEBUG - Received Event: PrintDone
2020-05-29 15:43:40,998 - octoprint.plugins.CooldownNotification - DEBUG - Heatbed Temp: 80.15
2020-05-29 15:43:41,003 - octoprint.plugins.CooldownNotification - DEBUG - Heatbed Temp Reached Threshold
2020-05-29 15:43:41,019 - octoprint.plugins.CooldownNotification - DEBUG - Sending GCODE: M300 P143 S349
2020-05-29 15:43:41,959 - octoprint.plugins.CooldownNotification - INFO - Cooldown Notification Sent

from octoprint-cooldownnotification.

Thanks for the log info. I will take a look.

from octoprint-cooldownnotification.

I added a new debug line to confirm that the Threshold setting was set properly and read properly.

2020-05-29 17:01:48,228 - octoprint.util.comm - INFO - Changing monitoring state from "Finishing" to "Operational"
2020-05-29 17:01:48,289 - octoprint.plugins.CooldownNotification - INFO - Print Ended, Watching Heatbed Temp
2020-05-29 17:01:48,290 - octoprint.plugins.CooldownNotification - DEBUG - Received Event: PrintDone
2020-05-29 17:01:48,320 - octoprint.plugins.CooldownNotification - DEBUG - Heatbed Temp: 80.37
2020-05-29 17:01:48,321 - octoprint.plugins.CooldownNotification - DEBUG - Threshold: 30
2020-05-29 17:01:48,325 - octoprint.plugins.CooldownNotification - DEBUG - Heatbed Temp Reached Threshold

The code looks fine to me. I can't see where the problem is.

from octoprint-cooldownnotification.

This should be fixed in v0.1.2. I'll close this. Feel free to re-open if not fixed.

from octoprint-cooldownnotification.