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 GOAT G1 won't start #115162

Closed
Brazen00 opened this issue Apr 8, 2024 · 8 comments · Fixed by #116025
Closed

Ecovacs GOAT G1 won't start #115162

Brazen00 opened this issue Apr 8, 2024 · 8 comments · Fixed by #116025
Assignees

Comments

@Brazen00
Copy link

Brazen00 commented Apr 8, 2024

The problem

The Ecovacs GOAT G1 won't start when the "start cleaning" command is sent via the UI.

What version of Home Assistant Core has the issue?

core-2024.4.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ecovacs

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ecovacs/

Diagnostics information

config_entry-ecovacs-db6ac9ed4137c116f6e0ae1e47cdf99e.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: deebot_client.command
Source: components/ecovacs/vacuum.py:320
First occurred: 10:50:56 AM (1 occurrences)
Last logged: 10:50:56 AM

No response received for command "clean". This can happen if the device has network issues or does not support the command

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Apr 8, 2024

Hey there @OverloadUT, @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)

@edenhaus
Copy link
Contributor

edenhaus commented Apr 8, 2024

Your model itk04l is probably one of the new Goats and therefore not yet recognized by the library. Feel free to add support for by creating a model files in https://github.com/DeebotUniverse/client.py/tree/dev/deebot_client/hardware/deebot

@edenhaus edenhaus added problem in dependency waiting-for-upstream We're waiting for a change upstream labels Apr 8, 2024
@Brazen00
Copy link
Author

Brazen00 commented Apr 8, 2024

Is it as simple as adding itk041.py which points to 5xu9h3.py? Or is it more complex?

@edenhaus
Copy link
Contributor

edenhaus commented Apr 8, 2024

It depends if your models has different features than the other G1. If there are the same than you need only to create a symbol link. @Augar Do you think both models have the same features?
I don't have one so it hard for me to answer this question.

@Brazen00 Which G1 do you have?

@Brazen00
Copy link
Author

Brazen00 commented Apr 8, 2024

The model on the device is MPB11-11

@Brazen00
Copy link
Author

how would I test on my system whether the symlink works or not? i'm happy to do testing but i'm not a coding guru

@edenhaus
Copy link
Contributor

I can add it for you in the next days. It will have than the same capabilities as the current included G1.

@edenhaus
Copy link
Contributor

Fixed with #116025

@github-actions github-actions bot locked and limited conversation to collaborators May 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants