Tuya quirks library
What is this?
tuya-device-handlers is a "quirks" library used by Home Assistant's Tuya integration to fix or normalise misbehaving Tuya devices. A quirk is matched against a device's product_id and patches its datapoints (function/status_range/local_strategy) before Home Assistant builds entities from them.
The library is shipped to end users via Home Assistant — you do not install it directly.
Writing a quirk
1. Find your device's product_id and datapoints
In Home Assistant: Settings → Devices & services → Tuya → your device → Download diagnostics. The JSON contains the product_id, the cloud-reported function / status_range maps, and the current status values. Use these to decide what needs patching.
2. Create a quirk file
Drop a Python file into your Home Assistant config folder at <config>/tuya_quirks/<category>_<product_id_lowercased>.py. The <category> prefix follows Tuya's official category codes (e.g. cz for plug/socket, wk for thermostat, cl for curtain).
Quirks are built using a fluent DeviceQuirk builder. Minimal example — redefine one datapoint and remove another:
from tuya_device_handlers import TUYA_QUIRKS_REGISTRY
from tuya_device_handlers.builder import DeviceQuirk
from tuya_device_handlers.const import DPMode
(
DeviceQuirk()
.applies_to(product_id="abcdEFGHijkl1234")
.add_dpid_integer(
dpid=18,
dpcode="cur_current",
dpmode=DPMode.READ,
unit="mA",
min=0,
max=30000,
scale=0,
step=1,
)
.remove_dpid(dpid=22, dpcode="phantom_dp")
.register(TUYA_QUIRKS_REGISTRY)
)
Each quirk file should contain exactly one DeviceQuirk()...register(...) chain at module top level — the file path is captured for reload tracking. Available builder methods include add_dpid_boolean, add_dpid_bitmap, add_dpid_enum, add_dpid_integer, and remove_dpid. For more complex needs (custom value scaling, platform-specific definitions), see the in-tree examples under src/tuya_device_handlers/devices/.
New to this and not a programmer? For a fully worked, copy-paste walkthrough of one of the most common fixes — a device sending ENUM values (e.g. extra
modepresets) that Home Assistant rejects asFound invalid ENUM value ...— see Recipe: add missing ENUM values. It covers writing the quirk, testing it live, and opening a PR end to end.
Entities missing — all of them, or just some? A quirk can only rewrite a device's datapoints; turning them into entities is Home Assistant's job, and it can only do that for a category and a DPCode it knows. If a datapoint is absent from the diagnostics, a quirk can add it; if it's present but never becomes an entity, the fix belongs in core. See Recipe: missing entities.
3. Test it inside Home Assistant
- Restart the Tuya integration (Settings → Devices & services → Tuya → ⋮ → Reload). Quirks under
<config>/tuya_quirks/are reloaded each time, so you don't need to restart Home Assistant itself. - Watch the logs — you should see
Loading custom quirk module …followed byLoaded custom quirks. Please contribute them to https://github.com/home-assistant-libs/tuya-device-handlers. If the import fails, the traceback is logged. - Verify the device's entities reflect your changes (download diagnostics again to confirm the patched function/status_range maps).
Contributing your quirk
Once your quirk works, please open a pull request so other Home Assistant users benefit.
-
Fork and clone this repository, then run
poetry install. -
Move your quirk file from
<config>/tuya_quirks/tosrc/tuya_device_handlers/devices/<category>/. The filename should match<category>_<product_id_lowercased>.py. -
Add a device fixture JSON at
tests/fixtures/devices/<category>_<product_id>.json. Build it from your Home Assistant diagnostics download: keep only the contents of the top-leveldataproperty (the captured device payload), then remove itsid,terminal_id, andhome_assistantkeys. Name the file from the payload's owncategoryandproduct_idfields. For example:python3 -c " import json d = json.load(open('diagnostics.json'))['data'] for k in ('id', 'terminal_id', 'home_assistant'): d.pop(k, None) name = f\"tests/fixtures/devices/{d['category']}_{d['product_id']}.json\" with open(name, 'w') as f: json.dump(d, f, indent=2, ensure_ascii=False) f.write('\n') print(name) "
-
Add a test under
tests/devices/<category>/covering the patched behaviour. -
Run the test suite locally:
poetry run pytest --cov tuya_device_handlers tests -
Open a pull request.
For broader contributor guidelines (issue reporting, dev setup, pre-commit hooks), see the Contributor Guide.
License
Distributed under the terms of the MIT license, Tuya quirks library is free and open source software.
Issues
If you encounter any problems, please file an issue along with a detailed description.
Release files for tuya-device-handlers 0.0.31
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tuya_device_handlers-0.0.31.tar.gz | 54.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tuya_device_handlers-0.0.31-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 149.4 kB
Release files / tuya_device_handlers-0.0.31.tar.gz
| Download URL | tuya_device_handlers-0.0.31.tar.gz |
|---|---|
| Size | 54.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8df7bfe83adab1919c91c8b30db704bfb3d4a4534cf2fdb0a5b6429c8bb7902b
|
|
BLAKE2b-256 checksum How to use checksums |
430be76baf744ab48bc466d4a7a087237c39d62329c2982b5e52e3bb8c6ff7bc
|
| 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 28, 2026.
Transparency logRelease files / tuya_device_handlers-0.0.31-py3-none-any.whl
| Download URL | tuya_device_handlers-0.0.31-py3-none-any.whl |
|---|---|
| Size | 95.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6276d3d0f426228e7e6daffdf394d192b4e983a9a4b6466222065f27c2137974
|
|
BLAKE2b-256 checksum How to use checksums |
dbfb57676a08d12e7a63330797f57112a1a538aab678e46663b5f38b20c09f44
|
| 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 28, 2026.
Transparency log