How to Fix Sonoff Device Online but Not Responding in App
- App session token stale
- Device cloud heartbeat alive but command path broken
- Router latency/packet loss causing timeout
Problem Description
The Sonoff device appears online in eWeLink but command attempts fail or do not change physical state. This mismatch typically indicates cloud-command timeout, stale app session, firmware command queue issues, or router path instability.
Symptoms
- Device appears online but command fails
- App shows wrong on/off state
- Physical relay unchanged after tap
- Works locally then fails remotely
- Issue started suddenly
- Other devices unaffected
Recognize these? Here's what usually causes it.
Common Causes
- App session token stale
- Device cloud heartbeat alive but command path broken
- Router latency/packet loss causing timeout
- Firmware command processing bug
- Overloaded relay device under high load
- Account-device sync drift
Most fixes happen in the first 3 steps.
Do not trust dashboard state alone. Always confirm actual load behavior to avoid silent control failures in safety-critical automations.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Refresh application session
Sign out of eWeLink and sign back in, then retry commands. Online-but-unresponsive states are often tied to stale session/auth tokens where status heartbeat still appears but command acknowledgments fail.
Needed for this step
30A Hight Power WiFi Wireless Smart Switch, DIY...
$15.97Power-cycle and local test
Restart the Sonoff device and test immediate on/off command behavior. If the relay does not actuate locally after reboot, inspect load/wiring and hardware state before cloud diagnostics.
Cross-check from alternate client path
Issue commands from another phone or network path to determine if failure is client-specific or cloud/device-wide. If one client works and another fails, focus on app/cache/session cleanup on failing client.
Update firmware and retest queue
Apply stable firmware and app updates, then test repeated commands with delay between actions. Firmware bugs can cause stuck command queues where first action appears accepted but device state remains unchanged.
Rebind if mismatch persists
If online state remains but commands still fail after session and firmware checks, remove/rebind device cleanly in app to rebuild cloud command mapping. Validate with sustained control tests afterward.
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.
When diagnosing online-but-unresponsive issues, test one command at a time and verify physical relay state before issuing another command.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- App session token stale
- Device cloud heartbeat alive but command path broken
- Router latency/packet loss causing timeout
- Firmware command processing bug
- Overloaded relay device under high load
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.
