Skip to main content

PyPI Python License Tests

pyskyrc

Pure-Python control and telemetry for SkyRC Q200neo / T1000 chargers via USB HID and Bluetooth LE.

Reverse-engineered from the official Charge Master 1.55.E207 protocol. No Charge Master or SkyRC app required.

Features

  • Two transports — USB HID and BLE with the same Python API.
  • 4 ports — A / B / C / D, each with independent telemetry.
  • Live cells — 6 × cell voltage, temperature, total V, delta.
  • Full control — START / STOP charge with full parameter set.
  • All chemistries — LiPo, LiIo, LiFe, LiHV, NiMH, NiCd, Pb.
  • Auto-discovery (BLE) — finds the charger by service UUID.
  • MAC cache — fast reconnect after first successful session.
  • Interactive shell — one connection, many commands.
  • Pure Python — only bleak needed for BLE; USB has no deps.

Install

pip install pyskyrc
pip install pyskyrc[ble]
pip install pyskyrc[ble,dev]

CLI

USB

pyskyrc info
pyskyrc status
pyskyrc monitor
pyskyrc start B --chem LiPo --cells 6 --current 2.0
pyskyrc stop B

BLE

pyskyrc --transport ble scan
pyskyrc --transport ble status
pyskyrc --transport ble start B --chem LiPo --cells 6 --current 2.0
pyskyrc --transport ble stop B

Interactive shell

pyskyrc --transport ble shell

Then inside the shell:

pyskyrc> status
pyskyrc> start B --chem LiPo --cells 6 --current 2.0
pyskyrc> monitor
pyskyrc> stop B
pyskyrc> exit

Python API

from pyskyrc import (
    SkyRCCharger, ChargeParameters, Port, Chemistry, LiMode,
)

with SkyRCCharger(transport="usb") as charger:
    for port, info in charger.read_telemetry().items():
        if info.has_battery:
            print(port.name, info.total_v, info.temperature_c)

    params = ChargeParameters(
        chemistry=Chemistry.LiPo,
        cells=6,
        mode=LiMode.BALANCE_CHARGE,
        charge_current_a=2.0,
    )
    charger.start_charge(Port.B, params)
    charger.stop_charge(Port.B)

For BLE, replace transport="usb" with transport="ble".

Protocol

Full protocol documentation is in docs/protocol.md.

Safety

This library controls a real charger with real current. You are responsible for choosing a chemistry and cell count that match your battery, choosing safe currents, and not leaving charging unattended.

License

MIT License — Copyright (c) 2026 Andreev Ivan.

See LICENSE for full text.

Author

Andreev Ivan — 2026

Metadata

Release files for pyskyrc 0.3.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 pyskyrc 0.3.0
File Size Uploaded
pyskyrc-0.3.0.tar.gz 26.6 kB Details

Built distribution (wheel)

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

Total release size: 54.0 kB

Release files / pyskyrc-0.3.0.tar.gz

Download URL pyskyrc-0.3.0.tar.gz
Size 26.6 kB
Tags Source
SHA-256 checksum
How to use checksums
ef2243206bb3a5a1bbd72653c06c3b7d3d70fbe9705039edb688231c998d4f75
BLAKE2b-256 checksum
How to use checksums
e61cec2e54c6af3ab81e48f689746573767d74a147df2b0edbe2c45e231233e1
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 Oct 7, 2026.

Transparency log

Release files / pyskyrc-0.3.0-py3-none-any.whl

Download URL pyskyrc-0.3.0-py3-none-any.whl
Size 27.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b462aebb7bf0051249238e6a962bf1e7b4868f37223bc87bd6f2b99ecf6428b3
BLAKE2b-256 checksum
How to use checksums
52a45a7798804d676fa6d3521af072b5defd1fc60b86e14513418aa0b528b21c
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 Oct 7, 2026.

Transparency log

Release history Release notifications | RSS feed

0.3.3

2 release files

0.3.2

2 release files

0.3.1

2 release files

This release

0.3.0 This release

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

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