Home Assistant room cleaning commands overridden by last settings in Eufy app

[Denkra]

System Health details

.

Checklist

• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of any previous issues..

Describe the issue

I am using a Home Assistant integration to control my Eufy E28. While basic controls work as expected, there is an issue with room-specific cleaning modes being overridden by the official Eufy app.

When triggering a room clean through Home Assistant, the integration fails to override the last used hardware state from the proprietary cloud, causing the robot to fall back to its previous app configuration instead of respecting the parameters sent by Home Assistant.

Steps to Reproduce / Behavior:
In the official Eufy app, I previously configured a specific room to be both vacuumed and mopped.

Later, inside Home Assistant, I trigger a command to clean that exact same room, but explicitly set the mode to vacuum only.

Result: The robot starts the cleaning cycle but ignores the Home Assistant parameters. Instead, it falls back to the last saved configuration from the official Eufy app and begins both vacuuming and mopping.

Reproduction steps

1. Open the official Eufy Security / Home app on your mobile device.

2. Select a specific room (e.g., "Living Room") and set its cleaning preferences to both vacuum and mop. Run or save this configuration so it is stored in the Eufy cloud.

3. Let the robot finish or cancel the run, ensuring it returns to the dock.

4. Go to Home Assistant and navigate to Developer Tools -> Services (or use a dashboard card / automation).

5. Trigger a room cleaning command for that same room, but explicitly change the attributes/parameters to vacuum only (e.g., setting mop intensity to off, or selecting the vacuum-only service call if available).

.6 Observe the robot's behavior as it starts the task.

Debug logs

.

Diagnostics dump

No response

[jeppesens]

Thanks for the detailed reports — cross-posting to #133 and #143 since they share the same root cause.

This is device/firmware-specific (it reproduces for @Denkra / @ItsMeRitch but not for @m11tch), so before changing the room-clean command logic I'd like to capture exactly what the official Eufy app sends for a room clean with an explicit mode, so we can replicate it precisely rather than guess.

If you can reproduce it, could you grab the following? Enable debug logging first:

logger:
  default: warning
  logs:
    custom_components.robovac_mqtt: debug

Then, in one sitting:

1. Device + firmware — model code (e.g. T2080A / E28 / E20) and the robot's firmware version.
2. App, Vacuum+Mop baseline — in the official app set one room to Vacuum and Mop and clean just that room; let it start, then stop it.
3. App, Vacuum-only — in the app set the same room to Vacuum only and clean just that room; stop it.
4. HA, Vacuum-only — in Home Assistant select Vacuum in the Cleaning Mode entity, then trigger the same room clean.

Attach the full debug log covering all four steps. The lines I'm after:

• the cmd/eufy_home/.../res payloads showing the device's reported clean_param and area_clean_param after steps 2 and 3 — this tells us whether your device stores the mode globally or per-room;
• the Sending command to cmd/eufy_home/.../req line(s) from step 4 (what HA sends) and the device's res afterward.

If you can packet-capture the app's own DPS 152 (ModeCtrlRequest) / 154 (CleanParam) for steps 2–3, that's the gold standard — but the debug log above is usually enough.

With that I can match the app's exact command (likely SelectRoomsClean.CUSTOMIZE carrying per-room clean_type) so HA's mode is honored on per-room-param devices without regressing the ones that already work.