Skip to content
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

Ecovacs Deebot 930 not working #128219

Open
pthoelken opened this issue Oct 12, 2024 · 9 comments
Open

Ecovacs Deebot 930 not working #128219

pthoelken opened this issue Oct 12, 2024 · 9 comments

Comments

@pthoelken
Copy link

The problem

I can configure and login with the integration and see my vacuumer and the sensors. But when I try to controle it, it doesn't work.

image

image

What version of Home Assistant Core has the issue?

core-2024.10.1

What was the last working version of Home Assistant Core?

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Ecovacs

Link to integration documentation on our website

https://homas.niekampsweg.de/config/integrations/integration/ecovacs

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

`2024-10-11 20:06:44.267 INFO (MainThread) [deebot_client.hardware.deebot] No capabilities found for y79a7u, therefore not all features are available. trying to use fallback...`

Additional information

No response

@home-assistant
Copy link

Hey there @mib1185, @edenhaus, @Augar, mind taking a look at this issue as it has been labeled with an integration (ecovacs) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of ecovacs can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign ecovacs Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


ecovacs documentation
ecovacs source
(message by IssueLinks)

@mib1185
Copy link
Contributor

mib1185 commented Oct 15, 2024

Your bot needs to be added to the deebot-client lib first, before it could be supported in HA

@pthoelken
Copy link
Author

@mib1185 thanks for your response. What does the deebot-client do and how can I install it? Did your have a step by step instruction for me to make it ready in HA?

@mib1185
Copy link
Contributor

mib1185 commented Oct 15, 2024

the deebot-client is the python library used by the ecovacs integration to control the newer/modern bots. You can start by open a request to this library to ask for support on adding your bot. You can also check existing requests there and try to get how to add your bot.

@pthoelken
Copy link
Author

As I understand correctly, I have to ask the official ecovacs support to add these library to my vacuumer model? Where can I do it?

@mib1185
Copy link
Contributor

mib1185 commented Oct 15, 2024

Nope ... simple said: you have to ask at the deebot-client library to add support for your model (or contribute the support on your own, if you are familiar how to do so). Neither Home Assistant nor the deebot-client is affiliated with ECOVACS nor is it sponsored or endorsed by ECOVACS manufacturer.

@pthoelken
Copy link
Author

pthoelken commented Oct 16, 2024

I've created a request here DeebotUniverse/client.py#587

After my Deebot is adding to the deebot-client, it will be working?

@mib1185
Copy link
Contributor

mib1185 commented Oct 16, 2024

as soon as support for your bot has been added to the deebot-client library, the lib needs to release a new version (containing the support of your model) than we can adopt this new version in HA

@mib1185 mib1185 added the waiting-for-upstream We're waiting for a change upstream label Oct 16, 2024
@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants