The creator 5 pro goes into "pause" mode if a clog is detected. - #23
Merged
Merged
Conversation
In error code it returns "E0163", but this code is undocumented. Fix the error-detection to include an error code returned from the machine. add a printer_state.py to read the current state of the printer for debugging
GhostTypes
added a commit
that referenced
this pull request
Aug 8, 2026
PR #23 made the Error binary sensor fire on a non-empty errorCode, which is what tells you something is wrong. It does not tell you what. On a Creator 5 Pro a clog never reaches the ERROR state - it pauses the print and fills errorCode - so the code is the entire diagnosis, and it lived on an entity that shipped disabled. Raw and unmapped on purpose. E0163 is not in FlashForge's published Creator 5 error table, so any code-to-description map is partial from the first release; a code you can search for beats a lookup that comes up empty. Existing installs keep the entity disabled - HA stores disabled_by at creation and does not revisit it when the default changes - so the changelog spells out how to switch it on. Also folds the duplicate Unreleased heading from #23 into the existing section and corrects its claim that the "pause" status mapping was fixed in flashforge-python-api: that is PR #16 there, still open and in no release. Co-Authored-By: Claude Code <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TWz3MaKK9nJTTs3EpGjjkf
GhostTypes
added a commit
that referenced
this pull request
Aug 8, 2026
1.3.5 carries the "pause" status mapping. Without it the clog fix from #23 is half-delivered: the Error sensor turns on, but Machine Status still reads "unknown" and the Paused sensor still reads off, because a Creator 5 Pro reports the undocumented "pause" rather than "paused". Raising the floor rather than leaving it to chance - the fix and the mapping are one behaviour to the user, and shipping them independently is how a bug report gets filed against the half that landed first. Also updates the CHANGELOG entry that described the mapping as pending; it is released now. Co-Authored-By: Claude Code <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TWz3MaKK9nJTTs3EpGjjkf
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In error code it returns "E0163", but this code is undocumented. (See https://wiki.flashforge.com/en/creator-series/creator-5-series/error_code_creator_5)
Fix the error-detection to include an error code returned from the machine.
add a printer_state.py to read the current state of the printer for debugging
It would be nice if the "error" entity wouldnt only display "problem" but WHICH problem! e. g. either the raw error code or a short value ("Clog detected!"). For this I'd need to activate the inactive error code entity and add a mapping from code to description. What do you say?