No M105 after print job

octoprint.log

2020-02-02 20:31:04,569 - octoprint.plugins.firmwareupdater - INFO - Got CONNECTED event
2020-02-02 20:31:04,570 - octoprint.plugins.firmwareupdater - INFO - Run postflash flag is not set
2020-02-02 20:31:04,573 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-02-02 20:31:04,609 - octoprint.util.comm - INFO - Printer reports firmware name "Klipper"
2020-02-02 20:31:04,614 - octoprint.util.comm - INFO - Detected Klipper firmware, enabling relevant features for issue free communication
2020-02-02 20:31:05,596 - octoprint.plugins.tracking - INFO - Sent tracking event printer_connected, payload: {u'printer_baudrate': 250000, u'printer_port': u'/tmp/printer', 'firmware_name': 'Klipper'}
2020-02-02 20:31:31,735 - octoprint.server.util.flask - INFO - Passively logging in user garth from ::ffff:192.168.0.26
2020-02-02 20:32:12,409 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: Null.gcode, owner: garth, user: garth
2020-02-02 20:32:12,447 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2020-02-02 20:32:12,461 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: Null.gcode, owner: garth, user: garth
2020-02-02 20:32:12,500 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-02-02 20:32:12,515 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2020-02-02 20:32:13,396 - octoprint.plugins.tracking - INFO - Sent tracking event print_started, payload: {'origin': 'local', 'file': '368e4351c70dec0443890cd907be2d4cf5cfe417'}
2020-02-02 20:32:25,934 - octoprint.util.comm - INFO - Finished in 13.489 s.
2020-02-02 20:32:25,939 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Finishing"
2020-02-02 20:32:25,958 - octoprint.printer.standard.job - INFO - Print job done - origin: local, path: Null.gcode, owner: garth
2020-02-02 20:32:30,018 - octoprint.plugins.tracking - INFO - Sent tracking event print_done, payload: {'origin': 'local', 'file': '368e4351c70dec0443890cd907be2d4cf5cfe417', 'elapsed': 13}
2020-02-02 20:32:40,899 - octoprint.util.comm - INFO - Changing monitoring state from "Finishing" to "Operational"
2020-02-02 20:34:10,976 - octoprint.util.comm - INFO - No response from printer after 3 consecutive communication timeouts, considering it dead.
2020-02-02 20:34:11,003 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
2020-02-02 20:34:11,091 - octoprint.plugins.forcelogin - WARNING - Socket message held back, but backlog full. Throwing message away: plugin
2020-02-02 20:34:11,094 - octoprint.plugins.forcelogin - WARNING - Socket message held back, but backlog full. Throwing message away: plugin
2020-02-02 20:34:13,033 - octoprint.plugins.tracking - INFO - Sent tracking event commerror_timeout, payload: {'commerror_text': 'Too many consecutive timeouts, printer still connected and alive?'}
2020-02-02 20:35:29,622 - octoprint.server.util.flask - INFO - Passively logging in user garth from ::ffff:192.168.0.26
2020-02-02 20:42:22,182 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-02-02 20:42:45,801 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 189022}
2020-02-02 20:48:22,714 - octoprint.plugins.forcelogin - WARNING - Socket message held back, but backlog full. Throwing message away: plugin