daybetter-ble-client 1.0.0rc1__tar.gz

daybetter_ble_client-1.0.0rc1/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2025 Siddhant Kameswar
+
+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.

daybetter_ble_client-1.0.0rc1/PKG-INFO

@@ -0,0 +1,230 @@
+Metadata-Version: 2.4
+Name: daybetter-ble-client
+Version: 1.0.0rc1
+Summary: Async Bluetooth Low Energy control for Daybetter P031 and P065 LED strips
+Author-email: Siddhant Kameswar <61r7jw39@kameswar.com>, Jack Stockley <jack@jstockley.com>
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/jnstockley/daybetter-led-strip
+Project-URL: Repository, https://github.com/jnstockley/daybetter-led-strip.git
+Project-URL: Issues, https://github.com/jnstockley/daybetter-led-strip/issues
+Project-URL: Upstream, https://github.com/grimsteel/daybetter-led-strip
+Requires-Python: <3.16,>=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: bleak<4,>=3.1.0
+Requires-Dist: bleak-retry-connector<5,>=4.7.1
+Dynamic: license-file
+
+# daybetter-ble-client
+
+![GitHub License](https://img.shields.io/github/license/jnstockley/daybetter-led-strip)
+![CI](https://img.shields.io/github/actions/workflow/status/jnstockley/daybetter-led-strip/ci-cd.yml)
+
+Async Python control for Daybetter P031 and P065 RGB LED strips over Bluetooth
+Low Energy, using [Bleak](https://bleak.readthedocs.io/en/latest/). Requires
+Python 3.11–3.15. Models are detected from advertised services, with device names
+as a fallback.
+
+This project is forked from [grimsteel/daybetter-led-strip](https://github.com/grimsteel/daybetter-led-strip),
+originally created by **Siddhant Kameswar** ([grimsteel](https://github.com/grimsteel)).
+Credit for the original library and documented BLE protocol belongs to the
+original author. The original MIT license and copyright notice are preserved
+in [LICENSE](LICENSE).
+
+## Installation and migration
+
+The new distribution name is **`daybetter-ble-client`**, and the import package
+is **`daybetter_ble_client`**. This intentionally changes the old
+`daybetter_led_strip` import path; class and method names remain the same:
+
+```python
+from daybetter_ble_client import DaybetterLedStrip
+from daybetter_ble_client.const import SUPPORTED_DISCOVERY_SERVICES
+```
+
+Until the first release of this fork is published, install this checkout with
+`uv sync --locked`. Once published, install the distribution with
+`uv pip install daybetter-ble-client` (or `pip install daybetter-ble-client`).
+The upstream `daybetter-led-strip` distribution does not include this fork's
+changes.
+
+## Local development
+
+Install [uv](https://docs.astral.sh/uv/) and run:
+
+```sh
+uv sync --locked --all-groups
+uv run --locked pytest
+uv run --locked pytest tests/examples
+uv run --locked ruff check
+uv run --locked ruff format --check
+uv build --no-sources
+```
+
+`.python-version` selects Python 3.15 locally. Commit `uv.lock` when changing
+dependencies; `pyproject.toml` is the only dependency manifest.
+Runtime dependencies have explicit major-version bounds: Bleak stays on 3.x
+and bleak-retry-connector stays on 4.x. A major upgrade requires changing those
+bounds deliberately; ordinary dependency updates stay within them.
+
+`./scripts/test.sh` runs the library/release-tool tests with branch coverage and
+then the example tests. Coverage must be at least 95%; reports are written to
+`logs/`. Both CI tests and linting run on Python 3.11, 3.12, 3.13, 3.14,
+and 3.15. `./scripts/lint.sh` additionally checks shell and YAML files, requiring
+`shellcheck`, `shfmt`, and `yamllint` on PATH. See [testing](docs/TESTING.md) and
+[releases](docs/RELEASING.md) for the full workflow.
+
+The repository uses `src/daybetter_ble_client/` for the library, `tests/` for
+offline tests, `tests/examples/` for example tests, `examples/` for runnable
+programs, and `scripts/` for validation/release helpers. Tests block real BLE
+access; they do not need hardware or a PyPI account.
+
+For actual device use, enable Bluetooth and grant Bluetooth access to the app
+running Python on macOS. Close the phone app before connecting; a strip accepts
+only one BLE connection at a time.
+
+## Usage
+
+The `DaybetterLedStrip` constructor only requires the device address (a UUID on
+macOS, a MAC address on other platforms). Pass the scanned device and its
+advertisement data to `.update_device` for automatic model selection. The
+detected model is available as `.model`. If identifying data is unavailable,
+the compatibility default is P031. If the device disconnects, it will not
+automatically reconnect; call `.update_device` again with a freshly scanned
+device, or `.connect` to retry the stored device. P065 authenticates on every
+connection, and initialization failures raise an exception after cleanup.
+
+```python
+import asyncio
+from bleak import BleakScanner
+from daybetter_ble_client import DaybetterLedStrip
+from daybetter_ble_client.const import SUPPORTED_DISCOVERY_SERVICES
+
+# This snippet runs inside an async function. Pick one target explicitly.
+devices = await BleakScanner.discover(timeout=10, return_adv=True)
+matches = [
+    (device, data)
+    for device, data in devices.values()
+    if any(service in data.service_uuids for service in SUPPORTED_DISCOVERY_SERVICES)
+]
+for device, data in matches:
+    print(device.name, device.address)
+if not matches:
+    raise RuntimeError("No supported strip found")
+device, data = matches[0]  # choose the intended strip if several are found
+led_strip = DaybetterLedStrip(device.address)
+try:
+    await led_strip.update_device(device, data)
+    if not led_strip.connected:
+        raise RuntimeError("Could not connect to strip")
+    await led_strip.set_power(True)
+    await led_strip.set_color((255, 0, 0))
+    await asyncio.sleep(1)
+    await led_strip.set_power(False)
+finally:
+    await led_strip.disconnect()
+```
+
+A complete example program is provided in `examples/test.py`.
+Run it with `uv run --locked python examples/test.py`. It cycles colors, changes brightness,
+and turns the strip off. It requires exactly one supported strip to be
+discoverable to avoid changing an unintended device.
+
+This package was created [for use in Home Assistant](https://github.com/grimsteel/homeassistant-daybetter-led-strip), which may explain some of the API choices.
+
+## Protocol
+
+Communication with the LED strip is done over BLE.
+
+The light strip exposes two services: the generic access profile w/ the device name, and a custom "LED control service" (`0xe031`).
+
+During discovery, the device also advertises itself with a third service (`0xc031`) for identification.
+
+P065 uses the equivalent UUIDs `0xc065` (discovery), `0xe065` (control
+service), `0xa065` (write), and `0xf065` (status notifications).
+
+### P065 connection initialization
+
+After subscribing to notifications, P065 requires a two-step handshake before
+control commands take effect. Send command `0x00` with `CCHIP`; the response
+contains `CCHIP` and two device-specific bytes. Echo that complete seven-byte
+payload with command `0x01`. A six-byte reply ending in `0x01` indicates success.
+The library validates framing and CRC and waits up to five seconds for each
+response. It disconnects if initialization fails. Do not hard-code the two
+device-specific bytes from another strip.
+
+P065 color commands append `0xff` after the RGB bytes, and effect commands
+append `0xff` after the effect ID. P031 payloads retain their existing format.
+An acknowledgement only confirms receipt; it does not prove a visible change.
+
+Validation on a physical P065 covered handshake/reconnect, RGB color, brightness,
+power, and `FADE_RED_GREEN`, with settings checked through status reads. Other
+effect IDs have not been individually tested. P031's original command format is
+covered by regression tests; a fresh P031 hardware check could not be completed
+during this change because the device was not consistently discoverable.
+
+The LED control service has a read characteristic (`0xf031`) and a write characteristic (`0xa031`). As far as I can tell, the read characteristic cannot actually be read directly. Rather, if notifications are enabled on this service, the device will push updates about its state at various times.
+
+### Write Data Format
+
+Commands written to the write characteristic have the following format. 
+
+1. The byte `0xA0` (referred to in the app source code as "APP_TO_DEVICE")
+2. The command ID. (1 byte)
+3. The length of the entire message, not including the checksum. (1 byte) `= len(payload) + 3`
+4. The payload for this command
+5. The little-endian CRC16 MODBUS checksum of the rest of the message.
+
+### Commands
+
+| Command         | ID     | Payload Description                                                                                  |
+|-----------------|--------|-----------------------------------------------------------------------------------------------------|
+| **Get status**  | `0x10` | `0x00`<br>Results in status payload below being sent on notify                                      |
+| **Set power**   | `0x11` | `0x01` (on) or `0x00` (off)                                                                         |
+| **Show effect** | `0x12` | One of the effect bytes listed below                                                                |
+| **Set brightness** | `0x13` | A byte representing the brightness, from 0 (`0x00`) to 100 (`0x64`). Brightness 0 still has the LEDs slightly on |
+| **Set color**   | `0x15` | 3 bytes, in RGB order                                                                               |
+
+Example command (set to red): `A0 15 06 FF 00 00 25 C0`
+
+### Notify/read data format
+
+The payloads received over notify have a similar structure as the write commands:
+
+1. The byte `0xA1` ("DEVICE_TO_APP")
+2. Command ID
+3. Length of entire message excluding checksum
+4. Payload 
+5. LE Checksum
+
+### Received "commands"
+
+When any of the above write commands are written to the characteristic successfully, the device responds with a message with the same command ID and `0x01` for the payload.
+
+For instance, the above color command would result in `A1 15 04 01 F1 1C`
+
+When the strip is turned on/off from the IR remote, a message with command ID `0x10` and the payload `00 01 01 64 32 32 ff 31 2d f0 00 00 00 00` (off) or `01 01 01 64 32 32 ff 31 2d f0 00 00 00 00`. The first byte indicates the on/off status, but I don't know what the rest means. It seems unrelated to the color of the light.
+
+Running the "get status" command also results in this being sent.
+
+### Effects
+
+> Note: the brightness can be changed during the following effects. Lower brightnesses result in blinking happening faster, likely because there is a smaller range of brightnesses to interpolate between.
+
+RGB: just red/green/blue
+
+All preset colors: red/green/blue/yellow/teal/purple/white
+
+* `0x02..0x08`: show preset colors
+* `0x09`: switch RGB abruptly, no transition
+* `0x0A`: switch all preset colors
+* `0x0B`: fade between colors quickly
+* `0x0C`: fade between colors slowly
+* `0x0D`..`0x13`: blink individual preset colors
+* `0x14`: fade red/green
+* `0x15`: fade red/blue
+* `0x16`: fade green/blue
+* `0x17`: flash all preset colors
+* `0x18`..`0x1E`: flash individual preset colors
+* `0x1F`: strobe RGB
+* `0x20`: strobe all colors

daybetter_ble_client-1.0.0rc1/README.md

@@ -0,0 +1,213 @@
+# daybetter-ble-client
+
+![GitHub License](https://img.shields.io/github/license/jnstockley/daybetter-led-strip)
+![CI](https://img.shields.io/github/actions/workflow/status/jnstockley/daybetter-led-strip/ci-cd.yml)
+
+Async Python control for Daybetter P031 and P065 RGB LED strips over Bluetooth
+Low Energy, using [Bleak](https://bleak.readthedocs.io/en/latest/). Requires
+Python 3.11–3.15. Models are detected from advertised services, with device names
+as a fallback.
+
+This project is forked from [grimsteel/daybetter-led-strip](https://github.com/grimsteel/daybetter-led-strip),
+originally created by **Siddhant Kameswar** ([grimsteel](https://github.com/grimsteel)).
+Credit for the original library and documented BLE protocol belongs to the
+original author. The original MIT license and copyright notice are preserved
+in [LICENSE](LICENSE).
+
+## Installation and migration
+
+The new distribution name is **`daybetter-ble-client`**, and the import package
+is **`daybetter_ble_client`**. This intentionally changes the old
+`daybetter_led_strip` import path; class and method names remain the same:
+
+```python
+from daybetter_ble_client import DaybetterLedStrip
+from daybetter_ble_client.const import SUPPORTED_DISCOVERY_SERVICES
+```
+
+Until the first release of this fork is published, install this checkout with
+`uv sync --locked`. Once published, install the distribution with
+`uv pip install daybetter-ble-client` (or `pip install daybetter-ble-client`).
+The upstream `daybetter-led-strip` distribution does not include this fork's
+changes.
+
+## Local development
+
+Install [uv](https://docs.astral.sh/uv/) and run:
+
+```sh
+uv sync --locked --all-groups
+uv run --locked pytest
+uv run --locked pytest tests/examples
+uv run --locked ruff check
+uv run --locked ruff format --check
+uv build --no-sources
+```
+
+`.python-version` selects Python 3.15 locally. Commit `uv.lock` when changing
+dependencies; `pyproject.toml` is the only dependency manifest.
+Runtime dependencies have explicit major-version bounds: Bleak stays on 3.x
+and bleak-retry-connector stays on 4.x. A major upgrade requires changing those
+bounds deliberately; ordinary dependency updates stay within them.
+
+`./scripts/test.sh` runs the library/release-tool tests with branch coverage and
+then the example tests. Coverage must be at least 95%; reports are written to
+`logs/`. Both CI tests and linting run on Python 3.11, 3.12, 3.13, 3.14,
+and 3.15. `./scripts/lint.sh` additionally checks shell and YAML files, requiring
+`shellcheck`, `shfmt`, and `yamllint` on PATH. See [testing](docs/TESTING.md) and
+[releases](docs/RELEASING.md) for the full workflow.
+
+The repository uses `src/daybetter_ble_client/` for the library, `tests/` for
+offline tests, `tests/examples/` for example tests, `examples/` for runnable
+programs, and `scripts/` for validation/release helpers. Tests block real BLE
+access; they do not need hardware or a PyPI account.
+
+For actual device use, enable Bluetooth and grant Bluetooth access to the app
+running Python on macOS. Close the phone app before connecting; a strip accepts
+only one BLE connection at a time.
+
+## Usage
+
+The `DaybetterLedStrip` constructor only requires the device address (a UUID on
+macOS, a MAC address on other platforms). Pass the scanned device and its
+advertisement data to `.update_device` for automatic model selection. The
+detected model is available as `.model`. If identifying data is unavailable,
+the compatibility default is P031. If the device disconnects, it will not
+automatically reconnect; call `.update_device` again with a freshly scanned
+device, or `.connect` to retry the stored device. P065 authenticates on every
+connection, and initialization failures raise an exception after cleanup.
+
+```python
+import asyncio
+from bleak import BleakScanner
+from daybetter_ble_client import DaybetterLedStrip
+from daybetter_ble_client.const import SUPPORTED_DISCOVERY_SERVICES
+
+# This snippet runs inside an async function. Pick one target explicitly.
+devices = await BleakScanner.discover(timeout=10, return_adv=True)
+matches = [
+    (device, data)
+    for device, data in devices.values()
+    if any(service in data.service_uuids for service in SUPPORTED_DISCOVERY_SERVICES)
+]
+for device, data in matches:
+    print(device.name, device.address)
+if not matches:
+    raise RuntimeError("No supported strip found")
+device, data = matches[0]  # choose the intended strip if several are found
+led_strip = DaybetterLedStrip(device.address)
+try:
+    await led_strip.update_device(device, data)
+    if not led_strip.connected:
+        raise RuntimeError("Could not connect to strip")
+    await led_strip.set_power(True)
+    await led_strip.set_color((255, 0, 0))
+    await asyncio.sleep(1)
+    await led_strip.set_power(False)
+finally:
+    await led_strip.disconnect()
+```
+
+A complete example program is provided in `examples/test.py`.
+Run it with `uv run --locked python examples/test.py`. It cycles colors, changes brightness,
+and turns the strip off. It requires exactly one supported strip to be
+discoverable to avoid changing an unintended device.
+
+This package was created [for use in Home Assistant](https://github.com/grimsteel/homeassistant-daybetter-led-strip), which may explain some of the API choices.
+
+## Protocol
+
+Communication with the LED strip is done over BLE.
+
+The light strip exposes two services: the generic access profile w/ the device name, and a custom "LED control service" (`0xe031`).
+
+During discovery, the device also advertises itself with a third service (`0xc031`) for identification.
+
+P065 uses the equivalent UUIDs `0xc065` (discovery), `0xe065` (control
+service), `0xa065` (write), and `0xf065` (status notifications).
+
+### P065 connection initialization
+
+After subscribing to notifications, P065 requires a two-step handshake before
+control commands take effect. Send command `0x00` with `CCHIP`; the response
+contains `CCHIP` and two device-specific bytes. Echo that complete seven-byte
+payload with command `0x01`. A six-byte reply ending in `0x01` indicates success.
+The library validates framing and CRC and waits up to five seconds for each
+response. It disconnects if initialization fails. Do not hard-code the two
+device-specific bytes from another strip.
+
+P065 color commands append `0xff` after the RGB bytes, and effect commands
+append `0xff` after the effect ID. P031 payloads retain their existing format.
+An acknowledgement only confirms receipt; it does not prove a visible change.
+
+Validation on a physical P065 covered handshake/reconnect, RGB color, brightness,
+power, and `FADE_RED_GREEN`, with settings checked through status reads. Other
+effect IDs have not been individually tested. P031's original command format is
+covered by regression tests; a fresh P031 hardware check could not be completed
+during this change because the device was not consistently discoverable.
+
+The LED control service has a read characteristic (`0xf031`) and a write characteristic (`0xa031`). As far as I can tell, the read characteristic cannot actually be read directly. Rather, if notifications are enabled on this service, the device will push updates about its state at various times.
+
+### Write Data Format
+
+Commands written to the write characteristic have the following format. 
+
+1. The byte `0xA0` (referred to in the app source code as "APP_TO_DEVICE")
+2. The command ID. (1 byte)
+3. The length of the entire message, not including the checksum. (1 byte) `= len(payload) + 3`
+4. The payload for this command
+5. The little-endian CRC16 MODBUS checksum of the rest of the message.
+
+### Commands
+
+| Command         | ID     | Payload Description                                                                                  |
+|-----------------|--------|-----------------------------------------------------------------------------------------------------|
+| **Get status**  | `0x10` | `0x00`<br>Results in status payload below being sent on notify                                      |
+| **Set power**   | `0x11` | `0x01` (on) or `0x00` (off)                                                                         |
+| **Show effect** | `0x12` | One of the effect bytes listed below                                                                |
+| **Set brightness** | `0x13` | A byte representing the brightness, from 0 (`0x00`) to 100 (`0x64`). Brightness 0 still has the LEDs slightly on |
+| **Set color**   | `0x15` | 3 bytes, in RGB order                                                                               |
+
+Example command (set to red): `A0 15 06 FF 00 00 25 C0`
+
+### Notify/read data format
+
+The payloads received over notify have a similar structure as the write commands:
+
+1. The byte `0xA1` ("DEVICE_TO_APP")
+2. Command ID
+3. Length of entire message excluding checksum
+4. Payload 
+5. LE Checksum
+
+### Received "commands"
+
+When any of the above write commands are written to the characteristic successfully, the device responds with a message with the same command ID and `0x01` for the payload.
+
+For instance, the above color command would result in `A1 15 04 01 F1 1C`
+
+When the strip is turned on/off from the IR remote, a message with command ID `0x10` and the payload `00 01 01 64 32 32 ff 31 2d f0 00 00 00 00` (off) or `01 01 01 64 32 32 ff 31 2d f0 00 00 00 00`. The first byte indicates the on/off status, but I don't know what the rest means. It seems unrelated to the color of the light.
+
+Running the "get status" command also results in this being sent.
+
+### Effects
+
+> Note: the brightness can be changed during the following effects. Lower brightnesses result in blinking happening faster, likely because there is a smaller range of brightnesses to interpolate between.
+
+RGB: just red/green/blue
+
+All preset colors: red/green/blue/yellow/teal/purple/white
+
+* `0x02..0x08`: show preset colors
+* `0x09`: switch RGB abruptly, no transition
+* `0x0A`: switch all preset colors
+* `0x0B`: fade between colors quickly
+* `0x0C`: fade between colors slowly
+* `0x0D`..`0x13`: blink individual preset colors
+* `0x14`: fade red/green
+* `0x15`: fade red/blue
+* `0x16`: fade green/blue
+* `0x17`: flash all preset colors
+* `0x18`..`0x1E`: flash individual preset colors
+* `0x1F`: strobe RGB
+* `0x20`: strobe all colors

daybetter_ble_client-1.0.0rc1/pyproject.toml

@@ -0,0 +1,57 @@
+[project]
+name = "daybetter-ble-client"
+version = "1.0.0rc1"
+description = "Async Bluetooth Low Energy control for Daybetter P031 and P065 LED strips"
+readme = "README.md"
+requires-python = ">=3.11,<3.16"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [
+    { name = "Siddhant Kameswar", email = "61r7jw39@kameswar.com" },
+    { name = "Jack Stockley", email = "jack@jstockley.com" },
+]
+dependencies = [
+    "bleak>=3.1.0,<4",
+    "bleak-retry-connector>=4.7.1,<5",
+]
+
+[project.urls]
+Homepage = "https://github.com/jnstockley/daybetter-led-strip"
+Repository = "https://github.com/jnstockley/daybetter-led-strip.git"
+Issues = "https://github.com/jnstockley/daybetter-led-strip/issues"
+Upstream = "https://github.com/grimsteel/daybetter-led-strip"
+
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+norecursedirs = ["examples", ".*"]
+addopts = "-ra"
+
+[tool.coverage.run]
+branch = true
+source = ["daybetter_ble_client"]
+
+[tool.coverage.report]
+show_missing = true
+fail_under = 95
+
+[dependency-groups]
+dev = [
+    "packaging>=25.0",
+    "pytest>=9.1.1",
+    "pytest-cov>=7.1.0",
+    "ruff>=0.17.2",
+    "twine>=6.0",
+]
+
+[tool.ruff]
+target-version = "py311"
+
+[tool.ruff.lint]
+select = ["E4", "E7", "E9", "F", "I"]

daybetter_ble_client-1.0.0rc1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

daybetter_ble_client-1.0.0rc1/src/daybetter_ble_client/__init__.py

@@ -0,0 +1,3 @@
+from .led_strip import DaybetterLedStrip
+
+__all__ = ["DaybetterLedStrip"]

daybetter_ble_client-1.0.0rc1/src/daybetter_ble_client/const.py

@@ -0,0 +1,101 @@
+from dataclasses import dataclass
+from enum import IntEnum, unique
+
+from bleak.uuids import normalize_uuid_16
+
+# includes Device Name characteristic
+SERVICE_GENERIC_ACCESS_PROFILE = normalize_uuid_16(0x1800)
+# read
+CHAR_DEVICE_NAME = normalize_uuid_16(0x2A00)
+
+SERVICE_LED_CONTROL = normalize_uuid_16(0xE031)
+# write
+CHAR_LED_CONTROL = normalize_uuid_16(0xA031)
+# "read", notify
+CHAR_LED_STATUS = normalize_uuid_16(0xF031)
+
+# Advertised service
+SERVICE_DISCOVERY = normalize_uuid_16(0xC031)
+
+
+@dataclass(frozen=True)
+class DeviceProfile:
+    model: str
+    discovery_service: str
+    control_service: str
+    write_characteristic: str
+    status_characteristic: str
+    requires_handshake: bool = False
+    variant: bytes = b""
+
+
+P031 = DeviceProfile(
+    "P031", SERVICE_DISCOVERY, SERVICE_LED_CONTROL, CHAR_LED_CONTROL, CHAR_LED_STATUS
+)
+P065 = DeviceProfile(
+    "P065",
+    normalize_uuid_16(0xC065),
+    normalize_uuid_16(0xE065),
+    normalize_uuid_16(0xA065),
+    normalize_uuid_16(0xF065),
+    True,
+    b"\xff",
+)
+DEVICE_PROFILES = (P031, P065)
+SUPPORTED_DISCOVERY_SERVICES = tuple(p.discovery_service for p in DEVICE_PROFILES)
+
+# GATT command ID
+COMMAND_BRIGHTNESS = 0x13
+COMMAND_EFFECT = 0x12
+COMMAND_POWER = 0x11
+COMMAND_COLOR = 0x15
+
+
+@unique
+class Effect(IntEnum):
+    # Show preset colors
+    SHOW_RED = 0x02
+    SHOW_GREEN = 0x03
+    SHOW_BLUE = 0x04
+    SHOW_YELLOW = 0x05
+    SHOW_TEAL = 0x06
+    SHOW_PURPLE = 0x07
+    SHOW_WHITE = 0x08
+
+    # Switch colors abruptly
+    SWITCH_RGB = 0x09
+    SWITCH_ALL_PRESET_COLORS = 0x0A
+
+    # Fade between colors
+    FADE_COLORS_QUICK = 0x0B
+    FADE_COLORS_SLOW = 0x0C
+
+    # Blink individual preset colors
+    BLINK_RED = 0x0D
+    BLINK_GREEN = 0x0E
+    BLINK_BLUE = 0x0F
+    BLINK_YELLOW = 0x10
+    BLINK_TEAL = 0x11
+    BLINK_PURPLE = 0x12
+    BLINK_WHITE = 0x13
+
+    # Fade between two colors
+    FADE_RED_GREEN = 0x14
+    FADE_RED_BLUE = 0x15
+    FADE_GREEN_BLUE = 0x16
+
+    # Flash all preset colors
+    FLASH_ALL_PRESET_COLORS = 0x17
+
+    # Flash individual preset colors
+    FLASH_RED = 0x18
+    FLASH_GREEN = 0x19
+    FLASH_BLUE = 0x1A
+    FLASH_YELLOW = 0x1B
+    FLASH_TEAL = 0x1C
+    FLASH_PURPLE = 0x1D
+    FLASH_WHITE = 0x1E
+
+    # Strobe effects
+    STROBE_RGB = 0x1F
+    STROBE_ALL_COLORS = 0x20