Why Did All My SwitchBot Devices Disappear After Changing Phones?
- SwitchBot lacks cloud sync for Bluetooth mesh device bindings
- New phone treats all local Bluetooth pairings as new devices
- Account logout clears locally cached device registration
Problem Description
After switching to a new phone or logging out and back into the SwitchBot app, all of your SwitchBot devices have disappeared from the device list. Bots, curtain motors, blind tilts, sensors, locks, and other accessories are all gone. Scenes and automations are deleted. The devices themselves still function on their last command — curtains stay where they are, plugs stay on or off — but you cannot control them from the app. This affects SwitchBot users who rely on Bluetooth mesh through the hub and is a known issue with how SwitchBot handles device-to-account binding.
Why This Happens in Real Homes
This is one of the most infuriating problems in the SwitchBot ecosystem and it hits people at the worst time — when they are excited about their new phone. You log into the SwitchBot app on your new iPhone or Android and your entire smart home is gone. Twenty devices, a dozen automations, all your curtain schedules — wiped. The devices themselves still work on their last command, so your curtains are not going to randomly open, but you have zero control until you re-pair everything. The root cause is that SwitchBot stores device binding data partially on your phone, not entirely in the cloud. Their cloud sync has improved but it is not complete. If you are setting up SwitchBot for a customer, enable cloud mode on the Hub and warn them to never log out of the app unnecessarily.
Symptoms
- Device list in SwitchBot app is completely empty after phone change
- Logging out and back in removed all paired devices
- Scenes and automations are deleted with no way to restore
- Devices still function on their last command but are uncontrollable
- Alexa and Google Home integrations show devices as unavailable
- Hub LED is normal but app says no devices are connected
Recognize these? Here's what usually causes it.
Common Causes
- SwitchBot lacks cloud sync for Bluetooth mesh device bindings
- New phone treats all local Bluetooth pairings as new devices
- Account logout clears locally cached device registration
- Hub firmware does not maintain independent device registry
- Cloud backup of device config is not automatic by default
- Switching between iOS and Android wipes platform-specific tokens
Most fixes happen in the first 3 steps.
Never log out of the SwitchBot app unless you absolutely have to. Logging out can clear your local device bindings even if you log back in with the same account.
Step-by-Step Solution
Understand what happened
SwitchBot devices pair via Bluetooth to your phone and register through the Hub to the cloud. But the device-to-account binding is partially stored locally on your phone, not entirely in the cloud. When you switch phones or log out, that local binding data is lost. The Hub knows the devices exist on its Bluetooth mesh, but the app on your new phone does not. SwitchBot has been working on improving cloud sync but as of 2026 it is still not reliable for full device state backup.
Re-pair devices one by one
Open the SwitchBot app on your new phone and make sure you are logged into the same account. Tap the plus icon to add devices. Your Hub should appear first — add it. Once the Hub is connected, some devices may automatically reappear if they were registered to your cloud account. For devices that do not reappear, you need to put each one into pairing mode and add it manually. SwitchBot Bot: press and hold the button on the top of the device for 2 seconds. Curtain 3: press the small reset button on the back of the motor unit once. This is tedious if you have 20 devices but there is no shortcut.
Rebuild scenes and automations
Scenes do not survive a device wipe because they reference specific device IDs that were cleared. You need to rebuild every scene and automation from scratch. If you had sunrise/sunset curtain automations, temperature-based fan triggers, or motion-activated lights, recreate them in the SwitchBot app under Scenes. Take a screenshot of your scene list on your old phone before switching if you still have access. If your old phone is already wiped, work from memory or check your Alexa/Google Home routines for clues about what automations you had.
Enable cloud backup for next time
In the SwitchBot app go to Profile > Settings and look for cloud sync or backup options. Enable everything available. As of 2026 the cloud backup covers Hub settings and some device configurations but not all scene logic. It is better than nothing. Also consider using the SwitchBot Hub in cloud mode rather than local Bluetooth mode — cloud mode maintains a server-side device registry that survives phone changes. The trade-off is slightly higher latency for commands.
Re-link voice assistants
After re-pairing the hubs, your Alexa and Google Home integrations will show them as unavailable. Open the Alexa app, go to the SwitchBot skill, unlink it, then re-link and run discovery. Same for Google Home — remove the SwitchBot integration and re-add it. Devices will appear with their original names if you used the same device names during re-pairing. If you changed any names, you will need to update your Alexa routines and Google Home automations to match.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Before switching phones, screenshot your complete device list and all scenes in the SwitchBot app. There is no automatic full backup yet.
Range tests in open air are useless for predicting real-world Z-Wave performance — a single concrete wall or appliance can cut effective range by more than half.
- SwitchBot lacks cloud sync for Bluetooth mesh device bindings
- New phone treats all local Bluetooth pairings as new
- Account logout clears locally cached device registration
- Hub firmware does not maintain independent device registry
- Cloud backup of device config is not automatic by
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by SwitchBot Hub owners.
SwitchBot Smart Automatic Curtain Opener with Solar Panel...
SwitchBot Thermometer Hygrometer & SwitchBot Hub Mini Sma...
SwitchBot Hub 2 (2nd Gen), work as a WiFi Thermometer Hyg...
As an Amazon Associate we earn from qualifying purchases.
Official Manufacturer Manual
SwitchBot provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your SwitchBot Hub.
Source: support.switch-bot.com
Need More Help? SwitchBot Support
Note: The contact information below connects you directly to SwitchBot's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
Accessories owners commonly pair with SwitchBot Hub.
Amazon Smart Plug, Works with Alexa, Simple Setup, Endles...
TP-Link WiFi Extender with Ethernet Port, Dual Band 5GHz/...
Kasa Smart Plug, Matter Compatible, Energy Monitoring, Co...
As an Amazon Associate we earn from qualifying purchases.
