Looking at the end of the print
2018-04-12 03:05:06,230 - Send: N267514 G28 X0*104
2018-04-12 03:05:06,243 - Recv: T:249.50 /250 B:70.04 /70 B@:0 @:104
2018-04-12 03:05:06,249 - Recv: ok 267513
2018-04-12 03:05:06,252 - Recv: ok 267514
2018-04-12 03:05:06,255 - Send: N267515 M400*21
2018-04-12 03:05:06,258 - Send: N267516 M114*22
2018-04-12 03:05:06,274 - Recv: ok 267515
2018-04-12 03:05:09,131 - Recv: X:0.00 Y:136.72 Z:14.17 E:-2.29
2018-04-12 03:05:09,149 - Recv: ok 267516
2018-04-12 03:05:09,164 - Recv: X:0.00 Y:136.71 Z:14.17 E:-2.29
2018-04-12 03:05:09,198 - Send: N267517 M140 S0*85
2018-04-12 03:05:09,223 - Recv: ok 267517
2018-04-12 03:05:09,231 - Recv: TargetBed:0
2018-04-12 03:05:09,237 - Send: N267518 M84*32
2018-04-12 03:05:09,255 - Recv: ok 267518
2018-04-12 03:05:09,287 - Changing monitoring state from "Printing" to "Operational"
it actually doesn't look like a
M104 S0 was sent. So the question is why. What I do see in there is a
M114 pair. Stock OctoPrint only sends those when cancelling a print, which was not the case here. Considering how many there are in there, I'm guessing you have Octolapse not only installed but also running here?
I know that this plugin does command replacements, and from the timing of that injected pair which is right where the
M104 S0 should be, I'm wondering if what you are seeing here is maybe caused by the plugin. Please disable the plugin or better yet enable safe mode as I mentioned earlier and see if your heater then properly shuts off at the end of a print. If it does, this is an issue in the plugin that will need to be investigated.
@FormerLurker, pinging you since this might be related to Octolapse.