Trigger on Tool Temp about octoprint-cooldownnotification HOT 12 OPEN

My friend, my apologies. I was reading the component now and I realized the plugin was setup to trigger by the bed temperature instead of the hot end and I thought it was the opposite. I wasn't expecting the bed temperature at all.

Is there any way we can have both options?

from octoprint-cooldownnotification.

Could you enable debug logging for the plugin and provide the octoprint.log?

Could you also confirm the version number?

from octoprint-cooldownnotification.

Hi, thanks for your reply. I did that and it's not showing any log so far. I was able to clean all other plugins and they were generated but not for CoolDownNotification.
After rebooting the system etc, I was able to get it working but not at the right temperature. I set for 50C and it's running around 70. It's still weird that the log is not showing up

from octoprint-cooldownnotification.

Hi, thanks for your reply. I did that and it's not showing any log so far. I was able to clean all other plugins and they were generated but not for CoolDownNotification.
After rebooting the system etc, I was able to get it working but not at the right temperature. I set for 50C and it's running around 70. It's still weird that the log is not showing up

Make sure you click the plus sign so it turns into a little trash can (like my pic above) prior to saving.

from octoprint-cooldownnotification.

from octoprint-cooldownnotification.

My friend, I found what is going on. So the temperature triggering is not the nozzle temperature. It's the bed temperature. When I set 50C, the bed temperature hits fast this temp and it was running earlier than expected(comparing with the hot end temperature) but when I lowered down to 35, it took forever, the hot end was colder than this and then once the bed temperature reached 35C, it ran the GCODE as expected. I recorded a video on my phone if you want I can send you.

Also, the log was not created as well. I hope I have helped.

from octoprint-cooldownnotification.

Well, that explains it. Yes, it's for bed temp. I was thinking about adding tool temp as well but it wasn't a priority since I didn't know how much it would be needed. I'll work on it.

from octoprint-cooldownnotification.

Thank you and my apologies. I would also include the word bed in the temperature field so everybody would get right away :)

Thanks again and let me know if you want me to test once you get it. I am pretty sure that will be very useful as there isn't any other plugin doing that so far

from octoprint-cooldownnotification.

I had the same issue. I thought the temperature was linked to the hot end. And it would be great, in my case, to be the latter as I am using it to turn off the printer by moving to the front and triggering a relay.

from octoprint-cooldownnotification.

Afternoon,
Wondering if you are planning on revisiting this project.
Notes:

1. I did setup the debug but nothing is been recorded. So it is impossible to check the workflow. :(
2. In another thread, I've mentioned hacking the plugin and replacing "bed" with "tool0" to try to retrieve the Hot End temperature. But it did not work! I don't know how to display or check what is returned by "printer.get". I know nothing about API. But "tool0" has to exist and its temp has to be always less or equal than "threshold" since the GCODE get executed!
   if 'tool0' in self._printer.get_current_temperatures(): toolTemp = self._printer.get_current_temperatures()['tool0']['actual'] threshold = int(self._settings.get(["Threshold"])) self._logger.debug("Hot End Temp: " + str(toolTemp)) if toolTemp <= threshold: self._logger.debug("Hot End Temp Reached ... _blablabla_
3. I've changed the notify_events to ['PrintDone'] only so it would not shutdown on a cancel :)
4. The enable button in the Navbar is crucial so we can easily toggle the plugin ON/OFF.
   I hope you are doing great and survived 2019.
   Cheers, Alex.

from octoprint-cooldownnotification.

Hi there,

Yes I would also like to see if there would be an option for triggering on tool temperature. So I could control my smart switch using this plugin and PSU control plugin by sending M81. Currently I add M81 to my slicer end gcode which sometimes causes my print to be unfinished as there are some additional lines generated by my slicer after my end gcode. Thanks in advance bro

from octoprint-cooldownnotification.

Yesterday, I've finished a long print and "Ho surprise!" the hack #2 worked and triggered when the Hot End reach my 40C setting. I did revert my change on #3, [PrintDone], to the original value. So no change there! I will post the files in the FORK

from octoprint-cooldownnotification.