Skip to main content

pySwitchbot codecov

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 .

OAuth account access

pySwitchbot provides helpers for SwitchBot's authorization-code flow. The calling application supplies a SwitchBot-issued client ID and its registered redirect URI; neither value is tied to Home Assistant or embedded in the library.

SwitchBot currently treats these integrations as public clients: the token request does not use a client secret, and the authorization server does not support PKCE. The caller must generate an unpredictable, single-use state, store it for the duration of the flow, and reject callbacks whose state does not match. State protects the callback from request forgery but does not replace PKCE.

import secrets

from switchbot import (
    build_oauth_authorize_url,
    exchange_oauth_code,
    fetch_cloud_devices_by_token,
)

state = secrets.token_urlsafe(32)
authorize_url = build_oauth_authorize_url(client_id, redirect_uri, state)

# Store state before sending the user to authorize_url. On callback:
if callback_state != state:
    raise ValueError("OAuth state mismatch")

token = await exchange_oauth_code(
    session,
    client_id,
    redirect_uri,
    authorization_code,
)
devices = await fetch_cloud_devices_by_token(session, token["access_token"])

The client ID and exact HTTPS redirect URI must be registered with SwitchBot; arbitrary values and wildcard redirect URIs will not work. exchange_oauth_code returns the provider's token mapping after validating the access token and normalizing expires_in to an integer. The access token can then be passed to fetch_cloud_devices_by_token or SwitchbotEncryptedDevice.async_retrieve_encryption_key_by_token.

HTTP 401 and 403 responses from the SwitchBot account API raise SwitchbotAuthenticationError. Other API failures raise SwitchbotApiError, while transport and availability failures raise SwitchbotAccountConnectionError.

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.
  • ..., status code: 190 (SwitchbotApiError) — 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.9.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for PySwitchbot 2.9.0
File Size Uploaded
pyswitchbot-2.9.0.tar.gz 71.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for PySwitchbot 2.9.0
File Interpreter ABI Platform
pyswitchbot-2.9.0-py3-none-any.whl Python 3 none any Details

Total release size: 173.4 kB

Release files / pyswitchbot-2.9.0.tar.gz

Download URL pyswitchbot-2.9.0.tar.gz
Size 71.5 kB
Tags Source
SHA-256 checksum
How to use checksums
bb64e02ee2003a06d24787de371eec8de381714734666278c18510b8bcc1ba54
BLAKE2b-256 checksum
How to use checksums
ce4aec237ddff9e3caa7b40b08e4fc815865507f1ebc0d52530cc01722c49607
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 15, 2026.

Transparency log

Release files / pyswitchbot-2.9.0-py3-none-any.whl

Download URL pyswitchbot-2.9.0-py3-none-any.whl
Size 101.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
73b8accdb86fc0fdcced67151e1807ad521e29b86d0d5a176161b0ee57fc43a2
BLAKE2b-256 checksum
How to use checksums
866abb6dc5e31c37ecb2f5311a789d5e7a33ca893b822837e4bcdf8185ef2918
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 15, 2026.

Transparency log

Release history Release notifications | RSS feed

2.10.0

2 release files

2.9.1

2 release files

This release

2.9.0 This release

2 release files

2.8.0

2 release files

2.7.1

2 release files

2.7.0

2 release files

2.6.0

2 release files

2.5.0

2 release files

2.4.1

2 release files

2.4.0

2 release files

2.3.0

2 release files

2.2.0

2 release files

2.1.0

2 release files

2.0.1

2 release files

2.0.0

2 release files

1.1.0

2 release files

1.0.0

2 release files

0.75.0

2 release files

0.74.0

2 release files

0.73.0

2 release files

0.72.1

2 release files

0.72.0

2 release files

0.71.0

2 release files

0.70.0

2 release files

0.69.0

2 release files

0.68.4

2 release files

0.68.2

2 release files

0.67.0

2 release files

0.64.1

2 release files

0.64.0

2 release files

0.63.0

2 release files

0.62.2

2 release files

0.62.1

2 release files

0.60.1

2 release files

0.60.0

2 release files

0.58.0

2 release files

0.57.1

2 release files

0.56.1

2 release files

0.56.0

2 release files

0.55.4

2 release files

0.55.3

2 release files

0.55.2

2 release files

0.55.1

2 release files

0.55.0

2 release files

0.54.0

2 release files

0.53.2

2 release files

0.53.0

2 release files

0.52.0

2 release files

0.51.0

2 release files

0.50.1

2 release files

0.50.0

2 release files

0.49.0

2 release files

0.48.2

2 release files

0.48.1

2 release files

0.48.0

2 release files

0.47.2

2 release files

0.46.1

2 release files

0.46.0

2 release files

0.45.0

2 release files

0.44.1

2 release files

0.44.0

2 release files

0.42.0

2 release files

0.41.0

2 release files

0.40.1

2 release files

0.40.0

2 release files

0.39.1

2 release files

0.39.0

2 release files

0.38.0

2 release files

0.37.5

2 release files

0.37.4

2 release files

0.37.3

2 release files

0.37.2

2 release files

0.37.1

2 release files

0.37.0

2 release files

0.36.4

2 release files

0.36.0

2 release files

0.35.0

2 release files

0.34.1

2 release files

0.34.0

2 release files

0.33.0

2 release files

0.32.1

2 release files

0.32.0

2 release files

0.31.0

2 release files

0.30.1

2 release files

0.30.0

2 release files

0.29.1

2 release files

0.29.0

2 release files

0.28.0

2 release files

0.27.1

2 release files

0.27.0

2 release files

0.26.3

2 release files

0.26.2

2 release files

0.26.1

2 release files

0.26.0

2 release files

0.25.0

2 release files

0.24.0

2 release files

0.23.2

2 release files

0.23.1

2 release files

0.23.0

2 release files

0.20.5

2 release files

0.20.4

2 release files

0.20.3

2 release files

0.20.2

2 release files

0.20.1

2 release files

0.20.0

2 release files

0.19.9

2 release files

0.19.8

2 release files

0.19.7

2 release files

0.19.6

2 release files

0.19.5

2 release files

0.19.4

2 release files

0.19.3

2 release files

0.19.2

2 release files

0.19.1

2 release files

0.18.9

2 release files

0.18.8

2 release files

0.18.7

2 release files

0.18.6

2 release files

0.18.5

2 release files

0.16.0

2 release files

0.15.2

2 release files

0.15.1

2 release files

0.15.0

2 release files

0.14.1

2 release files

0.14.0

2 release files

0.13.3

2 release files

0.11.0

2 release files

0.10.0

2 release files

0.9.1

2 release files

0.9.0

2 release files

0.8.0

1 release file

0.7.0

1 release file

0.6.2

1 release file

0.6.1

1 release file

0.6

1 release file

0.5

1 release file

0.4

1 release file

0.3

1 release file

0.2

1 release file

0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page