I have WS2812B on Pi4 with default settings on octoprint 1.4 installed from source on Linux Buster. "Effect delay" in every field is 10 of arbitrary units, which I assume are seconds or minutes and not hours. I have "Knight rider" effect for idle and startup and pulse green for complete.
Relevant logs from octoprint.log
2020-05-28 12:36:56,503 - octoprint.plugins.rgb_status - INFO - Updating Progress LEDs: 95
2020-05-28 12:37:08,008 - octoprint.util.comm - INFO - Finished in 950.423 s.
2020-05-28 12:37:08,009 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Finishing"
2020-05-28 12:37:08,020 - octoprint.printer.standard.job - INFO - Print job done - origin: local, path: Body3.gcode, owner: Oxmstr
2020-05-28 12:37:08,069 - octoprint.util.comm - INFO - Changing monitoring state from "Finishing" to "Operational"
2020-05-28 12:37:08,080 - octoprint.plugins.rgb_status - INFO - Updating Progress LEDs: 100
2020-05-28 12:37:08,158 - octoprint.plugins.detailedprogress - INFO - Printing stopped. Detailed progress stopped.
2020-05-28 12:37:08,172 - octoprint.plugins.excluderegion - INFO - Printing stopped: event=PrintDone
2020-05-28 12:37:08,174 - octoprint.plugins.rgb_status - INFO - Starting Done Effect
2020-05-28 12:37:08,177 - octoprint.plugins.rgb_status - INFO - Starting new effect Pulse
2020-05-28 12:37:08,186 - octoprint.plugins.rgb_status - INFO - Started new effect <Process(Pulse, started)>
In between there are no logs that are relevant to rgb_status during the 2 hour downtime, the finished effect was playing instead of idle, after starting a new print:
2020-05-28 14:25:01,486 - octoprint.plugins.detailedprogress - INFO - Printing started. Detailed progress started.
2020-05-28 14:25:01,497 - octoprint.plugins.excluderegion - INFO - Printing started
2020-05-28 14:25:01,550 - octoprint.plugins.tracking - INFO - Sent tracking event print_started
2020-05-28 14:25:02,618 - octoprint.plugins.rgb_status - INFO - Killed effect: Pulse
2020-05-28 14:25:02,619 - octoprint.plugins.rgb_status - INFO - Updating Progress LEDs: 0
2020-05-28 14:25:02,620 - octoprint.plugins.rgb_status - INFO - Killed effect: Pulse
2020-05-28 14:25:02,624 - octoprint.plugins.rgb_status - INFO - Starting new effect Solid Color
2020-05-28 14:25:02,639 - octoprint.plugins.rgb_status - INFO - Started new effect <Process(Solid Color, started)>
2020-05-28 14:25:12,602 - octoprint.plugins.HeaterTimeout - INFO - Print started, timer stopped
2020-05-28 14:25:43,869 - octoprint.plugins.rgb_status - INFO - Killed effect: Solid Color
Adding another instance, this time it showed done effect but after a while it changed to 100% progress bar.
2020-05-28 23:11:49,616 - octoprint.plugins.rgb_status - INFO - Updating Progress LEDs: 95
2020-05-28 23:12:15,849 - octoprint.plugins.rgb_status - INFO - Updating Progress LEDs: 96
2020-05-28 23:12:45,943 - octoprint.util.comm - INFO - Finished in 4407.068 s.
2020-05-28 23:12:45,945 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Finishing"
2020-05-28 23:12:45,953 - octoprint.printer.standard.job - INFO - Print job done - origin: local, path: 2Brim.gcode, owner: Oxmstr
2020-05-28 23:12:45,966 - octoprint.util.comm - INFO - Changing monitoring state from "Finishing" to "Operational"
2020-05-28 23:12:46,102 - octoprint.plugins.detailedprogress - INFO - Printing stopped. Detailed progress stopped.
2020-05-28 23:12:46,124 - octoprint.plugins.rgb_status - INFO - Starting Done Effect
2020-05-28 23:12:46,126 - octoprint.plugins.rgb_status - INFO - Starting new effect Pulse
2020-05-28 23:12:46,135 - octoprint.plugins.rgb_status - INFO - Started new effect <Process(Pulse, started)>
2020-05-28 23:12:46,373 - octoprint.plugins.rgb_status - INFO - Progress was set to 100, but the idle effect was already running. Ignoring progress update
2020-05-28 23:12:51,759 - octoprint.plugins.rgb_status - INFO - Killed effect: Pulse
2020-05-28 23:12:51,760 - octoprint.plugins.rgb_status - INFO - Updating Progress LEDs: 100
I have WS2812B on Pi4 with default settings on octoprint 1.4 installed from source on Linux Buster. "Effect delay" in every field is 10 of arbitrary units, which I assume are seconds or minutes and not hours. I have "Knight rider" effect for idle and startup and pulse green for complete.
Relevant logs from octoprint.log
In between there are no logs that are relevant to rgb_status during the 2 hour downtime, the finished effect was playing instead of idle, after starting a new print:
Adding another instance, this time it showed done effect but after a while it changed to 100% progress bar.