Back to SwitchBot Guides
SwitchBot

Why Aren't My SwitchBot Hub 2 Blind Commands Reaching the Curtain Motor?

SwitchBot GuideSmart Blinds
easy difficulty 10-15 minutes 85 views 2 found helpful Where this fix applies: Global Updated
This guide applies to: SwitchBot SwitchBot Hub 2 (SwitchBot Hub 2, W3202100, SwitchBot Curtain 3)
At a glance — most common causes
  • Blind device out of Bluetooth range of the Hub
  • Hub too far from the blind device
  • Hub offline or on weak WiFi
10-15 minutes13 solutions coveredeasy level

Expert Review & Technical Scope

DeviceSwitchBot SwitchBot Hub 2
Model CoverageSwitchBot Hub 2, W3202100, SwitchBot Curtain 3
Fix Time10-15 minutes
DifficultyEasy
Required ToolsNo special tools required
Network / ProtocolBluetooth

Problem Description

Your SwitchBot Hub 2 is not delivering open and close commands to your SwitchBot Curtain motor. The SwitchBot app shows the command as sent but the curtain does not move. Direct Bluetooth control from your phone works when you are near the motor but Hub 2 commands from across the house fail. This is caused by the Hub 2 being too far from the Curtain motor to reach it with its IR or Bluetooth relay, or the Curtain not being fully paired to the hub.

Why This Happens in Real Homes

The Hub 2 controls blinds by relaying your WiFi command over Bluetooth to the Blind Tilt or Curtain — so a command that "doesn't reach" usually breaks on the Bluetooth hop, not the WiFi side. The blind device sits too far from the Hub, or its battery is low, so the Hub can't reach it reliably.

Bring the Hub within solid Bluetooth range of the blind device (the same room, ideally), make sure the Hub itself has strong 2.4GHz WiFi, and charge the blind device's battery. Re-link the device to the Hub if the association is stale, reduce Bluetooth interference between them, and keep both on current firmware. Shortening that Bluetooth hop is what makes remote blind control reliable.

Symptoms

  • Blind commands don't reach the blinds
  • Hub online but blinds don't move
  • Delayed or dropped commands
  • Works locally not remotely
  • Intermittent blind control via the Hub
  • Schedules don't fire
  • Blind shows offline through the Hub
  • Only some commands get through

Recognize these? Here's what usually causes it.

Common Causes

  • Blind device out of Bluetooth range of the Hub
  • Hub too far from the blind device
  • Hub offline or on weak WiFi
  • Blind device battery low
  • Bluetooth interference between Hub and device
  • Device not properly linked to the Hub
  • Firmware out of date
  • Too many devices straining the Hub's Bluetooth

Most fixes happen in the first 3 steps.

Warning

Do not pair one Curtain motor to two different Hub 2 units. Dual hub pairing causes command race conditions where both hubs attempt to control the motor simultaneously resulting in unpredictable behavior.

Recommended Tools for SwitchBot Hub 2

These tools will help you complete this fix.

As an Amazon Associate we earn from qualifying purchases.

Step-by-Step Solution

1

Pair Curtain to Hub 2 Properly

Bluetooth SwitchBot devices only relay through the Hub 2 when they are paired to that specific hub. Open the SwitchBot app and tap the Curtain device then go to Settings and look for Hub Device. Confirm Hub 2 is selected as the home hub for this curtain. If no hub is listed the curtain is operating in Bluetooth-only mode and only your phone can control it directly. Tap Hub Device and select your Hub 2 to enable remote and automation control through the hub.

2

Move Hub 2 Closer to Curtain

SwitchBot Hub 2 relays commands to curtain motors via Bluetooth with a maximum range of approximately 10 metres in open air. Walls reduce this to 5 to 7 metres. If the hub is in a different room or on a different floor from the curtain motor the relay signal may not reach. Move the Hub 2 to the same room as the curtain or to an adjacent room with a clear path. After moving the hub test curtain commands from the app.

3

Check Hub 2 WiFi Connection

The Hub 2 must have a stable WiFi connection to receive commands from the SwitchBot cloud when you control the curtain remotely. In the SwitchBot app go to Hub 2 settings and check the WiFi signal indicator. If the hub shows a weak WiFi connection or offline status it cannot receive commands even if its Bluetooth relay to the curtain is working. Improve WiFi signal at the hub location or move it to a better-connected position.

4

Update Hub 2 and Curtain Firmware

Open SwitchBot app, go to Hub 2 settings then Firmware and update to the latest version. Also go to the Curtain device settings and check for a firmware update. Hub-to-device Bluetooth relay protocols are updated regularly and a mismatch between Hub 2 firmware and Curtain firmware can cause commands to be rejected silently. After both updates power cycle the Hub 2 by unplugging it for 10 seconds before testing curtain control.

5

Charge Curtain Battery

SwitchBot Curtain 3 motors reduce Bluetooth reception sensitivity when the battery falls below 20 percent to extend remaining runtime. At low battery the curtain may receive some commands but ignore hub-relayed ones that have lower signal strength than direct phone Bluetooth. Charge the Curtain motor via USB until the battery indicator in the SwitchBot app shows 80 percent or above then retest hub commands.

Quick Solutions

Move the Hub closer to the blind device (Bluetooth range)
Ensure the Hub has strong 2.4GHz WiFi
Charge the blind device's battery
Reduce Bluetooth interference between them
Re-link the blind device to the Hub
Keep the Hub and device on updated firmware
Reposition to shorten the Bluetooth hop
Reduce the number of devices per Hub if overloaded

Still having issues? This is usually the deeper cause below.

If the hub reconnects then drops every few minutes, check for an IP conflict — two devices sharing the same DHCP address fight each other continuously.

Pro Tip

Use the SwitchBot scene feature to create morning and evening curtain automations through Hub 2. Hub-based automations run without your phone being present making them more reliable than phone-triggered shortcuts. **Product Intelligence:** - Hub 2 required for Matter - Hub Mini for basic Bluetooth/IR - Battery devices use CR2 or AAA

Real-World Insight

Hub disconnections that cycle repeatedly are almost always IP conflicts — two devices fighting over the same DHCP lease after a router restart.

What Usually Goes Wrong
  • Blind device out of Bluetooth range of the Hub
  • Hub too far from the blind device
  • Hub offline or on weak WiFi
  • Blind device battery low
  • Bluetooth interference between Hub and device
Best SwitchBot Hub 2 Options

Most popular upgrades chosen by SwitchBot Hub 2 owners.

As an Amazon Associate we earn from qualifying purchases.

Official Manufacturer Manual

If you need the complete manufacturer documentation for advanced setup, wiring diagrams, or detailed specifications, you can download the official manual below. The manual includes full technical instructions directly from the manufacturer and may help if your issue requires deeper troubleshooting.

Download the Official SwitchBot Hub 2 Manual

Source: 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.