Add support for Deebot T9 (ipohi5)

[WARIO2412]

Add Deebot T9 support, class 'ipohi5'.

My Deebot T9 has a different class than other ones. Therefore I added my class in this PR.
The simlink is also pointing to the Deebot T8 (x4d34r.py). Everything works as expected right now.

Summary by CodeRabbit

• New Features

  • Introduced a comprehensive configuration for a new robotic vacuum device, enhancing its operational capabilities.

• Bug Fixes

  • Updated tests to include the new device identifier, ensuring proper recognition during model loading tests.

• Tests

  • Validated the retrieval of static device information and event capabilities for the new device.

[coderabbitai]

Walkthrough

The changes in this pull request introduce a new file, x5d34r.py, which establishes a comprehensive configuration for a robotic vacuum device within the deebot_client framework. This file defines various capabilities such as device type, battery status, cleaning actions, and error handling through a modular design. Additionally, the test suite is updated to recognize the new device identifier "ipohi5" in the model loading tests, ensuring proper validation of device functionalities.

Changes

File	Change Summary
deebot_client/hardware/deebot/x5d34r.py	New file added to define comprehensive configurations for a robotic vacuum device.
tests/hardware/test_init.py	Added new device identifier "ipohi5" to the test_all_models_loaded function.

Possibly related issues

• Add support for T9+ #620: The addition of support for the DEEBOT T9+ is relevant as the new configurations may help in recognizing and supporting this device.
• Add support for Deebot T9 AIVI (8kwdb4) #607: The request for support for the DEEBOT T9 AIVI aligns with the introduction of new device capabilities in this PR.

Possibly related PRs

• Add support for Deebot N8 #613: Related as it also introduces a new file for robotic vacuum configurations, sharing similar functionalities.
• Add support for Deebot N8 Pro+ Black #619: Introduces a new file that defines capabilities for a robotic vacuum device, closely related to this PR.
• adding Deebot N30 Omni support (zwkcqc) #622: Contains a new file for a robotic vacuum device with capabilities similar to those in this PR.
• Add Deebot OZMO T9 AIVI #624: Adds a file defining capabilities for a robotic vacuum device, consistent with the objectives of the main PR.
• Add support for Deebot T9 AIVI (8kwdb4) #630: Introduces a new file for the DEEBOT OZMO T9 AIVI, focusing on similar device functionalities.

Suggested labels

pr: new-feature

Suggested reviewers

• edenhaus

Poem

🐇 In the world of bots, a new friend appears,
With features so bright, it calms all your fears.
From cleaning to charging, it handles with grace,
The x5d34r's here, ready to race!
So let’s cheer for the changes, both big and small,
For our robotic companions, we’ll cherish them all! 🌟

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between e0fde3d and 2f55758.

📒 Files selected for processing (2)

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

🔇 Additional comments (2)

deebot_client/hardware/deebot/ipohi5.py (1)

1-1: ⚠️ Potential issue

Remove unintended filename declaration

The first line 'x5d34r.py' appears to be an unintended artifact and should be removed from the code.

Apply this diff to fix the issue:

- x5d34r.py

Likely invalid or redundant comment.

tests/hardware/test_init.py (1)

273-273: Consistency Check: Verify device identifier usage

Ensure that the device identifier 'ipohi5' is consistently used across all relevant tests and aligns with the filename in the hardware directory.

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.68%. Comparing base (e0fde3d) to head (2f55758).
Report is 8 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #651   +/-   ##
=======================================
  Coverage   86.68%   86.68%           
=======================================
  Files          90       90           
  Lines        3365     3365           
  Branches      298      298           
=======================================
  Hits         2917     2917           
  Misses        394      394           
  Partials       54       54           

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

[edenhaus]

Thanks @WARIO2412 👍