Skip to content

fix: name B01 Q7 code 2103 and document dock dust-collection state fields - #921

Open
akj wants to merge 2 commits into
Python-roborock:mainfrom
akj:q7-b01-notification-codes
Open

fix: name B01 Q7 code 2103 and document dock dust-collection state fields#921
akj wants to merge 2 commits into
Python-roborock:mainfrom
akj:q7-b01-notification-codes

Conversation

@akj

@akjakj commented Aug 16, 2026

Copy link
Copy Markdown

Small follow-up to #919, based on a live end-to-end capture of a completed clean → docking → auto-empty on a Q7 M5+ (roborock.vacuum.sc05, fw 03.01.80). Full evidence timeline is in this #919 comment.

Changes:

  • B01Fault.F_2103: placeholder fault_2103cleaning_complete_docked. Observed appearing the moment a completed clean's dock + dust collection finished, persisting while docked-idle; it follows 2102 (cleaning_complete, seen exactly at completion/return) and is a benign task notification, not an error.
  • B01Props.station_act / dust_action: documented hw-observed dock-emptying semantics — station_act=3 + dust_action=1 during the ~30s auto-empty cycle, both 0 otherwise; dust_action is read-only (prop.set rejected with code 1).

These two fields are enough for a "dock emptying" state/sensor downstream; the clean record's record_dust_num additionally tracks empties per clean.

Left 2105 as a placeholder — I've observed it while long-idle on the dock (possibly a later idle/charged notice) but don't have a clean state transition for it yet; happy to capture more if useful.

…elds
Live capture on a Q7 M5+ (roborock.vacuum.sc05, fw 03.01.80) through a
completed clean, docking, and auto-empty shows:
- fault 2102 (cleaning_complete) at completion/return, then 2103 the
moment the task finishes on the dock, persisting while docked-idle —
2103 is a benign task notification, now named cleaning_complete_docked.
- station_act=3 with dust_action=1 during the ~30s auto-empty cycle;
both return to 0 after. dust_action is read-only (prop.set rejected
with code 1). Documented on the container fields.
Evidence timeline in Python-roborock#919 (comment).
@akj
akj marked this pull request as ready for review August 16, 2026 16:09
Sign up for freeto 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.

1 participant

@akj