- cloud path latency
- weak WiFi signal
- device busy with reconnect/telemetry backlog
Problem Description
When your SONOFF Sonoff Command Latency isn't working as expected, it usually traces back to one of a small number of causes — this guide covers them in order, starting with the most likely.
Symptoms
- Slow on/off execution
- inconsistent delay
- local control faster than app
Recognize these? Here's what usually causes it.
Common Causes
- cloud path latency
- weak WiFi signal
- device busy with reconnect/telemetry backlog
Most fixes happen in the first 3 steps.
Do not assume app lag is always cloud-side without WiFi quality checks.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Measure command round-trip
Compare app tap time to physical relay action.
Check WiFi quality at device
Improve signal and reduce packet loss/retry behavior.
Retest under normal load
Validate improved latency consistency.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Command latency tuning should separate cloud delay from local RF issues.
Notification delays over 2 minutes are almost never the device's fault — background app restrictions quietly re-enable themselves after every OS update.
- cloud path latency
- weak WiFi signal
- device busy with reconnect/telemetry backlog
Before you go — try one of these (they fix most cases).
Need More Help? SONOFF Support
Note: The contact information below connects you directly to SONOFF's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.






