Changing a control device or moving to a new apartment often puts smart home owners in need of reconfiguration of the network. In the Xiaomi ecosystem, the process of binding sensors, lamps and sockets is rigidly tied to a particular gateway or account, which creates certain difficulties during migration. Users often face a situation when gadgets simply stop responding after changing the main router or smartphone.
Technically, the Gateway acts as a bridge between local communication protocols like ZigBee or Bluetooth and the WAN. If you change your phone but leave the same account and region, the process is usually transparent. However, when you replace the hub itself or move devices to a completely new account, you need a complete reassignment, and ignoring the right steps will cause the smart home system to cease to function.
In this guide, we will take a look at all the nuances of the procedure, including hidden server settings and regional work, and learn why simply changing your Wi-Fi router may not be enough and how to properly prepare your devices for the โmoveโ. It is important to understand the architecture of Mi Home to avoid data loss and the need to buy new sensors.
Preparation of equipment and account before migration
Before any manipulations begin, you need to make sure that all the components of the system are ready to work. Often problems arise due to trivial mismatch of software versions or regional settings. Make sure that the new gateway or smartphone that will become the control center is connected to a stable Wi-Fi network at a frequency of 2.4 GHz. Five-gigahertz networks are often not supported by budget smart home communication modules.
The critical step is to check the region in the Mi Home app. All devices added to the account must be in the same region as the gateway. If you used the China server before and now want to switch to Europe or Russia, you will have to add all devices again. Changing the region in the application settings will hide all previously added gadgets, but will not delete them from the server.
- ๐ฑ Install the latest version of the Mi Home app from the official store or manufacturerโs website.
- ๐ Make sure your Wi-Fi router is distributing a network at 2.4GHz and does not use only 5GHz modeยป.
- ๐ Check the battery charge in the sensors, as the re-binding process is energy intensive.
- ๐ Write it down. MAC-Addresses of critical devices in case of synchronization failure.
Also, you should prepare the new gateway for work in advance. If this is a Xiaomi Gateway 3 or a newer model, make sure that it is reset to factory settings. This will eliminate configuration file conflicts. To reset, it is usually enough to pinch the reset button on the device body for 5-10 seconds before the characteristic audible signal or flashing of the indicator.
Detachment process from old gateway
The first step in the migration process is to remove devices from the old system correctly. Just turning off the old gateway is not enough - the devices will remain locked on the old account or in the memory of the old hub. Go to the Mi Home app, select the desired device and go to the settings (three dots in the upper right corner).
Once confirmed, the device will go to pairing standby. However, some sensor models can store the old encryption keys. In this case, a hardware reset is required. For most motion sensors and doors, this is done by pressing the reset button five times quickly. The indicator should light up blue or start flashing quickly, signaling readiness for pairing.
โ ๏ธ Note: When you remove a device from an application, all scripts and automation created for it are automatically deleted. Before reset, it is recommended to take screenshots of complex logical chains to recreate them on a new gateway.
If you only change your phone and leave your account, you don't have to delete your devices. Just log in to Mi Home on a new device, and all the gadgets will be pulled up from the cloud server. The problems arise when you change the physical gateway or the region of your account, and in such cases, completely clearing the list of devices is the only reliable way to avoid synchronization errors.
โ๏ธ Checklist before resetting devices
Set up a new gateway and add devices
Once the old configuration is cleared, you can start deploying the new network. Connect the new gateway to the power grid and wait until the indicator flashes orange to indicate the connection standby mode. In the Mi Home app, click + and select automatic device search. The system must detect the gateway on the local network.
As you configure the gateway, you'll be asked to select a region. The region you select determines the physical location of the server where your device data will be stored, and it can't be changed without re-registering all the gadgets. Once the gateway is successfully added to the system, it will update its firmware. Don't interrupt this process, as this can lead to a software failure.
You can now add peripherals. Put the sensor in pairing mode (usually 5 quick presses) and bring it close to the gateway (no more than 1-2 meters away). The app will start finding and installing the connection. Once successfully added, you can assign a name to the device and assign a room.
| Type of device | Resetting method | Indication of success | Mating distance |
|---|---|---|---|
| Motion sensor | 5 quick presses | Blue flashing | < 1 meter |
| Smart socket | 5-7 sec retention | Fast blinking. | < 2 meters |
| Temperature sensor | Pressing the button 1 time | Blinking of the indicator | < 1 meter |
| Yeelight light bulb | 5 on/off | Light pulsation | < 3 meters |
For some devices, especially those running ZigBee 3.0, it's important to add them sequentially, waiting for each previous one to be confirmed. Massive addition can cause the gateway buffer to overflow, causing connection errors. If the device isn't there, try holding it close to the gateway antenna.
What if the gateway does not see the device?
Solving problems with regions and servers
One of the most common problems with porting is regional incompatibility: Devices purchased in China (CN version) may not be added to the Russia or Europe region without additional manipulation. At the same time, global versions (Global) work perfectly in all regions. If you encounter the error "Device cannot be added to this region", check the labeling on the box.
There is a technique for forcing Chinese devices to be added to a European server by changing the region in the application, but it works unstable and depends on the version of the gateway firmware. A more reliable way is to create a second account with the China region and add devices there, but then they will not be visible in the main automation system along with European devices.
If you do decide to change your primary account region, remember the consequences: all device history data accumulated over the years will be lost; voice assistants may also stop working if they were tied to a specific region; XiaoAI and Google Assistant have different lists of supported commands in different zones.
- ๐จ๐ณ China: full functionality, support for all devices, but the interface is partly in English/Chinese.
- ๐ช๐บ Europe/Russia Region: Full Localization, Compliance GDPR, Limited list of supported devices.
- ๐บ๐ธ US: similar to European region, but with other servers and communication delays.
For advanced users, third-party gateways such as the Home Assistant with Xiaomi Gateway 3 integration are available, allowing devices from different regions to be integrated into a single local area network, bypassing cloud constraints, but this requires a separate server (such as the Raspberry Pi) and technical expertise.
๐ก
Use the shortcuts on the Mi Home app desktop to quickly switch between accounts from different regions if you have devices from different zones.
Automation and post-transfer scenarios
Once all devices are successfully migrated to the new system, you need to restore the logic of the smart home. Unfortunately, cloud scripts don't automatically migrate between different gateways or accounts. You'll have to recreate them manually. This is a great opportunity to optimize old scenarios without unnecessary delays or idle conditions.
When you create new automations, look at the type of trigger. Local scenarios (executed by the gateway or hub itself) are faster and more stable than cloud ones. If you have a Xiaomi Multimode Gateway installed, try to create scenarios that do not require access to the Internet, such as โIf the door opener worked โ Turn on the lightsโ, which will ensure the system will work even if the channel breaks into the external network.
โ ๏ธ Note: When recreating time-based scenarios (e.g., โat 20:00, turn off the lightsโ), make sure that the new gateway or phone is correctly timed. Time-distorting can trigger automation at an unforeseen moment.
Remember to check notifications. After porting your devices, push notifications may be disabled by default. Go to the settings of each sensor and make sure that the Send Notification option is active. Also check the Do Not Disturb settings in the Mi Home app itself to keep important signals from the security sensors.
๐ก
Local scenarios run faster than cloud scenarios and work without the Internet, so prioritize setting up automation at the gateway level.