Ecovacs DEEBOT 600 not supported

[scottyphillips]

The problem

Good morning,

I have an older Deebot 600 that is not officially supported by the official Ecovacs component, as my understanding is that it is an older model that uses XMPP for control. At the moment I have been reliant on a custom component (which uses an unmaintained 'ozmo' library), but having played around with the code this morning, I realize it is on borrowed time. I would like to work with the maintainers of the official component to get support for my Deebot added back into the main core. I can help with providing all interesting data on my vacuum as required, I just would need to be pointed in the right direction. I managed to get ozmo working in a python command line, so I can run and capture any debugs needed.

What version of Home Assistant Core has the issue?

core-2024.10.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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

I am currently using this custom component -> https://github.com/Ligio/hacc-ozmo

[home-assistant[bot]]

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]

Hi @scottyphillips just to be sure - did you already try to add your bot with the ecovacs integration?

[nchieffo]

I've added it: the robot is discovered but all the sensors and the vacuum is set to unavailable

[scottyphillips]

I've added it: the robot is discovered but all the sensors and the vacuum is set to unavailable

Thanks mate, that’s the same issue I have with the official integration.

[mib1185]

I've added it: the robot is discovered but all the sensors and the vacuum is set to unavailable

ok, than as next step please enable debug logging, restart the integration and download and provide the log file after the issue occur again.

Further if possible please download and provide the diagnostics data for this integration.

Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.

thx 👍

[nchieffo]

LOG: home-assistant_ecovacs_2024-10-19T08-52-32.135Z.log DIAGNOSTICS: config_entry-ecovacs-01J9QSPQWQWWQSW93PM6GQQXK2.json

[issue-triage-workflows[bot]]

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.

[nchieffo]

Yup, still happening in 2024.11.0

[issue-triage-workflows[bot]]

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.

[nchieffo]

Still not working in 2024.11.2