Aqara and Xiaomi devices often travel farther than their original sales market. If you move countries or use imported hardware, changing an app’s region can affect the devices and services you see. It does not necessarily move those registrations to a new server.
The distinction matters in Home Assistant. An account-based integration follows the vendor’s regional registration; a device already paired directly to Zigbee2MQTT or ZHA belongs to your own Zigbee network. Changing a vendor app’s region should not alter that network membership. That is an inference from the documented connection paths, rather than a region-switch test on this site’s hardware.
This article covers an existing setup. For first-time pairing of a China-market device, including model IDs that can be mistaken for region lock, see the region-lock guide.
What “region” actually controls
Keep three settings separate: the country/region selected in an app, the regional server holding a device registration, and the market for which the hardware was sold. Changing the first does not guarantee migration of the second or compatibility of the third.
For Xiaomi Home, Xiaomi documents Profile → Settings → Region for changing the app’s country/region; labels can vary with app version. Its official support instructions use that setting when a device is missing from the app. This is not the same as changing every regional field attached to your Xiaomi account.
In an Aqara forum reply, a user is told that the same login can be used in another region by switching regions and signing in, with repeated switching needed to use both regional setups. That supports separate regional views, not a claim that switching automatically deletes or transfers all hubs. For an app workflow that differs on your phone, follow its current prompts and record the original region first.
Data-center geography is a related but separate question. Aqara’s app policy describes regional data handling; the EU store privacy policy covers a different service. Do not infer a device’s activation eligibility from a server’s physical location.
A region can also change the add-device catalog. The Thermostat E1 thread reports it missing from the Mainland China list, with W600 also mentioned by the original poster and Taiwan by another participant. These are dated reports of catalog visibility, not evidence that an already-paired Zigbee device outside the app will stop working.
What breaks: app links and hub hardware
A regional view can stop showing your existing devices. Xiaomi’s BE3600 Pro router FAQ distinguishes two actions: leaving its old registration alone, in which case changing back restores that regional view, or adding it under the new region, which clears its information from the original server. That is a documented example for this router, not a migration rule for every Xiaomi or Aqara device.
The older Mi Home walkthrough is additional reading. For a live migration, use the exact product’s current instructions. Do not reset or re-add every hub and child merely because the first screen looks empty. Check the original region before taking a step that removes a registration.
Hardware activation can be a separate restriction. Aqara’s Product Activation Region Policy ties supported activation regions to the original sales market. It lists Singapore-market products for Southeast Asia, for example, and warns that using products outside supported regions can limit functionality or service availability. An app dropdown does not override that policy.
Reports about mainland-China versus overseas hubs are useful leads, but do not establish one hard server-lock rule for every M100, M2 or M3 variant and firmware. The Singapore retailer’s warning about imported stock is retailer guidance. Confirm your exact model, sales market and destination with Aqara or the seller before relying on an account-region change.
Check its supported activation regions first. A new account region is not a guaranteed workaround for out-of-market hardware.
| What changes | Effect of a region switch | Touches Zigbee2MQTT/ZHA? |
|---|---|---|
| App-linked devices (Aqara Home / Mi Home) | May disappear from the selected region; actual migration or re-adding is a separate step | No, app layer only |
| Hub hardware (mainland-China vs. overseas units) | Activation and service support depend on the sales market and model | No, hub-to-cloud link only |
| Addable-device catalog in the app | Specific models can vanish from a region’s list | No, catalog visibility only |
| Scenes/automations built in the vendor app | Tied to the account and hub that created them | No, unless you route through that hub |
| Xiaomi Home integration in Home Assistant | Region setting must match where devices are registered | Not direct Zigbee; account/region dependency remains even where later control can be local |
| Devices already joined to Z2M/ZHA | None expected (site’s reasoning, not vendor-stated) | No vendor account in the path |
What doesn’t break: devices already on Zigbee2MQTT or ZHA
A direct Zigbee setup has a different connection path. Check the Zigbee2MQTT adapter settings or ZHA documentation: the sensor joins your coordinator rather than logging into an Aqara or Xiaomi account.
The join itself is covered in the region-lock article: it’s a radio-level handshake with your coordinator, and nothing in the documented flow contacts a vendor server. What matters for a region switch is what happens after the join. A Zigbee device is a member of one network at a time. Once it has joined Zigbee2MQTT or ZHA, its network membership sits between the device and your coordinator, and it isn’t connected to any Aqara or Xiaomi hub or account. Neither Zigbee2MQTT nor ZHA logs into a vendor account, so a region switch has no connection to break.
Region still matters for anything that keeps routing through the vendor’s own path. That includes commissioning through the official app (where catalog restrictions bite), scenes and automations built in the vendor app, push notifications, and cloud-hosted OTA delivery through the hub. It also includes one Home Assistant path: the official Xiaomi Home integration requires account authorization and a selected region, and devices registered in one region don’t appear under another. Its LAN/gateway control options do not remove that account and device-discovery dependency. A directly paired Zigbee entity has no vendor registration to migrate. The same local-layer logic runs through does Aqara work without internet and why discontinued Aqara/Xiaomi devices keep working locally: the local layer doesn’t ask the vendor’s cloud for permission to keep doing what it was already doing.
Before you switch: a practical checklist
- On the reasoning above, devices already paired to Zigbee2MQTT or ZHA need nothing done. No re-pairing, no config change tied to the account switch itself.
- Record app-linked devices, their original region, sharing and automations. Check the original regional view if the new one is empty; migrate or re-add only after checking the product-specific consequences.
- If you run the Xiaomi Home integration in Home Assistant, its cloud region has to match wherever the devices end up registered.
- If moving a hub, check its sales market, the official activation policy and current support for the destination. Record its model and firmware when asking about a restriction.
- Check the destination region’s addable-device list for any model you plan to add fresh after the switch. Availability isn’t guaranteed to match what you had before.
- If data handling is why you’re switching regions in the first place, read what Aqara’s 2026 privacy policy says about local mode and what the Xiaomi Home integration sends to the cloud versus what stays local alongside this.
FAQ
Can I switch my Aqara account from China to Global region?
The app offers regional sign-in, but changing the selected region is not an automatic migration of hubs or account data. Record the old setting, inspect the destination catalog and check the hub’s activation eligibility before moving its registration.
Does changing my Aqara or Mi Home region affect my Home Assistant setup?
It depends on the integration. Devices paired through Zigbee2MQTT or ZHA shouldn’t be affected, by this site’s reading of how Zigbee pairing works, because no vendor account is involved. The official Xiaomi Home integration is different: it logs into a regional Xiaomi cloud endpoint, so its region setting has to match where your devices are registered.
Will I lose my devices if I change my Xiaomi account region?
Devices may be absent from the new app-region view without having been erased. Returning to the original region is a useful first check. Resetting or re-adding a device is a separate operation with product-specific consequences. A device still joined directly to Z2M/ZHA should retain that membership unless you also reset or move it.
Are Aqara hubs locked to one region?
Aqara states that activation and use are supported within regions associated with the original sales market. Individual hub/server restrictions need checking for the exact model and firmware; do not turn a report about one unit into a universal rule.
Does Zigbee2MQTT care what region my Aqara account is set to?
No. Zigbee2MQTT and ZHA don’t authenticate against an Aqara or Xiaomi account at all. If a China-market device shows up as unsupported after it joins, that’s a model-identifier issue, not region, and the region-lock article covers it.
Evidence and limits
This is a comparison of documented connection paths and regional support, not a hardware region-switch test. Xiaomi’s support example distinguishes changing the app view from migrating a router registration. Aqara’s activation policy describes market eligibility, while its forum threads provide dated examples of regional views and catalog differences.
The expected independence of already-paired Zigbee2MQTT/ZHA devices follows from their account-free local connection. It is not a guarantee for a device you reset, move back to a vendor hub or control through an account-based integration. Record availability, last-seen times and one working sensor/control test before switching, then repeat the same checks afterwards. Preserve the existing Zigbee network and change one layer at a time.