Separately (possibly related, possibly expected robot behavior): while the vacuum is in the returning state, tapping Start again also has no effect — this may just be the robot correctly refusing to abort an in-progress return, not a bug, but flagging for context.
2026-08-07 09:42:30.478 DEBUG (MainThread) [custom_components.robovac.vacuum] Return home Pressed
2026-08-07 09:42:30.497 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.<device_id>] Sending to <device_id> (<ip>:6668): Message(0x7, b'{"devId": "<device_id>", "uid": "", "t": 1786088550, "dps": {"101": "return"}}', 156098328, <Device <device_id> (<ip>:6668)>)
2026-08-07 09:42:30.502 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.<device_id>] Received message from <device_id> (<ip>:6668): Message(0x7, b'', 156098328, None)
2026-08-07 09:42:30.502 DEBUG (MainThread) [custom_components.robovac.vacuum] Updating entity values from data points: {'2': True, '5': 'auto', '15': 'standby', ..., '122': 'Pause', ...}
# Start pressed 5 times over the following ~0.7s, each ACKed, state never changes:
2026-08-07 09:42:32.214 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.<device_id>] Sending to <device_id> (<ip>:6668): Message(0x7, b'{"devId": "<device_id>", "uid": "", "t": 1786088552, "dps": {"5": "Auto", "2": true}}', 156100024, <Device <device_id> (<ip>:6668)>)
2026-08-07 09:42:32.247 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.<device_id>] Received message from <device_id> (<ip>:6668): Message(0x7, b'', 156100024, None)
2026-08-07 09:42:32.248 DEBUG (MainThread) [custom_components.robovac.vacuum] Updating entity values from data points: {'2': True, '5': 'auto', '15': 'standby', ..., '122': 'Pause', ...}
2026-08-07 09:42:32.417 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.<device_id>] Sending to <device_id> (<ip>:6668): Message(0x7, b'{"devId": "<device_id>", "uid": "", "t": 1786088552, "dps": {"5": "Auto", "2": true}}', 156100183, <Device <device_id> (<ip>:6668)>)
2026-08-07 09:42:32.457 DEBUG (MainThread) [custom_components.robovac.vacuum] Updating entity values from data points: {'2': True, '5': 'auto', '15': 'standby', ..., '122': 'Pause', ...}
2026-08-07 09:42:32.619 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.<device_id>] Sending to <device_id> (<ip>:6668): Message(0x7, b'{"devId": "<device_id>", "uid": "", "t": 1786088552, "dps": {"5": "Auto", "2": true}}', 156100350, <Device <device_id> (<ip>:6668)>)
2026-08-07 09:42:32.672 DEBUG (MainThread) [custom_components.robovac.vacuum] Updating entity values from data points: {'2': True, '5': 'auto', '15': 'standby', ..., '122': 'Pause', ...}
2026-08-07 09:42:32.822 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.<device_id>] Sending to <device_id> (<ip>:6668): Message(0x7, b'{"devId": "<device_id>", "uid": "", "t": 1786088552, "dps": {"5": "Auto", "2": true}}', 156100503, <Device <device_id> (<ip>:6668)>)
2026-08-07 09:42:32.864 DEBUG (MainThread) [custom_components.robovac.vacuum] Updating entity values from data points: {'2': True, '5': 'auto', '15': 'standby', ..., '122': 'Pause', ...}
2026-08-07 09:42:32.923 DEBUG (MainThread) [custom_components.robovac.tuyalocalapi.<device_id>] Sending to <device_id> (<ip>:6668): Message(0x7, b'{"devId": "<device_id>", "uid": "", "t": 1786088552, "dps": {"5": "Auto", "2": true}}', 156100684, <Device <device_id> (<ip>:6668)>)
2026-08-07 09:42:32.969 DEBUG (MainThread) [custom_components.robovac.vacuum] Updating entity values from data points: {'2': True, '5': 'auto', '15': 'standby', ..., '122': 'Pause', ...}
Describe the bug
When the vacuum is in the
idlestate, no command (Start, Return Home) has any effect on the robot, even though the local Tuya connection successfully sends and the robot acknowledges each command. Debug logs show the underlyingdps['122']data point stuck at"Pause"throughout, and neither thestartservice (which sendsdps 5="Auto",dps 2=true) norreturn_to_base(which sendsdps 101="return") ever clears it —dps['15'](tuya_state) stays"standby"the whole time.Separately (possibly related, possibly expected robot behavior): while the vacuum is in the
returningstate, tapping Start again also has no effect — this may just be the robot correctly refusing to abort an in-progress return, not a bug, but flagging for context.To Reproduce
idlestate (observed here after a manual pause/pickup mid-cycle, away from dock)vacuum.start/vacuum.return_to_basedirectly), send Start or Return Homecustom_components.robovacand observe: the command is sent, queued, and ACKed by the device (Message(0x7, b'', ...)), but the reported state (dps.15,dps.122) never changesExpected behavior
Sending
startorreturn_to_basewhile the vacuum isidleshould either resume/move the robot, or the integration should recognize the stuckdps.122 = "Pause"condition and send whatever command actually clears it (rather than only touchingdps 2/5/101).Screenshots
N/A (behavior confirmed via debug log, see below)
Environment
Logs
(Device ID and local IP redacted.)
Additional context
dps['122']is"Pause"from the very start of this capture and never changes value across either the return-home command or five separate start commands — it appears to be a distinct "paused mid-cycle" flag that isn't addressed by any command this integration sends (onlydps 2/5/101are touched bystart/return_to_base).