- Subnet isolation
- mDNS/UDP blocked
- LAN mode disabled
Problem Description
When your SONOFF Sonoff Local Reachability 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
- LAN mode unreachable
- Cloud works only
- Local automations fail
Recognize these? Here's what usually causes it.
Common Causes
- Subnet isolation
- mDNS/UDP blocked
- LAN mode disabled
Most fixes happen in the first 3 steps.
Do not assume cloud success means local endpoint path is configured correctly.
Tools & Requirements
Step-by-Step Solution
Check local mode settings
Confirm local/LAN control is enabled for the device/integration path.
Validate same-subnet reachability
Ensure controller and device can communicate without isolation barriers.
Retest local automation path
Run local command tests with internet temporarily disconnected if applicable.
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.
Local control improves resilience when cloud access is degraded.
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.
- Subnet isolation
- mDNS/UDP blocked
- LAN mode disabled
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.





