fix(ecovacs): split raw_get_positions into vacuum + mower services

`async_register_platform_entity_service` only supports one `entity_domain`
per call — registering twice with the same service name silently overrode
the vacuum handler, breaking the existing service.

Split into two distinct service names:
- `ecovacs.raw_get_positions` (vacuums, unchanged, backward-compatible)
- `ecovacs.mower_raw_get_positions` (lawn mowers, new)

The mower handler still raises `ServiceValidationError` until the optional
position capability for mowers lands in deebot-client (see
DeebotUniverse/client.py#1588). The test now reflects that user-facing
behaviour and will be updated once the lib bump happens.

Addresses CI 'Run tests Python 3.14.4 (ecovacs)' fail.

Author: Beennnn

homeassistant/components/ecovacs/services.py

@@ -8,13 +8,14 @@
 from .const import DOMAIN
 
 SERVICE_RAW_GET_POSITIONS = "raw_get_positions"
+SERVICE_MOWER_RAW_GET_POSITIONS = "mower_raw_get_positions"
 
 
 @callback
 def async_setup_services(hass: HomeAssistant) -> None:
     """Set up services."""
 
-    # Vacuum Services
+    # Vacuum: existing service, unchanged
     service.async_register_platform_entity_service(
         hass,
         DOMAIN,
@@ -25,14 +26,13 @@ def async_setup_services(hass: HomeAssistant) -> None:
         supports_response=SupportsResponse.ONLY,
     )
 
-    # Lawn Mower Services (Ecovacs GOAT family — same raw position payload as
-    # vacuums; exposed here so users can capture the response and inspect
-    # additional fields the cloud may return, e.g. RTK status / satellite count
-    # for GOAT mowers).
+    # Lawn Mower: distinct service name (helper only supports one entity_domain
+    # per service registration — registering twice with the same name would
+    # silently override the vacuum handler).
     service.async_register_platform_entity_service(
         hass,
         DOMAIN,
-        SERVICE_RAW_GET_POSITIONS,
+        SERVICE_MOWER_RAW_GET_POSITIONS,
         entity_domain=LAWN_MOWER_DOMAIN,
         schema=None,
         func="async_raw_get_positions",

homeassistant/components/ecovacs/services.yaml

@@ -3,5 +3,9 @@ raw_get_positions:
     entity:
       - domain: vacuum
         integration: ecovacs
+
+mower_raw_get_positions:
+  target:
+    entity:
       - domain: lawn_mower
         integration: ecovacs

homeassistant/components/ecovacs/strings.json

@@ -313,6 +313,10 @@
     "raw_get_positions": {
       "description": "Retrieves a raw response containing the positions of the chargers and the device itself.",
       "name": "Get raw positions"
+    },
+    "mower_raw_get_positions": {
+      "description": "Retrieves a raw response containing the positions of the chargers and the mower itself (Ecovacs GOAT family). The payload includes RTK fix quality, satellite counts and signal strength when supported by the mower firmware.",
+      "name": "Get mower raw positions"
     }
   }
 }

tests/components/ecovacs/test_services.py

@@ -8,9 +8,13 @@
 import pytest
 
 from homeassistant.components.ecovacs.const import DOMAIN
-from homeassistant.components.ecovacs.services import SERVICE_RAW_GET_POSITIONS
+from homeassistant.components.ecovacs.services import (
+    SERVICE_MOWER_RAW_GET_POSITIONS,
+    SERVICE_RAW_GET_POSITIONS,
+)
 from homeassistant.const import ATTR_ENTITY_ID
 from homeassistant.core import HomeAssistant
+from homeassistant.exceptions import ServiceValidationError
 
 pytestmark = [pytest.mark.usefixtures("init_integration")]
 
@@ -63,21 +67,16 @@ def mock_device_execute_response(data: dict[str, Any]) -> Generator[dict[str, An
     ],
 )
 @pytest.mark.parametrize(
-    ("device_fixture", "entity_id"),
-    [
-        ("yna5x1", "vacuum.ozmo_950"),
-        ("5xu9h3", "lawn_mower.goat_g1"),
-    ],
-    ids=["yna5x1", "5xu9h3"],
+    "device_fixture",
+    ["yna5x1"],
 )
-async def test_get_positions_service(
+async def test_get_positions_service_vacuum(
     hass: HomeAssistant,
     mock_device_execute_response: dict[str, Any],
-    entity_id: str,
 ) -> None:
-    """Test that get_positions service response snapshots match."""
-    entity = hass.states.get(entity_id)
-    assert entity
+    """Vacuum service returns the raw payload."""
+    entity_id = "vacuum.ozmo_950"
+    assert hass.states.get(entity_id)
 
     assert await hass.services.async_call(
         DOMAIN,
@@ -86,3 +85,36 @@ async def test_get_positions_service(
         blocking=True,
         return_response=True,
     ) == {entity_id: mock_device_execute_response}
+
+
+@pytest.mark.parametrize(
+    "data",
+    [{"deebotPos": {"x": 1, "y": 5, "a": 85}, "chargePos": {"x": 5, "y": 9, "a": 85}}],
+)
+@pytest.mark.parametrize(
+    "device_fixture",
+    ["5xu9h3"],
+)
+@pytest.mark.usefixtures("mock_device_execute_response")
+async def test_get_positions_service_mower_not_supported(
+    hass: HomeAssistant,
+) -> None:
+    """Mower service raises ServiceValidationError when the position capability is absent.
+
+    The optional position capability for mowers is being added in
+    DeebotUniverse/client.py#1588. Until that ships in a deebot-client release and
+    the integration bumps its pin, ``map.position.get`` is None on the 5xu9h3
+    fixture and the handler reports ``raw_get_positions_not_supported`` — which
+    is the user-facing behaviour we ship today.
+    """
+    entity_id = "lawn_mower.goat_g1"
+    assert hass.states.get(entity_id)
+
+    with pytest.raises(ServiceValidationError):
+        await hass.services.async_call(
+            DOMAIN,
+            SERVICE_MOWER_RAW_GET_POSITIONS,
+            {ATTR_ENTITY_ID: entity_id},
+            blocking=True,
+            return_response=True,
+        )