How to Fix a Rerouting Sonoff eWeLink to Local MQTT
Smart home gear is supposed to simplify routines, not trap you in endless setup failures. If your Sonoff hub is not behaving the way the title describes, the issue is often a mismatch between the device, your hub, and your network — not a dead unit on arrival.
Before you factory-reset everything, follow these phases in order.
Safety first
This guide focuses on app, hub, and network troubleshooting. Do not open mains panels, defeat safety interlocks, or change line-voltage wiring unless you are a qualified professional.
Phase 1: Logs and backups
- Create or confirm a recent Home Assistant backup before changing YAML or integrations.
- Open Settings → System → Logs and capture the first error after restart.
- Note whether the issue began after a core, supervisor, add-on, or custom integration update.
Phase 2: Integration and network checks
- Reload the affected integration from the UI when supported.
- Validate YAML syntax before restarting if configuration files are involved.
- Check add-on logs separately from core logs for Docker, Supervisor, or MQTT issues.
Phase 3: Conservative recovery
- Restore the most recent working backup if the system fails after a change.
- Disable custom cards or integrations one at a time to find the trigger.
- Pin or roll back a custom integration only when its documentation recommends that path.
Phase 4: Verifying the fix
- Restart or reload only the affected integration and confirm the log no longer repeats the error.
- Trigger the related automation manually and confirm expected state changes.
- Recheck after one scheduled automation cycle or device polling interval.
Need more help?
Behavior can vary by model and firmware. Cross-reference Sonoff official support for your exact product before undocumented resets.
Check home-assistant.io integration pages and release notes for version-specific behavior.