Skip to content

Add support for Deebot 502 #999

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
4 tasks done
howels opened this issue May 29, 2025 · 2 comments
Open
4 tasks done

Add support for Deebot 502 #999

howels opened this issue May 29, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@howels
Copy link

howels commented May 29, 2025

Checks

  • I have searched the existing issues and no issue is describing my issue
  • I have checked the FAQ
  • I have checked the documentation
  • I have installed the latest version

The problem

Deebot 502 is an older model but lacks support:

Device "DEEBOT 502" not supported. More information at https://github.com/DeebotUniverse/client.py/issues/612: {'did': '1a4e68b8-5553-4a74-b5d4-7345e259c8c1', 'name': 'e2001292591902451342', 'class': 'r8ead0', 'resource': '4o7k', 'company': 'eco-ng', 'bindTs': 1698043669862, 'service': {'jmq': 'jmq-ngiot-eu.dc.ww.ecouser.net', 'mqs': 'api-ngiot.dc-eu.ww.ecouser.net'}, 'deviceName': 'DEEBOT 502', 'icon': 'https://portal-ww.ecouser.net/api/pim/file/get/5c93204b63023c0001e7faa7', 'ota': False, 'UILogicId': 'D_500', 'materialNo': '702-0000-0161', 'pid': '5c763f63280fda0001770b88', 'product_category': 'DEEBOT', 'model': 'D502', 'updateInfo': {'needUpdate': False, 'changeLog': ''}, 'nick': None, 'homeId': '6268c13b63a68e3348296b37', 'homeSort': 1, 'status': 1, 'otaUpgrade': {}}

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

Deebot 502

Which version of the deebot-client are you using?

latest in HA OS

Country

gb

Continent

eu

Anything in the logs that might be useful for us?

Additional information

No response

@howels howels added the bug Something isn't working label May 29, 2025
@flubshi
Copy link
Contributor

flubshi commented May 31, 2025

To support your robot, we need to know the capabilities of the device. If you are lucky, there is already a similar robot that uses the same API. In this case, we need to figure out which one matches.

I would assume that the Deebot 502 is using the older XML commands. If thats the case, 2pv572.py would be a good starting point.

You can try to link to this existing robot and check if all features work:

  • Login to Home Assistant via SSH:
    • ssh hassio@<ip>
  • Run shell in docker:
    • docker exec -it $(docker ps -f name=homeassistant -q) bash
  • Change to library directory:
    • cd /usr/local/lib/python3.13/site-packages/deebot_client/hardware/deebot
  • Now it is time to find an existing model definition that matches your robot. You might have to try different links, until everything works:
    • Link exmaple: ln -svfT <existing_model> <your_model>
    • ln -svfT 2pv572.py r8ead0.py
  • Restart home assistant

Check if everything works. If not, go two steps back and link to another existing model.

You can find possible existing capability files here: https://github.com/DeebotUniverse/client.py/tree/dev/deebot_client/hardware/deebot

If you find capability file that enables all functions of the robot, please post here or create a pull request.

@howels
Copy link
Author

howels commented May 31, 2025

  • ln -svfT 2pv572.py r8ead0.py

Thanks so much for responding! Good guess on the model type also - that 2pv572.py does appear to match the capabilities - this is a basic start/pause/stop/home vacuum with no mapping ability and I have full control over the robot via that device type. I also see values reported for hours-used on replaceable parts, battery status and the total area cleaned.

@edenhaus edenhaus added enhancement New feature or request and removed bug Something isn't working labels Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants