Begin with the quick checks. Stop if a step requires tools or experience you do not have.
If your Ecovacs T20 OMNI YIKO voice assistant is not working, first distinguish no wake response from a command that is acknowledged but not carried out. Those observations narrow the problem more effectively than repeating a long instruction across the room.
Choose one simple command from the current ECOVACS HOME guidance and test it in a quiet setting. Record whether the robot responds to the wake phrase, whether it acknowledges the request and whether the task begins. Keep any alert shown in the app.
Match the result to the next check
| What you observe | Check next |
|---|---|
| No response to the wake phrase | YIKO enabled, current connection and test conditions |
| Wake response but no task | Supported command and any task alert |
| Response works nearby but not across the room | Compare distance and background noise |
| App cannot reach the robot either | Connection troubleshooting |
| Delay began after a software change | Record app and firmware versions |
1. Confirm that YIKO is enabled
Ecovacs’ YIKO usage instructions say the assistant must be enabled in ECOVACS HOME and the robot must have a network connection. Use the voice guidance and command list in the app: the manufacturer notes that supported commands may change.
Confirm you are viewing the correct T20 OMNI if several robots are listed. Save a screenshot of the setting before changing anything else. A robot that cleans normally from the app can still require a separate check of its voice-assistant setting.
Check the app’s current device status rather than an old notification. If it shows Offline or cannot refresh, follow the T20 Wi-Fi guide before interpreting a failed voice test.
2. Use a short, controlled voice comparison
Follow the app’s wake-phrase guidance, then try one listed command. Use ordinary clear speech and give the robot a chance to respond before repeating it. Avoid combining several different requests in one trial.
In its voice-response troubleshooting guidance, Ecovacs identifies excessive noise, distance and unclear speech as possible recognition issues. It also recommends a good Wi-Fi signal and current app and robot firmware. Its note says YIKO does not work during a video voice call.
Reduce background sound for the comparison and note your position. If one nearby attempt works but a distant one does not, retain that result. Do not assume the microphone is damaged from an unsuccessful command shouted over a television.
3. Separate recognition from task execution
Listen for the wake response before assessing what happens next. If that response occurs, record the exact command and any acknowledgment. If a warning prevents cleaning, copy its wording rather than treating the whole sequence as silence.
Compare the same ordinary task through the app when it is appropriate to start it. If both routes fail with the same alert, address that alert. If the app task works but the voice request does not, that is useful evidence for voice troubleshooting.
A room-specific request also depends on what the app currently shows for that room. Check the selected area and saved layout when the task concerns a particular location. For a distorted map, use the T20 mapping guide; for a room the robot cannot reach, use the missed-room checks.
4. Review versions without interrupting an update
Record the installed firmware and app versions, especially if the behavior changed recently. Review updates through the normal app route. If a firmware attempt fails, follow the T20 update guide with its charging and connection requirements.
Do not disconnect the station or restart the robot during an active firmware installation as a voice test. Wait for the update process to finish according to its instructions before repeating the same simple command.
After any software change, keep the test conditions similar. Changing the command, distance and room noise together makes the before-and-after result harder to interpret.
5. Keep a useful record for support
If the issue persists, send Ecovacs the wake-response result, exact command, app and firmware versions, connection status and any task alert. A short clip of one controlled attempt is more useful than a general report that voice control sometimes fails.
The manufacturer’s troubleshooting page also mentions resetting a persistent problem. Before taking that broader step, ask Ecovacs to confirm the applicable reset procedure and its effect on your setup. Keep your settings and map information available rather than using an uncertain button sequence.
Frequently asked questions
Should I use commands from an old online list?
Use the current list in ECOVACS HOME. It is the manufacturer’s reference for supported wording.
Does an acknowledged command prove the task can run?
No. Check the task result and any warning separately from the wake response.
Does silence prove a microphone fault?
No. Check the documented settings, connection and test conditions before asking support to assess hardware.
Find related checks in the Ecovacs troubleshooting hub.