pySwitchbot 
Library to control Switchbot IoT devices https://www.switch-bot.com/
Setting up the environment
python3 -m venv .venv
source .venv/bin/activate
pip install .
Obtaining encryption key for Switchbot Locks
Using the script scripts/get_encryption_key.py you can manually obtain locks encryption key.
Usage:
$ python3 scripts/get_encryption_key.py MAC USERNAME
Key ID: XX
Encryption key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Where MAC is MAC address of the lock and USERNAME is your SwitchBot account username, after that script will ask for your password.
If authentication succeeds then script should output your key id and encryption key.
Troubleshooting key retrieval
Key retrieval talks to SwitchBot's account API with your username and password. The most common failures are account-side, not bugs in this library:
Authentication failed: ...— the username/password were rejected. This happens when:- Two-factor authentication (2FA) is enabled on the account. The API login used here does not support a verification code, so 2FA accounts cannot retrieve keys this way — temporarily disable 2FA, fetch the key, then re-enable it.
- The account was created via "Sign in with Apple"/Google and has no password set. Set a password in the SwitchBot app first, or use an email/password account.
- The username is an email but the account is registered to a phone number (or vice versa). Use the exact identifier you log in with.
Failed to retrieve encryption key from SwitchBot Account: ...— authentication succeeded but the key could not be read. Usually the account is not the device owner: keys are only returned to the owning account, not to shared/family members. Retrieve the key from the owner account, or transfer ownership in the app.
The key only needs to be fetched once; store the key_id and encryption key
and reuse them — there is no need to call the script on every connection.
Examples:
WoLock (Lock-Pro)
Unlock:
import asyncio
from switchbot.discovery import GetSwitchbotDevices
from switchbot.devices import lock
from switchbot.const import SwitchbotModel
BLE_MAC = "XX:XX:XX:XX:XX:XX" # The MAC of your lock
KEY_ID = "XX" # The key-ID of your encryption-key for your lock
ENC_KEY = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" # The encryption-key with key-ID "XX"
LOCK_MODEL = SwitchbotModel.LOCK_PRO # Your lock model (here we use the Lock-Pro)
async def main():
wolock = await GetSwitchbotDevices().get_locks()
await lock.SwitchbotLock(
wolock[BLE_MAC].device, KEY_ID, ENC_KEY, model=LOCK_MODEL
).unlock()
asyncio.run(main())
Lock:
import asyncio
from switchbot.discovery import GetSwitchbotDevices
from switchbot.devices import lock
from switchbot.const import SwitchbotModel
BLE_MAC = "XX:XX:XX:XX:XX:XX" # The MAC of your lock
KEY_ID = "XX" # The key-ID of your encryption-key for your lock
ENC_KEY = "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" # The encryption-key with key-ID "XX"
LOCK_MODEL = SwitchbotModel.LOCK_PRO # Your lock model (here we use the Lock-Pro)
async def main():
wolock = await GetSwitchbotDevices().get_locks()
await lock.SwitchbotLock(
wolock[BLE_MAC].device, KEY_ID, ENC_KEY, model=LOCK_MODEL
).lock()
asyncio.run(main())
WoCurtain (Curtain 3)
import asyncio
from pprint import pprint
from switchbot import GetSwitchbotDevices
from switchbot.devices import curtain
async def main():
# get the BLE advertisement data of all switchbot devices in the vicinity
advertisement_data = await GetSwitchbotDevices().discover()
for i in advertisement_data.values():
pprint(i)
print() # print newline so that devices' data is separated visually
# find your device's BLE address by inspecting the above printed debug logs, example below
ble_address = "9915077C-C6FD-5FF6-27D3-45087898790B"
# get the BLE device (via its address) and construct a curtain device
ble_device = advertisement_data[ble_address].device
curtain_device = curtain.SwitchbotCurtain(ble_device, reverse_mode=False)
pprint(await curtain_device.get_device_data())
pprint(await curtain_device.get_basic_info())
await curtain_device.set_position(100)
if __name__ == "__main__":
asyncio.run(main())
Release files for PySwitchbot 2.8.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pyswitchbot-2.8.0.tar.gz | 67.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyswitchbot-2.8.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 165.1 kB
Release files / pyswitchbot-2.8.0.tar.gz
| Download URL | pyswitchbot-2.8.0.tar.gz |
|---|---|
| Size | 67.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e489e2a0b68733728aba0920654120edb669c1a36bd01e265c265977e71ba232
|
|
BLAKE2b-256 checksum How to use checksums |
2cc6d8a53612e5703d83ff09d239c56725d3e5731f40b602139ff3afe0b29576
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency logRelease files / pyswitchbot-2.8.0-py3-none-any.whl
| Download URL | pyswitchbot-2.8.0-py3-none-any.whl |
|---|---|
| Size | 97.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
06312302b42ac05119c088cc5a483e69b668c81e3cd4c7f22f216d4372d9f130
|
|
BLAKE2b-256 checksum How to use checksums |
2b5ae150d08e4b2f09318a087dd8f0a3f730859eef24618e42eab5c80c76ef82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency log
