Formally have this Client Library also support Ecovacs GOAT series of devices (lawn mower robots)?

[Gamester17]

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 have installed the latest version

The feature you want to suggest

This is directly related to an issue reported to Home Assistant's core repo about Ecovacs integration component there:

• Ecovacs GOAT A3000 LiDAR robotic lawn mower exposed as robot vacuum cleaner? home-assistant/core#169723

Now it looks like that the Ecovacs integration is currently already depending on the deebot-client library to not only support the Vacuum entiry in Home Assistant but they have also started using to use it to support the newer Lawn mower entiry as well without remapping states and actions, so while it is now possible to add and see some sensors from Ecovacs GOAT series of lawn mower robots the entities they expose partially how as "cleaning" instead "mowing".

• https://github.com/home-assistant/core/blob/dev/homeassistant/components/ecovacs/lawn_mower.py

  • https://www.home-assistant.io/integrations/lawn_mower/

    • https://github.com/home-assistant/core/tree/dev/homeassistant/components/lawn_mower

• https://github.com/home-assistant/core/blob/dev/homeassistant/components/ecovacs/vacuum.py

  • https://www.home-assistant.io/integrations/vacuum/

    • https://github.com/home-assistant/core/tree/dev/homeassistant/components/vacuum

Anyway, not sure if this should just be fixed in only the Ecovacs mower entity inside this ecovacs component in Home Assistant's core if it should also need to be fixed and corrected in the upstream deebot-client client library for Deebot devices (Vacuums) which it looks to depend on? I mean, would it be best to also extent the deebot-client to also support Ecovacs Ecovacs GOAT series of lawn mower robots as well or would it be better to fork deebot-client to create a new goat-client that is dedicated client library for Ecovacs GOAT devices (lawn mowers) and then make the Ecovacs mower entity import and use that instead?

• https://github.com/DeebotUniverse/client.py

That made me think that if we can convince the upstream developer(s) of deebot-client to more formally extend it to support for it, and might perhaps also be a good idea to convience them tomaybe rename the deebot-client library to ecovacs-client or something similar as Ecovacs do not only make vacuum and lawnmowever robots but have since also expanded to making a new pool cleaner robot which supports WiFi, then it has window cleaner series of robots too but all those currently only feature Bluetooth support.

As such this is also directly related to all the other feature suggestions/requests that ask this to support GOAT lawn mowers:

• Add support for Ecovacs GOAT A3000 LiDAR lawn mower robot #1574
• Ecovacs GOAT A1600 RTK Support #852
• Add support for Ecovacs GOAT O500 Panorama #936
• Ecovacs GOAT O800 RTK #1467
• Add support for GOAT O600 RTK (class: 6n9pcz) #1502
• Please add support for the GOAT O1200 RTK (qhq6i0) #964
• Add Support for GOAT O1200 LIDAR PRO #1524

For reference, here below is a copy of the original issue report submitted to Home Assistant's core repository about ecovacs:

Ecovacs GOAT A3000 LiDAR sensors exposed as a robot vacuum cleaner instead of as a device using robotic lawn mower platform?

Just installed a brand new Ecovacs GOAT A3000 LiDAR (o4kvvk) lawnmower robot yesterday and upgraded its firmware to latest version (FW version 1.13.31) before I added it for the first time to the Ecovacs integration in Home Assistant via their cloud account.

the problem is it looks like this model is partially exposing sensors as vacuum entities instead of as lawn mower entities as it should?

To clearify, Ecovacs GOAT A3000 LiDAR is a lawn mower robot and not a vacuum cleaner robot, so expect other names on sensors.

Problem is it now show several sensors entities use terminology that refer to "cleaning" instead of "mowing", like example these:

• "Area cleaned" instead of "Area mowed"
• "Cleaning duration" instead of "Mowing duration"
• "Total area cleaned" instead of "Total area mowed"
• "Total cleaning duration" instead of "Total mowing duration"
• "Total cleans" instead of "Total mows"

To me it only looks like all sensor entiry entries are using the wrong platform (using vacuum instead of lawn mower integration), or?

However Configuration and Diagnostics is using correct terminology (refering to stuff like "cut direction" and "blade lifespan")

[Gamester17]

Ecovacs do not only make vacuum and lawnmowever robots but have since also expanded to making a new pool robot which supports WiFi, then it has window cleaner series of robots too but all those currently only feature Bluetooth support.

For refence it would also be nice if this client library could also support the new Ultramarine P1 pool cleaner robot from Ecovacs too:

• https://www.ecovacs.com/global/ultramarine-robotic-pool-cleaner

Linking to feature request asking for new/seperate pool cleaner entity for pool cleaning devices (cloning existing vacuum entity):

• https://github.com/orgs/home-assistant/discussions/3662

UPDATE: This is not AI-spam. In fact nothing I wrote was written above was written using AI. I just have a neurodivergency that make me write very verbose and detained. Closing this as spam is frankly not only rude but practically discrimination against nurodiversity.

[edenhaus]

Closing this issue as it's AI spam. This library is already supporting mower without issues. Adding support needs to be done by the user as I cannot do it because Ecovacs has no public api documentation. Also renaming the repo or the pypi makes no sense as it working without any issues. Also most users don't see the package name.

[nord-]

Feel free to close it, but it's not AI spam. The sensors clearly states "cleaning", for a mower?
@edenhaus

[OCIO-ricky]

I can confirm there appears to be a legitimate GOAT related issue in the underlying client library.

While testing a GOAT A3000 LiDAR with the Home Assistant Ecovacs integration, I enabled debug logging and observed the following behavior:

• The integration successfully communicates with the Ecovacs cloud.
• Battery and some state updates are received.
• Pressing “Start Mowing” from Home Assistant sends a clean_V2 command.
• A P2P MQTT message is subsequently received for clean_V2.
• The client library logs:

Command clean_V2 does not support p2p handling (yet)

The mower does not start.

This suggests the issue is not simply user configuration or connectivity. There appears to be a missing or incomplete code path related to GOAT command handling in the client library.

Based on these findings, I believe the report warrants technical review rather than being dismissed as invalid or AI-generated.

[OCIO-ricky]

Here are some operational state observations i found while debugging:

• The entity history can show transitions such as Mowing, Paused, and Docked.
• However, I have not seen a reliable Returning / “returning to dock” state exposed.
• Paused is not equivalent to returning; I observed sequences where the mower changed from Mowing to Paused and then back to Mowing.
• So completion/return can only be inferred indirectly when the mower eventually reports Docked.

3. Error reporting appears incomplete

• Some mower errors visible in the Ecovacs app do not appear to be reliably reflected in Home Assistant.
• sensor.goat_a3000_lidar_error may remain 0 or not update live.
• This makes it difficult to automate around startup failures, blocked LiDAR cover conditions, or mowing errors.

4. Job telemetry appears stale or inconsistent

• Current job fields like area cleaned and cleaning duration may not update live during a mowing session.
• homeassistant.update_entity can refresh some fields, but live synchronization is inconsistent.
• Lifetime totals such as total area cleaned, total cleaning duration, and total cleanings may lag behind the Ecovacs app.