Error while processing hook octopod

[gernot11]

I am experiencing recurring issues with the OctoPod plugin on OctoPrint. During or after prints, the plugin throws repeated exceptions and sometimes the connection to OctoPrint becomes unresponsive. In some cases, the Raspberry Pi even requires a hardware reset.

octopod_issue.log

The print itself continues running on the printer, but OctoPrint becomes unreachable.

---

Environment

• OctoPrint version: 1.11.7
• OctoPi version: 1.1.0
• Python: 3.11.2
• Raspberry Pi: 3 Model B Rev 1.2
• OctoPod plugin version: 0.3.19

---

Observed behavior

• During print or shortly after:

  • OctoPod throws repeated exceptions
  • OctoPrint UI becomes unreachable (web + app)
  • Printer continues printing normally

• In some cases:

  • Raspberry Pi becomes unresponsive
  • Only hardware reset helps

---

Relevant log output

AttributeError: 'NoneType' object has no attribute 'process_received_gcode'
AttributeError: 'NoneType' object has no attribute 'process_sent_gcode'
AttributeError: 'NoneType' object has no attribute 'send_print_job_notification'

Full stack trace example:

File ".../octoprint_octopod/__init__.py", line 441, in process_received_gcode
    line = self._paused_for_user.process_received_gcode(...)
AttributeError: 'NoneType' object has no attribute 'process_received_gcode'

This repeats many times in the log:

ERROR - Error while processing hook octopod
ERROR - Error while processing hook octopod for phase sent

---

Additional warnings from OctoPod

Could not send message:
HTTPConnectionPool(host='octopodprint.com', port=80):
Failed to resolve 'octopodprint.com'

---

Reproduction (not 100% deterministic)

1. Start a print via OctoPrint

2. Let the print run for some time

3. Observe:

   • OctoPod errors start appearing
   • Eventually OctoPrint becomes unreachable

---

Notes / Suspicions

• It looks like _paused_for_user is None but still used
• Errors occur inside GCODE processing hooks
• Possibly triggered by connection issues or plugin state corruption
• Issue seems to worsen when network/DNS problems occur

---

Expected behavior

• Plugin should not crash or spam exceptions
• OctoPrint should remain responsive
• Network issues should be handled gracefully

---

Workaround

• Disabling OctoPod avoids the issue completely

---

Question

Is this a known issue with OctoPrint 1.11.x or Python 3.11 compatibility?

---

config.yaml

Thanks for your work on the plugin!