Battery Circulator Fan: turnOn command succeeds via API but device does not physically respond #503

Current Situation

Summary

Sending a turnOn command to a Battery Circulator Fan via the Open API returns a
success response (statusCode: 100), but the physical device does not turn on.

Manual control works fine in both of the following cases:

• Pressing the physical power button on the device
• Controlling the device directly from the SwitchBot app via Bluetooth (phone next to the device)

So the device itself, its battery, and its Bluetooth radio all appear to be working normally.
Only commands sent through the cloud API fail to reach the device.

Device

• Device type: Battery Circulator Fan
• deviceId: B0E9FEE4674A
• Power: connected to AC power (not running on battery)

API request used

POST https://api.switch-bot.com/v1.0/devices/B0E9FEE4674A/commands
Authorization: <token>
Content-Type: application/json
{
 "command": "turnOn",
 "parameter": "default",
 "commandType": "command"
}

Response received:

{
 "statusCode": 100,
 "message": "success"
}

Despite the success response, the fan does not turn on.

Troubleshooting steps already taken

1. The device was originally linked to a plain Hub Mini (non-Matter). I noticed that
   hub's enableCloudService field was false in the /v1.0/devices response.

2. I factory-reset that hub and reconnected it to Wi-Fi. enableCloudService became true,
   but the turnOn command to the Battery Circulator Fan still returned success without any
   physical effect.

3. Since the product page states that cloud automation for the Battery Circulator Fan requires
   a Hub 2, Hub 3, or a Matter-enabled Hub Mini, I factory-reset the Battery Circulator Fan
   itself and re-paired it near a Matter-enabled Hub Mini (a different hub on the same account).

4. After re-pairing, /v1.0/devices correctly showed the fan's hubDeviceId updated to the
   Matter-enabled hub's device ID.

5. Even so, the turnOn command still returns success but the fan does not physically turn on.

Question

• Is there a known issue or limitation with cloud-command delivery to the Battery Circulator
  Fan, even when it is paired with a Matter-enabled hub?
• Are there any additional requirements (hub firmware version, device firmware version, account
  region, etc.) needed for turnOn/turnOff commands to actually reach this device?

Environment

• SwitchBot app: latest version
• Connected hub: Hub Mini2 (Matter-enabled)
• Network: Wi-Fi 2.4GHz, hub has a valid local IP and strong signal

Logs

Request:
POST https://api.switch-bot.com/v1.0/devices/B0E9FEE4674A/commands
{"command": "turnOn", "parameter": "default", "commandType": "command"}
Response:
{"statusCode": 100, "message": "success"}
No error is returned, but the device does not physically turn on.

Configuration

OS: N/A (cloud-based, Google Apps Script runtime)
Software: Google Apps Script (V8 runtime)
Node: N/A
npm: N/A

Environment

SwitchBot app: latest version
Connected hub: Hub Mini2 (Matter-enabled)
Network: Wi-Fi 2.4GHz, hub has a valid local IP and strong signal

Additional Context

No response