Add Deebot OZMO T9 AIVI

[Yterz]

Add Deebot OZMO T9 AIVI, class '659yh8'
Base on the Deebot OZMO T8 AIVI, class 'x5d34r', as most likely all OZMO T8 T9 T10 many variants

Summary by CodeRabbit

Summary by CodeRabbit

• New Features

  • Introduced a new device model, "659yh8", enhancing the hardware capabilities with various functionalities, including battery management, cleaning actions, and mapping.

• Tests

  • Expanded test coverage for hardware initialization by adding the new device identifier to the test suite, ensuring comprehensive validation of device functionalities.

[coderabbitai]

Walkthrough

A new file named x5d34r.py has been added to the deebot_client/hardware/deebot/ directory. Additionally, the test suite in tests/hardware/test_init.py has been updated to include a new device identifier, "659yh8", in the test_all_models_loaded function. The existing test functions remain unchanged but continue to validate device capabilities and static information retrieval.

Changes

File Path	Change Summary
deebot_client/hardware/deebot/x5d34r.py	New file added.
tests/hardware/test_init.py	Added device identifier "659yh8" to test_all_models_loaded.

Possibly related issues

• Add support for T9+ #620: The addition of support for new device models, including the T9+, aligns with the changes made in this PR.

Possibly related PRs

• Add support for Deebot N8 #613: Introduces the new file x5d34r.py, indicating a direct relation in terms of file creation.
• Add support for Deebot T10 #618: Adds a file jtmf04.py that encapsulates various capabilities for a vacuum device, similar to those defined in x5d34r.py.
• Add support for Deebot N8 Pro+ Black #619: Also adds a new file named x5d34r.py, suggesting a connection based on functionality.
• adding Deebot N30 Omni support (zwkcqc) #622: Introduces another new file zwkcqc.py, related to the addition of a new device, similar to x5d34r.py.

Suggested labels

pr: new-feature

Suggested reviewers

• edenhaus

Poem

🐇 In the land of code where rabbits play,
A new file hops in to brighten the day.
With tests that grow and models anew,
We celebrate changes, both fresh and true!
So let’s code and test, with joy and cheer,
For every new feature brings us near! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between e2db4e9 and b780f79.

📒 Files selected for processing (1)

• deebot_client/hardware/deebot/659yh8.py (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• deebot_client/hardware/deebot/659yh8.py

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

🧹 Outside diff range and nitpick comments (1)

tests/hardware/test_init.py (1)

260-260: Consider adding specific test cases for T9 AIVI capabilities

While adding the model ID to test_all_models_loaded is correct, consider adding test cases in test_capabilities_event_extraction to validate the specific capabilities of the T9 AIVI model.

Would you like me to help generate test cases for the T9 AIVI model's capabilities?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 987cc64 and e2db4e9.

📒 Files selected for processing (2)

• deebot_client/hardware/deebot/659yh8.py (1 hunks)
• tests/hardware/test_init.py (1 hunks)

🧰 Additional context used

🪛 Ruff (0.8.0)

deebot_client/hardware/deebot/659yh8.py

1-1: Found useless expression. Either assign it to a variable or remove it.

(B018)

---

1-1: Undefined name x5d34r

(F821)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.42%. Comparing base (987cc64) to head (b780f79).
Report is 1 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #624   +/-   ##
=======================================
  Coverage   86.42%   86.42%           
=======================================
  Files          88       88           
  Lines        3301     3301           
  Branches      298      298           
=======================================
  Hits         2853     2853           
  Misses        394      394           
  Partials       54       54           

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

[edenhaus]

Thanks @Yterz 👍