- Cloud sync delay
- App cache holding the old name
- Not logged into the same account
Problem Description
You renamed a SONOFF device in the eWeLink app, but the old name still appears in Alexa, Google Home, or Home Assistant. Or you renamed it in Alexa but eWeLink still shows the original name. Device names are stored separately in each platform — renaming in one does not automatically propagate to others. This affects voice commands because Alexa and Google respond to the name stored in their own system, not the eWeLink name.
Why This Happens in Real Homes
A SONOFF name change not syncing across apps is a cloud-sync or cache issue — the rename saved to your account but hasn't propagated to another phone yet, or that phone is showing a cached copy. It's cosmetic and resolves once everything re-syncs.
Give cloud sync a moment and pull to refresh on the other device, and clear the app cache there if it's holding the old name. Make sure every app is logged into the same eWeLink account and is up to date. Rename while the device is online so the change syncs promptly, and have shared users refresh or re-log in. The name settles across all apps once they pull the latest from the cloud.
Symptoms
- Renamed device doesn't sync
- Old name on other devices/apps
- Name change not reflected
- Different names across phones
- Rename not saving
- Name reverts
- Inconsistent naming
- Sync delay on rename
Recognize these? Here's what usually causes it.
Common Causes
- Cloud sync delay
- App cache holding the old name
- Not logged into the same account
- Offline device / delayed sync
- App out of date
- Session issue
- Shared users not refreshed
- Editing while offline
Most fixes happen in the first 3 steps.
Do not rename devices repeatedly before sync completes.
Tools & Requirements
Step-by-Step Solution
Understand where device names live
When you rename a SONOFF device in eWeLink, that name is stored on SONOFF's cloud servers and syncs to all phones logged into the same eWeLink account. But third-party integrations (Alexa, Google Home, Home Assistant) pull the name once during linking — they do not auto-sync name changes. So renaming in eWeLink does not automatically rename the device in Alexa or Google Home. You need to update the name in each platform separately.
Rename in eWeLink first
Open eWeLink, tap the device, tap the device name at the top of the screen, and type the new name. Tap Save. This updates the name on SONOFF's cloud. If you have eWeLink installed on multiple phones under the same account, pull down to refresh the device list on each phone — the new name should appear within a few seconds. If a shared user (family member) has a different eWeLink account with device sharing, they need to pull-to-refresh their device list too.
Update the name in Alexa
Alexa stores its own copy of device names. After renaming in eWeLink: open the Alexa app > Devices > find the SONOFF device (it still shows the old name). Tap it > tap the gear icon > Edit Name. Type the new name and save. You can also say 'Alexa, discover my devices' to force a re-sync, but this only adds new devices — it does not rename existing ones. The Alexa app is the only way to rename an existing device.
Update the name in Google Home
Google Home also maintains its own device names. Open Google Home > tap the SONOFF device > tap the gear icon (Settings) > Name > type the new name > Save. Google Home does re-sync device attributes periodically, but names are user-set in Google Home and do not auto-update from eWeLink. If you unlink and relink the eWeLink service in Google Home, it reimports all devices with their current eWeLink names — but you lose any Google Home room assignments.
Update names in Home Assistant if using eWeLink integration
If you use the eWeLink Smart Home or SonoffLAN integration in Home Assistant: entity names are set at first discovery and do not auto-rename. Go to Settings > Devices & Services > find the SONOFF device > click the entity > tap the gear icon > change the Name field. The entity_id does not change when you rename — only the friendly_name updates. If you need the entity_id to match, you must delete and re-add the entity, which breaks any automations referencing the old entity_id.
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.
- Cloud sync delay
- App cache holding the old name
- Not logged into the same account
- Offline device / delayed sync
- App out of date
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by Sonoff Metadata Sync owners.

SONOFF MINI Duo (Matter Over WiFi) 2 - Channel WiFi Smart...

SONOFF Zigbee Smart USB Outlet, 5-22V DC Outlet Timer Sma...
As an Amazon Associate we earn from qualifying purchases.
Official Manufacturer Manual
SONOFF provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Sonoff Metadata Sync.
Source: sonoff.tech
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.
Accessories owners commonly pair with Sonoff Metadata Sync.

SONOFF Zigbee 3.0 USB Dongle Plus Gateway, Universal Zigb...

SONOFF Zigbee 3.0 USB Dongle Plus-E Gateway, Universal Wi...

SONOFF Zigbee Indoor Temperature Humidity Sensor, SNZB-02...
As an Amazon Associate we earn from qualifying purchases.




