XML ChargeState IDLE should not produce any events

[nanomad]

Fixes #952

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.15%. Comparing base (5b6d68b) to head (e6eccfa).
Report is 15 commits behind head on dev.

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #956   +/-   ##
=======================================
  Coverage   93.15%   93.15%           
=======================================
  Files         128      128           
  Lines        4995     4997    +2     
  Branches      331      332    +1     
=======================================
+ Hits         4653     4655    +2     
  Misses        282      282           
  Partials       60       60           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[codspeed-hq]

CodSpeed Performance Report

Merging #956 will not alter performance

_{Comparing nanomad:feature/ignore-xml-idle-charge-state (e6eccfa) with dev (5b6d68b)}

Summary

✅ 6 untouched benchmarks

[nanomad]

Sure, that's how I tested the scenario I described. The idle state comes from the cleaning report messages not from the charger state Il Mar 13 Mag 2025, 19:20 Robert Resch ***@***.***> ha scritto:

…

***@***.**** commented on this pull request. ------------------------------ In deebot_client/messages/xml/charge_state.py <#956 (comment)> : > match charge_type.lower(): case "slotcharging" | "slot_charging" | "wirecharging": status = State.DOCKED case "idle": - status = State.IDLE + # Bot reports IDLE while not on the charger (e.g. while cleaning) + # We ignore this state since it will conflict with the actual cleaning state + pass If i stop cleaning without pressing return to base: IDLE Can we still mark the bot as idle with the above changes? — Reply to this email directly, view it on GitHub <#956 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIT3RXHF4XECSYPSVBJLHL26ISVPAVCNFSM6AAAAAB4XENLCGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDQMZXGU4DANRXHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[edenhaus]

Thanks @nanomad 👍