Skip to content

Map the machine status "pause" to the "paused" status in HA. - #16

Merged
GhostTypes merged 2 commits into
GhostTypes:mainfrom
RedAces:add-pause-status
Aug 8, 2026
Merged

Map the machine status "pause" to the "paused" status in HA.#16
GhostTypes merged 2 commits into
GhostTypes:mainfrom
RedAces:add-pause-status

Conversation

@RedAces

@RedAces RedAces commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

The Creator 5 Pro goes into this state e. g. when a clog is detected.

Map "downloading" to "busy" - debatable whether an extra HA status is required

RedAces added 2 commits August 8, 2026 11:28
The Creator 5 Pro goes into this state e. g. when a clog is detected.

Map "downloading" to "busy" - debatable whether an extra HA status is required
@GhostTypes
GhostTypes merged commit f6f0c96 into GhostTypes:main Aug 8, 2026
7 checks passed
GhostTypes added a commit that referenced this pull request Aug 8, 2026
Releases the "pause" and "downloading" status mappings from #16, which
ff-5mp-hass needs before its own clog fix does anything: without this,
a Creator 5 Pro sitting on a detected clog still reads "unknown" for
Machine Status and off for Paused.

Also corrects the #16 changelog's rationale for mapping "downloading"
onto BUSY rather than a new enum member. The concern is real for a
consumer that pins the enum to a fixed list, but ff-5mp-hass is not one:
its ENUM sensor derives its options from MachineState, so a new member
would reach it for free. Keeping BUSY for a patch release regardless -
a new state is a design decision, not a bugfix.

And makes test_empty_status_is_unknown_without_a_warning assert the
absence it is named for; it checked the return value twice and never
looked at caplog, so the no-warning guard was untested.

Co-Authored-By: Claude Code <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TWz3MaKK9nJTTs3EpGjjkf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants