How to Fix Sonoff Device Name Changes Not Syncing Across Apps
- Client cache stale
- Sync delay
- Partial account role visibility
Problem Description
SONOFF Sonoff Metadata Sync pairing failures follow a short list of causes — this guide works through them from most to least common.
Symptoms
- Old name persists
- Different names per client
- Automation shows outdated label
Recognize these? Here's what usually causes it.
Common Causes
- Client cache stale
- Sync delay
- Partial account role visibility
Most fixes happen in the first 3 steps.
Do not rename devices repeatedly before sync completes.
Tools & Requirements
These tools will help you complete this fix.
As an Amazon Associate we earn from qualifying purchases.
Step-by-Step Solution
Rename from primary account
Apply name updates from owner/admin account first.
Refresh all clients
Sign out/in or reload apps to fetch latest metadata.
Validate automation references
Ensure rules reference current device entity not stale label.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If pairing fails after multiple attempts, the device may still be registered to a previous account — factory-reset it before trying to add it to a new one.
Stable naming conventions reduce automation maintenance overhead.
Pairing failures almost always come down to distance during the initial handshake — manufacturers seriously understate how close you actually need to be.
- Client cache stale
- Sync delay
- Partial account role visibility
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.
