smartblinds-ble 0.1.0__tar.gz

smartblinds_ble-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,28 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install (with dev extras)
+        run: pip install -e ".[dev]"
+      - name: Lint
+        run: ruff check .
+      - name: Test
+        run: pytest -q

smartblinds_ble-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,38 @@
+name: Release
+
+# Publishes to PyPI via Trusted Publishing (OIDC) when a version tag is pushed.
+# One-time PyPI setup (https://pypi.org/manage/account/publishing/):
+#   PyPI project name: smartblinds-ble
+#   Owner: benbalter   Repository: smartblinds-ble
+#   Workflow name: release.yml   (leave Environment blank)
+# Then: git tag v0.1.0 && git push origin v0.1.0
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  pypi:
+    name: Build and publish to PyPI
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write # required for Trusted Publishing
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+      - name: Build sdist and wheel
+        run: |
+          python -m pip install --upgrade build
+          python -m build
+      - name: Verify version tag matches pyproject
+        run: |
+          TAG="${GITHUB_REF_NAME#v}"
+          PKG=$(ls dist/*.whl | sed -E 's/.*smartblinds_ble-([0-9.]+)-.*/\1/')
+          echo "tag=$TAG wheel=$PKG"
+          test "$TAG" = "$PKG"
+      - uses: pypa/gh-action-pypi-publish@release/v1

smartblinds_ble-0.1.0/.gitignore

@@ -0,0 +1,34 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.venv/
+venv/
+env/
+
+# Tooling
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+
+# Exported BLE keys (secrets) from the cloud importer — never commit
+smartblinds-keys.json
+*-keys.json
+
+# Captured cloud traffic (redacted, but still contains emails/MACs/room names)
+tilt-capture/
+*.pklg
+*.pcap
+
+# Editors / OS
+.DS_Store
+.vscode/
+.idea/
+
+# Local Tilt pairing keys for the in-room gate check — never commit.
+keys/
+*.key
+keys.json

smartblinds_ble-0.1.0/CLAUDE.md

@@ -0,0 +1,86 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## What this is
+
+Local, hub-free & cloud-free BLE control of **MySmartBlinds / Tilt** shade motors, so
+they keep working after the (winding-down) vendor cloud dies. Two layers: this
+`smartblinds-ble` async, `bleak`-based Python library, and a planned
+`ha-smartblinds-ble` HACS integration (separate repo). Unofficial, not affiliated
+with the vendor. Apache-2.0; a modern async port of `dnschneid/pysmartblinds` (see
+`NOTICE`).
+
+## ⚠️ M0 gates everything
+
+The BLE protocol here was reverse-engineered in 2018 (legacy MySmartBlinds, firmware
+2.0) and is **UNVERIFIED on current hardware**. The constants in `const.py` and the
+GATT writes in `blind.py` are a *hypothesis*, marked as such. Do not describe them as
+working. `docs/ROADMAP.md` Milestone 0 = confirm connect + key + tilt-write on a real
+shade before any packaging/publishing. Everything downstream is contingent on M0.
+
+## Commands
+
+- Install (dev): `pip install -e ".[dev]"`
+- Test: `pytest -q` — single: `pytest tests/test_protocol.py::test_set_tilt_writes_key_then_position`
+- Lint (the CI gate): `ruff check .`
+  - CI deliberately does **not** run `ruff format --check` — this ruff version
+    reformats Python inside markdown code blocks, which is brittle for the docs.
+- Run a tool without installing (src/ layout needs the path): `PYTHONPATH=src python -m smartblinds_ble.tools.find_key`
+- CLIs (`[project.scripts]`): `smartblinds-find-key` (BLE brute-force key discovery),
+  `smartblinds-import-cloud` (legacy-cloud key export; flags `--debug`,
+  `--include-deleted`, `--token`).
+- CI: `.github/workflows/ci.yml` runs `ruff check` + `pytest` on Python 3.11/3.12/3.13.
+
+## Architecture
+
+- `blind.py` — `SmartBlind`, the async `bleak` client. Takes a `BLEDevice` (not just an
+  address) so connections route through Home Assistant / ESPHome Bluetooth proxies.
+  Every op: connect → write key (handle `0x001b`) → write a position byte 0–200 (handle
+  `0x001f`) → disconnect. **Open-loop**: motors don't report state (reads return
+  `0xFF`), so `position` is tracked optimistically — the eventual HA cover must be
+  `assumed_state`.
+- `const.py` — protocol constants, all flagged UNVERIFIED. `scanner.py` — discover
+  `SmartBlind_DFU` devices.
+- `cloud.py` + `tools/import_cloud.py` — **optional** (`[cloud]` extra) key export from
+  the vendor cloud, isolated so the core stays cloud-free. See "Two backends" below.
+- `tools/find_key.py` — cloud-independent BLE brute-force of the first key byte.
+- `contrib/mitm_tilt_addon.py` — mitmproxy addon for reversing the Tilt cloud API;
+  auto-redacts secrets, writes `tilt-capture/`.
+- `docs/` — `PROTOCOL.md` (RE'd protocol), `ROADMAP.md` (M0-gated milestones),
+  `CAPTURE.md` (definitive field notes for capturing the protocol; read before
+  attempting either a network-MITM or BLE capture).
+
+## Two backends / device generations (critical, non-obvious)
+
+The hardware split into two ecosystems that do **not** share a data backend:
+
+- **Legacy "MySmartBlinds"** → cloud `api.mysmartblinds.com` (GraphQL). `cloud.py`
+  targets this. Key is short (first byte often suffices → brute-forceable). BLE is
+  plaintext (`0x001b`/`0x001f`).
+- **Newer "Tilt"** → cloud `api.tiltsmarthome.com/v2/store/tilt`. **Same Auth0 tenant**
+  (`mysmartblinds.auth0.com`), so a legacy login *succeeds* but returns 0 devices for
+  Tilt users. Store: `rooms[].rollerShades[]`/`bridges[]`, each `{id = BLE MAC, name,
+  pairingKey}`; `pairingKey` is 32 bytes → Tilt BLE is likely **encrypted/authenticated**,
+  unlike the legacy protocol. Use `access_token` (id_token → 401).
+
+Implications: `cloud.py` only serves *legacy* accounts. Tilt devices need the Tilt API
+(different Auth0 client_id `Owjr4yOJ2H…`, not yet built) or BLE. The **Tilt bridge is a
+cloud-only AWS IoT MQTT client with no local API** (verified: all ports closed) — it is
+**not** a local control path. Direct BLE is the only durable local path.
+
+## Conventions / gotchas
+
+- **ruff broad-except**: an `except Exception` that **re-raises** must NOT have
+  `# noqa: BLE001` (RUF100 flags it unused); one that swallows / `sys.exit`s **must**.
+  `BLE001` is enabled here; `PLC0415` (lazy import) is not.
+- `__all__` must be sorted per RUF022 (SCREAMING_SNAKE, then CamelCase, then lowercase;
+  alphabetical within each group).
+- **Cloud dep**: PyPI `smartblinds-client` is stale (0.6, 2019; won't log in). Install
+  the docBliny fork from git; the `[cloud]` extra pin is a floor only (a git URL can't
+  live in a PyPI-published extra).
+- **Secrets**: `*-keys.json` and `.pklg`/`.pcap` traces contain keys; `tilt-capture/`
+  is redacted but still holds emails/MACs/room names — all gitignored, keep them out.
+- **Python**: `requires-python >=3.11`; the `type X = Y` statement (3.12+) breaks older
+  parsers — avoid it.
+- Not on PyPI yet — install from git. Publishing (final name + PyPI) waits for M0.

smartblinds_ble-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+

smartblinds_ble-0.1.0/NOTICE

@@ -0,0 +1,35 @@
+smartblinds-ble
+Copyright 2026 Ben Balter and contributors
+
+This product includes software derived from pysmartblinds
+(https://github.com/dnschneid/pysmartblinds), Copyright 2018 The pysmartblinds
+authors, licensed under the Apache License, Version 2.0.
+
+The smartblinds_ble.tilt subpackage (the Tilt-era encrypted protocol codec and
+BLE transport) is vendored from tilt-local-bridge
+(https://github.com/Sunrise-Labs-Dot-AI/tilt-local-bridge), Copyright (c) 2026
+Sunrise Labs, licensed under the MIT License. protocol.py is kept byte-for-byte;
+ble.py adapts only the TiltShadeClient entry point. The MIT license terms:
+
+    Permission is hereby granted, free of charge, to any person obtaining a copy
+    of this software and associated documentation files (the "Software"), to deal
+    in the Software without restriction, including without limitation the rights
+    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+    copies of the Software, and to permit persons to whom the Software is
+    furnished to do so, subject to the following conditions:
+
+    The above copyright notice and this permission notice shall be included in
+    all copies or substantial portions of the Software.
+
+    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+    SOFTWARE.
+
+The BLE protocol details were reverse-engineered without any knowledge of the
+internal workings of MySmartBlinds / Tilt products. This project is not
+affiliated with, authorized by, or endorsed by MySmartBlinds or Tilt. Those names
+are used only to describe the hardware this software interoperates with.

smartblinds_ble-0.1.0/PKG-INFO

@@ -0,0 +1,192 @@
+Metadata-Version: 2.5
+Name: smartblinds-ble
+Version: 0.1.0
+Summary: Local, hub-free async BLE control of MySmartBlinds/Tilt shade motors
+Project-URL: Homepage, https://github.com/benbalter/smartblinds-ble
+Project-URL: Issues, https://github.com/benbalter/smartblinds-ble/issues
+Author: Ben Balter
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: ble,blinds,bluetooth,home-assistant,mysmartblinds,tilt
+Requires-Python: >=3.11
+Requires-Dist: bleak-retry-connector>=3.5
+Requires-Dist: bleak>=0.22
+Requires-Dist: cryptography>=42
+Provides-Extra: cloud
+Requires-Dist: smartblinds-client>=0.6; extra == 'cloud'
+Provides-Extra: dev
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.5; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# smartblinds-ble — local control for MySmartBlinds / Tilt smart blinds (no hub, no cloud)
+
+[![CI](https://github.com/benbalter/smartblinds-ble/actions/workflows/ci.yml/badge.svg)](https://github.com/benbalter/smartblinds-ble/actions/workflows/ci.yml)
+
+Keep your **MySmartBlinds / Tilt motorized blinds** working **even after the cloud
+shuts down**. `smartblinds-ble` controls the shade motors **locally over Bluetooth
+LE** — **no proprietary hub, no cloud account, no phone app required** — and is
+built to run through **Home Assistant** and cheap **ESP32 / ESPHome Bluetooth
+Proxies**.
+
+> **Status: pre-alpha / bring-up.** The BLE protocol was reverse-engineered in 2018
+> and is **not yet re-verified** on current firmware — see [`docs/ROADMAP.md`](docs/ROADMAP.md)
+> (Milestone 0 gates everything). The **cloud key-export tool below works today**,
+> independent of that.
+>
+> Unofficial project. Not affiliated with, authorized by, or endorsed by
+> MySmartBlinds, Tilt, or SmarterHome. Use at your own risk; may void your warranty.
+
+## Is this you?
+
+If you're searching for any of the following, you're in the right place:
+
+- **"Is MySmartBlinds / Tilt shutting down / discontinued / out of business?"** —
+  the signs point that way (`tiltsmarthome.com` now redirects to a wind-down page,
+  parts are unavailable, support has gone quiet).
+- **"MySmartBlinds app not working / won't connect / no one answers support."**
+- **"How do I control MySmartBlinds without the hub / without the cloud / without the app?"**
+- **"MySmartBlinds / Tilt Home Assistant integration"** — a *local* one, not the
+  old laggy cloud bridge.
+- **"Will my smart blinds keep working if the servers go offline?"**
+- **"MySmartBlinds ESP32 / ESPHome / Bluetooth local control."**
+
+## ⏳ Rescue your keys now (do this before the cloud goes dark)
+
+Each motor needs a small BLE **key** to accept commands. While the vendor cloud is
+still online, it will hand back the real key for **every shade on your account**
+after a single login. Once the cloud shuts down, keys are only recoverable the hard
+way (brute-force or Bluetooth sniffing). This step needs **no extra hardware**:
+
+```bash
+# Not on PyPI yet — install from GitHub. Use the maintained docBliny fork of the
+# cloud client (PyPI's build is stale and no longer logs in):
+pip install "git+https://github.com/docBliny/smartblinds-client.git" \
+            "git+https://github.com/benbalter/smartblinds-ble.git"
+
+smartblinds-import-cloud            # cloud email/password -> smartblinds-keys.json
+```
+
+> If pip errors with `externally-managed-environment`, run it in a venv:
+> `python3 -m venv .venv && . .venv/bin/activate` then re-run the install.
+> Once this is published to PyPI, the above collapses to `pip install "smartblinds-ble[cloud]"`.
+
+The output holds `{name, mac, key}` per shade and is your **offline insurance** if
+the cloud disappears. Keep it safe — it contains secrets (gitignored by default).
+
+> **Legacy app only.** This exports from the *legacy MySmartBlinds* cloud. If you
+> set your shades up in the newer **Tilt** app, they live in a separate backend and
+> won't appear here (login works but returns zero blinds). In that case, skip the
+> cloud and read the key directly over BLE with `smartblinds-find-key`.
+
+> The importer logs into **your own account** to retrieve **your own devices'**
+> keys, for interoperability with hardware you own. Use your own credentials, at
+> your own risk.
+
+## Why this exists
+
+The motors are ordinary Bluetooth LE devices. The only reason the vendor's hub
+exists is to bridge Wi-Fi → cloud → Bluetooth. With the company winding down, that
+cloud is a single point of failure that could take your blinds offline. This
+project talks to the motors **directly and locally**, so:
+
+- **No hub, no cloud, no account** — everything stays on your LAN.
+- Control routes through inexpensive **ESP32 ESPHome Bluetooth Proxies** for
+  whole-home coverage, or any Home Assistant Bluetooth adapter.
+- Your **MySmartBlinds keep working after the cloud shuts down**.
+
+## How it works
+
+Two layers:
+
+1. **`smartblinds-ble`** (this repo) — a small async, `bleak`-based Python library
+   for talking to the motors over BLE.
+2. **`ha-smartblinds-ble`** (in progress) — a HACS-installable **Home Assistant**
+   integration exposing each shade as an optimistic tilt `cover`, working through
+   ESPHome Bluetooth Proxies.
+
+## Two things everyone gets stuck on
+
+- **The per-motor key.** Best: export it from the cloud with `smartblinds-import-cloud`
+  (above) while you still can. Offline fallback: brute-force the first byte with
+  `smartblinds-find-key`, or sniff the app once. See [`docs/PROTOCOL.md`](docs/PROTOCOL.md).
+- **No state feedback.** The motors are open-loop (reads return `0xFF`). Position is
+  tracked optimistically; changes made from the app or a physical wand are invisible.
+
+## Quick start (bring-up, local adapter)
+
+```bash
+pip install -e ".[dev]"
+smartblinds-find-key            # scan + brute-force keys for nearby motors
+pytest                          # protocol/encoding unit tests (mocked BLE)
+```
+
+```python
+import asyncio
+from smartblinds_ble import SmartBlind, discover
+
+async def main():
+    (device,) = await discover()
+    blind = SmartBlind(device, key="2a")   # from the cloud export or find-key
+    await blind.set_tilt_percent(50)       # flat-ish
+
+asyncio.run(main())
+```
+
+## FAQ
+
+### Is MySmartBlinds / Tilt going out of business?
+There's no formal shutdown announcement, but the signals are strong: the operator
+(SmarterHome, a Hall Labs subsidiary) is winding down, `tiltsmarthome.com`
+permanently redirects to that wind-down page, replacement parts have been
+unavailable for a while, and support has gone quiet. The app still received updates
+into 2025, so the cloud is alive **for now** — which is exactly why you should
+export your keys today.
+
+### Will my blinds stop working if the cloud/app shuts down?
+The blinds themselves are local Bluetooth devices, so they don't *need* the cloud —
+but the **official app and hub depend on it**, and you need each motor's key to
+control it locally. That's what this project (and the key-export tool) is for:
+keeping your **MySmartBlinds working after the cloud goes offline**.
+
+### How do I control MySmartBlinds without the hub or the app?
+Get each motor's key (cloud export or brute-force), then send BLE commands with
+this library — directly from a computer/Raspberry Pi, or through Home Assistant +
+an ESP32 Bluetooth Proxy.
+
+### Does this work with Home Assistant?
+That's the goal — a local HACS integration (`ha-smartblinds-ble`) exposing each
+shade as a tilt `cover`, no cloud bridge. It's in progress and gated on hardware
+validation (see the roadmap).
+
+### Do I need an ESP32 / ESPHome Bluetooth Proxy?
+Only for range. Any Home Assistant Bluetooth adapter works if it's near the shades;
+ESP32 ESPHome Bluetooth Proxies (a few dollars each) extend coverage across a house.
+
+### Does it work with the Tilt app still installed?
+Avoid using both at once — the app and this library can fight over position, since
+the motors don't report their true state.
+
+## Credits
+
+- [`dnschneid/pysmartblinds`](https://github.com/dnschneid/pysmartblinds) — the
+  original reverse engineering (Apache-2.0); this is a modern async port. See
+  [`NOTICE`](NOTICE).
+- [`ianlevesque/smartblinds-client`](https://github.com/ianlevesque/smartblinds-client)
+  and [`docBliny/ha-mysmartblinds`](https://github.com/docBliny/ha-mysmartblinds) —
+  the cloud client and (cloud-based) HA integration this borrows the key-export idea from.
+- [`LennP/ha-motionblinds_ble`](https://github.com/LennP/ha-motionblinds_ble) — the
+  template for the Home Assistant integration layer.
+
+## Keywords
+
+MySmartBlinds · Tilt · Tilt SmartHome · SmarterHome · Hall Labs · smart blinds ·
+motorized blinds · local control · no cloud · no hub · cloud shutdown ·
+discontinued · Home Assistant · HACS · Bluetooth · BLE · bleak · ESP32 · ESPHome ·
+Bluetooth Proxy · retire the hub · keep working after cloud shutdown
+
+## License
+
+[Apache-2.0](LICENSE).