Skip to content

DEEBOT X5 OMNI (model_id 4jd37g) mapped to wrong T20 Omni capabilities #1709

Description

@nino76

Checks

  • I have read the above text and I'm aware of the situation
  • I have searched the existing issues and no issue is describing my issue
  • I'm not creating an issue to add support for a new device/model.
  • I have installed the latest version

The problem

I have a DEEBOT X5 OMNI detected as:

Model: DEEBOT X5 OMNI
Model ID: 4jd37g
Firmware: 1.74.0

The integration loads:

deebot_client/hardware/4jd37g.py

which contains:

"Deebot T20 Omni Capabilities."

I noticed that this seems to be incorrect. The X5 OMNI appears to have the same capability structure as the X5 PRO OMNI.

As a test, I temporarily replaced the capabilities profile with:

deebot_client/hardware/mxse7w.py

(DEEBOT X5 PRO OMNI)

After this change the device works correctly and commands using the newer JSON API work:

  • clean_V2
  • freeClean
  • area cleaning

With the original T20 profile I get errors such as:

Command "clean" was not successfully.
body={'code':20003,'msg':'rcp not support'}

Could the model mapping for 4jd37g be reviewed?

On which deebot device (vacuum) you have the issue?

Deebot X5 OMNI

Which version of the deebot-client are you using?

18.4.0

Country

it

Continent

eu

Anything in the logs that might be useful for us?

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions