rustuya-local 0.1.0.dev5__tar.gz → 0.1.0.dev6__tar.gz

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/.github/workflows/_test.yml

@@ -38,14 +38,14 @@ jobs:
           repository: 3735943886/ildevice-homeassistant
           path: ildevice-homeassistant
 
-      # tuya2ildevice is on PyPI (installed below via uv), so this isn't for dependency
+      # tuya-interpreter is on PyPI (installed below via uv), so this isn't for dependency
       # resolution -- it's so tests/e2e/test_full_stack_devices.py can reach its sibling
       # checkout's tests/golden fixture data, which isn't shipped in the published package.
-      - name: Check out tuya2ildevice
+      - name: Check out tuya-interpreter
         uses: actions/checkout@v7
         with:
-          repository: 3735943886/tuya2ildevice
-          path: tuya2ildevice
+          repository: 3735943886/tuya-interpreter
+          path: tuya-interpreter
 
       - name: Set up Python ${{ matrix.python-version }}
         uses: actions/setup-python@v7
@@ -114,7 +114,7 @@ jobs:
           "$RUNNER_TEMP/smoke/bin/python" -c "
           import rustuya_local.cli, rustuya_local.manager_plugin, rustuya_local.service
           from rustuya_local import register
-          import tuya2ildevice
-          tuya2ildevice.preload()
+          import tuya_interpreter
+          tuya_interpreter.preload()
           print('ok')"
           "$RUNNER_TEMP/smoke/bin/rustuya-local" --help

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/.github/workflows/release.yml

@@ -96,7 +96,7 @@ jobs:
         run: twine check --strict dist/*      # --strict: a missing README (long description) fails the release
 
       - name: Build the rustuya-manager drop-in zip
-        # The manager's plugin catalog installs this asset (it cannot pip-install): rustuya_local with the tuya2ildevice
+        # The manager's plugin catalog installs this asset (it cannot pip-install): rustuya_local with the tuya-interpreter
         # the wheel resolves to vendored inside. Kept out of dist/ so it is not uploaded to PyPI.
         run: |
           python -m pip install dist/*.whl

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/CHANGELOG.md

@@ -8,6 +8,12 @@ stable release.
 
 ## [Unreleased]
 
+## [0.1.0.dev6] — 2026-10-12
+
+### Changed
+- Require tuya-interpreter 0.1.0a1 (tuya2ildevice renamed) in place of tuya2ildevice, in the package, the Home Assistant integration and the manager drop-in archive.
+- Fetch builtin rule updates from tuya-interpreter's `master` branch.
+
 ## [0.1.0.dev5] — 2026-10-11
 
 ### Fixed

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.5
 Name: rustuya-local
-Version: 0.1.0.dev5
-Summary: Local Tuya control: rustuya-bridge -> tuya2ildevice -> IL (ildevice). HA-independent core.
+Version: 0.1.0.dev6
+Summary: Local Tuya control: rustuya-bridge -> tuya-interpreter -> IL (ildevice). HA-independent core.
 Project-URL: Homepage, https://github.com/3735943886/rustuya-local
 Project-URL: Repository, https://github.com/3735943886/rustuya-local
 Project-URL: Issues, https://github.com/3735943886/rustuya-local/issues
@@ -10,7 +10,7 @@ License-File: LICENSE
 Requires-Python: >=3.13
 Requires-Dist: paho-mqtt>=2.0
 Requires-Dist: pyrustuyabridge>=0.4
-Requires-Dist: tuya2ildevice>=0.4.0.dev4
+Requires-Dist: tuya-interpreter>=0.1.0a1
 Provides-Extra: fullstack
 Requires-Dist: tuyamock; extra == 'fullstack'
 Provides-Extra: manager
@@ -37,7 +37,7 @@ rustuya-bridge ──MQTT──► rustuya-local ──MQTT (il/…)──► il
                          BridgeClient + rustuya_local.host.Hub
 ```
 
-- **[tuya2ildevice](https://github.com/3735943886/tuya2ildevice)** is the only place that interprets Tuya: Home Assistant core's `tuya` behaviour and
+- **[tuya-interpreter](https://github.com/3735943886/tuya-interpreter)** is the only place that interprets Tuya: Home Assistant core's `tuya` behaviour and
   user overrides for non-standard devices, through its Sans-I/O Rust engine and Python wrapper.
 - **rustuya-local** is one `Service` (`src/rustuya_local/service.py`) and three thin shells that run it:
   the `rustuya-local run` daemon, the `custom_components/rustuya` Home Assistant integration, and a rustuya-manager
@@ -62,7 +62,7 @@ Stopping the daemon only marks it `offline`; its devices stay in IL (retained) f
 and run `rustuya-local purge --config config.json`: the retained descriptors, values and presence of its IL prefix and
 source are cleared (other sources on the prefix are left alone), so IL consumers drop the devices.
 
-## tuya2ildevice 0.4 host boundary
+## tuya-interpreter host boundary
 
 The shared Rust core interprets one device and has no MQTT or rule-file loading API.
 `rustuya_local.host.Hub` owns the device registry and maps `TuyaDriver` outputs to IL MQTT wire data;
@@ -96,16 +96,16 @@ everything on an external bridge, are left as they are.
 Tuya's cloud schemas are fragmented; fixes go in a `custom_converters/` directory (daemon: `custom_converters` in the
 config; integration: `<config>/rustuya_converters`; manager plugin: its data dir), followed live:
 
-- `*.json`: tuya2ildevice override blocks by product or device id: rename a dp, define one the schema lacks, map the
+- `*.json`: tuya-interpreter override blocks by product or device id: rename a dp, define one the schema lacks, map the
   device's words to the standard ones (`remap.alias`), fix labels and classes, define a declarative converter. A cover's
   direction is not set here but with its settings (below). Each file is a rule object with fixes under `overrides`, for example
   `{"overrides": {"product_id": {"cover": {"invert_position": true}}}}`.
 - Converters are JSON programs under `converters.declarative`; Python code plugins are not loaded.
 
-See tuya2ildevice's README ("User overrides") for the format. Official builtin rules, including `00-default.json`,
-ship with tuya2ildevice and update when that package is upgraded. They are applied before your own rule files.
+See tuya-interpreter's [device customization guide](https://github.com/3735943886/tuya-interpreter/blob/master/docs/device-customization.md#user-overrides) for the format. Official builtin rules, including `00-default.json`,
+ship with tuya-interpreter and update when that package is upgraded. They are applied before your own rule files.
 
-Online updates fetch the latest [builtin rules](https://github.com/3735943886/tuya2ildevice/tree/feat/rust-rule-engine/rules/builtin)
+Online updates fetch the latest [builtin rules](https://github.com/3735943886/tuya-interpreter/tree/master/rules/builtin)
 into `rules/builtin/` inside the overrides directory at start and daily. In the Rustuya panel, use *Update builtin rules*
 to fetch them now or *Automatically update builtin rules* to control automatic updates. Opening the panel checks for
 updates: with automatic updates on, available changes are installed immediately without a yellow dot. With automatic
@@ -158,7 +158,7 @@ language: Korean, or English.
 ## rustuya-manager plugin
 
 Installed next to rustuya-manager, as a pip package (`pip install rustuya-local` in the manager's environment) or as
-the drop-in zip each release carries (`rustuya_local-<version>-dropin.zip`, tuya2ildevice binding, native library and builtin rules vendored inside, built by
+the drop-in zip each release carries (`rustuya_local-<version>-dropin.zip`, tuya-interpreter binding, native library and builtin rules vendored inside, built by
 `scripts/build_dropin.py`; unpack it into the manager's plugin directory, or install it from the manager's plugin
 catalog once listed there), it appears as a **Tuya (IL)** tab and runs the service under the manager: the manager's broker and bridge root, the manager's device
 list (followed). Its data dir (`rustuya-local/` next to the manager's plugins) holds `settings.json` (`il`,
@@ -166,7 +166,7 @@ list (followed). Its data dir (`rustuya-local/` next to the manager's plugins) h
 converter files are picked up while it runs. A settings file it cannot use is shown on the tab until it is fixed.
 
 The drop-in zip includes native code for the platform on which it was built; use a matching OS and architecture,
-or install with pip to select the appropriate wheel. It freezes the tuya2ildevice it was built with: a tuya2ildevice fix reaches manager users with the next
+or install with pip to select the appropriate wheel. It freezes the tuya-interpreter it was built with: a tuya-interpreter fix reaches manager users with the next
 rustuya-local release (bump the patch version and tag; the manager's catalog follows the release). Installed both ways
 (pip and the plugin directory), the plugin runs once.
 
@@ -178,7 +178,7 @@ rustuya-local release (bump the patch version and tag; the manager's catalog fol
 
 Everything here needs the sibling repos and, for the last two groups, `mosquitto`, `pyrustuya-bridge` and `tuyamock`
 (`pip install -e ".[test,fullstack]"`); those are skipped when missing. Parity with Home Assistant core's fixtures lives in
-`tuya2ildevice/tests/chain`, the wire and topic vectors in `ildevice/vectors`.
+`tuya-interpreter/tests/chain`, the wire and topic vectors in `ildevice/vectors`.
 
 - `tests/unit/`: the configuration.
 - `tests/e2e/test_service.py`: the service on in-memory brokers (overrides directory, a failed start).
@@ -188,7 +188,7 @@ Everything here needs the sibling repos and, for the last two groups, `mosquitto
 - `tests/ha/`: the integration (config flow, setup).
 - `tests/e2e/test_full_stack*.py`: the real rustuya-bridge (`pyrustuyabridge`, in process) and Tuya device emulators
   (`tuyamock`) around the daemon: state, commands, rejections, a device dropping off and returning, a daemon restart, and a
-  differential check that 38 real device shapes come out of the whole chain exactly as `tuya2ildevice` computes them.
+  differential check that 38 real device shapes come out of the whole chain exactly as `tuya-interpreter` computes them.
 
 ## Status
 

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/README.md

@@ -11,7 +11,7 @@ rustuya-bridge ──MQTT──► rustuya-local ──MQTT (il/…)──► il
                          BridgeClient + rustuya_local.host.Hub
 ```
 
-- **[tuya2ildevice](https://github.com/3735943886/tuya2ildevice)** is the only place that interprets Tuya: Home Assistant core's `tuya` behaviour and
+- **[tuya-interpreter](https://github.com/3735943886/tuya-interpreter)** is the only place that interprets Tuya: Home Assistant core's `tuya` behaviour and
   user overrides for non-standard devices, through its Sans-I/O Rust engine and Python wrapper.
 - **rustuya-local** is one `Service` (`src/rustuya_local/service.py`) and three thin shells that run it:
   the `rustuya-local run` daemon, the `custom_components/rustuya` Home Assistant integration, and a rustuya-manager
@@ -36,7 +36,7 @@ Stopping the daemon only marks it `offline`; its devices stay in IL (retained) f
 and run `rustuya-local purge --config config.json`: the retained descriptors, values and presence of its IL prefix and
 source are cleared (other sources on the prefix are left alone), so IL consumers drop the devices.
 
-## tuya2ildevice 0.4 host boundary
+## tuya-interpreter host boundary
 
 The shared Rust core interprets one device and has no MQTT or rule-file loading API.
 `rustuya_local.host.Hub` owns the device registry and maps `TuyaDriver` outputs to IL MQTT wire data;
@@ -70,16 +70,16 @@ everything on an external bridge, are left as they are.
 Tuya's cloud schemas are fragmented; fixes go in a `custom_converters/` directory (daemon: `custom_converters` in the
 config; integration: `<config>/rustuya_converters`; manager plugin: its data dir), followed live:
 
-- `*.json`: tuya2ildevice override blocks by product or device id: rename a dp, define one the schema lacks, map the
+- `*.json`: tuya-interpreter override blocks by product or device id: rename a dp, define one the schema lacks, map the
   device's words to the standard ones (`remap.alias`), fix labels and classes, define a declarative converter. A cover's
   direction is not set here but with its settings (below). Each file is a rule object with fixes under `overrides`, for example
   `{"overrides": {"product_id": {"cover": {"invert_position": true}}}}`.
 - Converters are JSON programs under `converters.declarative`; Python code plugins are not loaded.
 
-See tuya2ildevice's README ("User overrides") for the format. Official builtin rules, including `00-default.json`,
-ship with tuya2ildevice and update when that package is upgraded. They are applied before your own rule files.
+See tuya-interpreter's [device customization guide](https://github.com/3735943886/tuya-interpreter/blob/master/docs/device-customization.md#user-overrides) for the format. Official builtin rules, including `00-default.json`,
+ship with tuya-interpreter and update when that package is upgraded. They are applied before your own rule files.
 
-Online updates fetch the latest [builtin rules](https://github.com/3735943886/tuya2ildevice/tree/feat/rust-rule-engine/rules/builtin)
+Online updates fetch the latest [builtin rules](https://github.com/3735943886/tuya-interpreter/tree/master/rules/builtin)
 into `rules/builtin/` inside the overrides directory at start and daily. In the Rustuya panel, use *Update builtin rules*
 to fetch them now or *Automatically update builtin rules* to control automatic updates. Opening the panel checks for
 updates: with automatic updates on, available changes are installed immediately without a yellow dot. With automatic
@@ -132,7 +132,7 @@ language: Korean, or English.
 ## rustuya-manager plugin
 
 Installed next to rustuya-manager, as a pip package (`pip install rustuya-local` in the manager's environment) or as
-the drop-in zip each release carries (`rustuya_local-<version>-dropin.zip`, tuya2ildevice binding, native library and builtin rules vendored inside, built by
+the drop-in zip each release carries (`rustuya_local-<version>-dropin.zip`, tuya-interpreter binding, native library and builtin rules vendored inside, built by
 `scripts/build_dropin.py`; unpack it into the manager's plugin directory, or install it from the manager's plugin
 catalog once listed there), it appears as a **Tuya (IL)** tab and runs the service under the manager: the manager's broker and bridge root, the manager's device
 list (followed). Its data dir (`rustuya-local/` next to the manager's plugins) holds `settings.json` (`il`,
@@ -140,7 +140,7 @@ list (followed). Its data dir (`rustuya-local/` next to the manager's plugins) h
 converter files are picked up while it runs. A settings file it cannot use is shown on the tab until it is fixed.
 
 The drop-in zip includes native code for the platform on which it was built; use a matching OS and architecture,
-or install with pip to select the appropriate wheel. It freezes the tuya2ildevice it was built with: a tuya2ildevice fix reaches manager users with the next
+or install with pip to select the appropriate wheel. It freezes the tuya-interpreter it was built with: a tuya-interpreter fix reaches manager users with the next
 rustuya-local release (bump the patch version and tag; the manager's catalog follows the release). Installed both ways
 (pip and the plugin directory), the plugin runs once.
 
@@ -152,7 +152,7 @@ rustuya-local release (bump the patch version and tag; the manager's catalog fol
 
 Everything here needs the sibling repos and, for the last two groups, `mosquitto`, `pyrustuya-bridge` and `tuyamock`
 (`pip install -e ".[test,fullstack]"`); those are skipped when missing. Parity with Home Assistant core's fixtures lives in
-`tuya2ildevice/tests/chain`, the wire and topic vectors in `ildevice/vectors`.
+`tuya-interpreter/tests/chain`, the wire and topic vectors in `ildevice/vectors`.
 
 - `tests/unit/`: the configuration.
 - `tests/e2e/test_service.py`: the service on in-memory brokers (overrides directory, a failed start).
@@ -162,7 +162,7 @@ Everything here needs the sibling repos and, for the last two groups, `mosquitto
 - `tests/ha/`: the integration (config flow, setup).
 - `tests/e2e/test_full_stack*.py`: the real rustuya-bridge (`pyrustuyabridge`, in process) and Tuya device emulators
   (`tuyamock`) around the daemon: state, commands, rejections, a device dropping off and returning, a daemon restart, and a
-  differential check that 38 real device shapes come out of the whole chain exactly as `tuya2ildevice` computes them.
+  differential check that 38 real device shapes come out of the whole chain exactly as `tuya-interpreter` computes them.
 
 ## Status
 

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/custom_components/rustuya/bridge_supervisor.py

@@ -1,6 +1,6 @@
 """An embedded rustuya-bridge: `pyrustuyabridge.PyBridgeServer` run in a background thread, tied to this config
 entry's lifecycle instead of a separate rustuya-bridge process. Same class our own end-to-end tests drive
-(tuya2ildevice/rustuya-local tests/e2e/test_full_stack.py) — proven against a real broker and real Tuya-protocol
+(tuya-interpreter/rustuya-local tests/e2e/test_full_stack.py) — proven against a real broker and real Tuya-protocol
 devices, just supervised here instead of by a test fixture.
 
 The embedded bridge still needs a real MQTT broker to talk through (it manages its own native MQTT client); it does

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/custom_components/rustuya/const.py

@@ -28,7 +28,7 @@ CONF_DEVICES_PATH = "devices_path"              # tuyadevices.json; the cloud wi
 # --- entry options (changed any time through the options flow) -------------------------
 CONF_ALLOW_HAZARDOUS = "allow_hazardous"
 CONF_EXPOSE_UNUSED = "expose_unused"
-CONF_PACK = "pack"                          # sync tuya2ildevice's override pack into CONVERTERS_DIR
+CONF_PACK = "pack"                          # sync tuya-interpreter's override pack into CONVERTERS_DIR
 CONF_PANEL = "panel"                        # the sidebar page (panel.py); Configure adds / removes it
 
 DEFAULT_OPTIONS = {CONF_ALLOW_HAZARDOUS: False, CONF_EXPOSE_UNUSED: False, CONF_PACK: True}

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/custom_components/rustuya/manifest.json

@@ -9,12 +9,12 @@
   "iot_class": "local_push",
   "issue_tracker": "https://github.com/3735943886/rustuya-local/issues",
   "requirements": [
-    "tuya2ildevice>=0.4.0.dev4",
+    "tuya-interpreter>=0.1.0a1",
     "paho-mqtt>=2.0",
     "rustuya-manager>=0.2.2",
     "pyrustuyabridge>=0.4",
-    "rustuya-local>=0.1.0.dev5"
+    "rustuya-local>=0.1.0.dev6"
   ],
   "single_config_entry": true,
-  "version": "0.1.0.dev5"
+  "version": "0.1.0.dev6"
 }

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/custom_components/rustuya/www/rustuya-panel.js

@@ -195,9 +195,9 @@ const I18N = {
     settings_unreadable: "Cannot read the settings: {error}", confirm_settings: "Save {names} and restart Rustuya?",
     sync_now: "Update builtin rules", hide_title: "Remove this panel from the sidebar; the integration's Configure adds it back",
     hide: "Hide panel", pack_title: "Builtin rules",
-    pack_intro: "Official rules included with tuya2ildevice. Fetch the latest rules without updating the integration.",
+    pack_intro: "Official rules included with tuya-interpreter. Fetch the latest rules without updating the integration.",
     converters_title: "Custom converters",
-    converters_intro: "Rule files (*.json: override blocks and declarative converters) in rustuya_converters/. Saved files apply within seconds. See tuya2ildevice's README, \"User overrides\". Drop files here to copy them in.",
+    converters_intro: "Rule files (*.json: override blocks and declarative converters) in rustuya_converters/. Saved files apply within seconds. See tuya-interpreter docs/device-customization.md, \"User overrides\". Drop files here to copy them in.",
     new_file: "New file", save: "Save", delete: "Delete",
     only_converters: "{name} (only *.json files are converters)",
     confirm_replace_pack: "{name} comes from the override pack. Replaced, it is yours: the pack no longer updates or removes it.",
@@ -266,9 +266,9 @@ const I18N = {
     settings_unreadable: "설정을 읽을 수 없습니다: {error}", confirm_settings: "{names}을(를) 저장하고 Rustuya를 재시작할까요?",
     sync_now: "Builtin 규칙 업데이트", hide_title: "사이드바에서 이 패널을 없앱니다. 통합구성요소의 구성(Configure)에서 다시 추가할 수 있습니다",
     hide: "패널 숨기기", pack_title: "Builtin 규칙",
-    pack_intro: "tuya2ildevice에 포함된 공식 규칙입니다. 통합구성요소 업데이트 없이 최신 규칙을 가져옵니다.",
+    pack_intro: "tuya-interpreter에 포함된 공식 규칙입니다. 통합구성요소 업데이트 없이 최신 규칙을 가져옵니다.",
     converters_title: "커스텀 컨버터",
-    converters_intro: "rustuya_converters/ 안의 규칙 파일(*.json: 오버라이드 블록과 선언형 컨버터). 저장한 파일은 몇 초 안에 적용됩니다. tuya2ildevice README의 \"User overrides\"를 참고하세요. 여기에 파일을 끌어다 놓으면 복사됩니다.",
+    converters_intro: "rustuya_converters/ 안의 규칙 파일(*.json: 오버라이드 블록과 선언형 컨버터). 저장한 파일은 몇 초 안에 적용됩니다. tuya-interpreter docs/device-customization.md의 \"User overrides\"를 참고하세요. 여기에 파일을 끌어다 놓으면 복사됩니다.",
     new_file: "새 파일", save: "저장", delete: "삭제",
     only_converters: "{name} (*.json 파일만 컨버터입니다)",
     confirm_replace_pack: "{name}은(는) 오버라이드 팩의 파일입니다. 바꾸면 내 파일이 되어 팩이 더 이상 갱신하거나 지우지 않습니다.",

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/docs/MIGRATING.md

@@ -1,4 +1,4 @@
-# Moving to tuya2ildevice 0.4
+# Moving to tuya-interpreter
 
 The device file, MQTT configuration and IL topics stay the same. Custom files in the converters directory now use
 the rule-layer format. Wrap an existing product/device override mapping in `{"overrides": ...}`. For example:
@@ -30,7 +30,7 @@ rustuya-manager plugin. It is retired. Its replacement is two pieces:
   `ildevice`, and Home Assistant keeps the two apart. Automations, scripts and dashboards that name the old entities
   need the new ids. If you clear the old discovery first (step 1), the old ids are free and you can rename the new
   entities to them in Home Assistant.
-- **Entities follow Home Assistant core's `tuya` integration** (tuya2ildevice reproduces it), so a device can come out
+- **Entities follow Home Assistant core's `tuya` integration** (tuya-interpreter reproduces it), so a device can come out
   with more, fewer or differently split entities than v1 made.
 - **Availability** comes from rustuya-local's presence: when it stops, its devices show unavailable.
 
@@ -61,7 +61,7 @@ rustuya-manager plugin. It is retired. Its replacement is two pieces:
    | daemon | `custom_converters` in its `config.json` |
 
    - `*.json` files are rule layers, with product/device fixes under `overrides`
-     ([User overrides](https://github.com/3735943886/tuya2ildevice#user-overrides)); the old ones are not read, so rewrite them.
+     ([User overrides](https://github.com/3735943886/tuya-interpreter/blob/master/docs/device-customization.md#user-overrides)); the old ones are not read, so rewrite them.
      A property the tables do not build is defined from its dp in `props`.
    - A curtain's `invert_position` / `invert_set_position`, reversed command words and derived state are not files any
      more: each cover has configuration switches for them (README, *Cover settings*).
@@ -69,7 +69,7 @@ rustuya-manager plugin. It is retired. Its replacement is two pieces:
    - `converters.cover_motion` and a cover's `infer_motion` are read as the cover's `state_source` (`inferred`, or
      `none` for `infer_motion: false`), and a `cover_motion` `settle` as the cover's `settle`; its other keys are
      dropped with a warning. `zz_settings.json` is rewritten in the new form the next time a setting is saved.
-   - Leave the old pack (`00_default.json`, `00_curtain.py`, `.rustuya_pack.json`) out. Official rules ship with tuya2ildevice; online updates arrive under
+   - Leave the old pack (`00_default.json`, `00_curtain.py`, `.rustuya_pack.json`) out. Official rules ship with tuya-interpreter; online updates arrive under
      `rules/builtin/` automatically. User files are applied after all official rules.
 
    Changes to the directory are picked up while running, no restart needed.

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/docs/ROADMAP.md

@@ -1,6 +1,6 @@
-# 남은 일 (2026-10-11 갱신)
+# 남은 일 (2026-10-12 갱신)
 
-현재 작업 트리는 `rustuya-local 0.1.0.dev2`이며 `tuya2ildevice>=0.4.0.dev3`, `pyrustuyabridge>=0.4`를 요구한다.
+현재 작업 트리는 `rustuya-local 0.1.0.dev6`이며 `tuya-interpreter>=0.1.0a1`, `pyrustuyabridge>=0.4`를 요구한다.
 HA 통합과 매니저 플러그인 테스트는 `rustuya-manager>=0.2.2`를 사용한다. 변환은 Sans-I/O Rust 드라이버가 맡고,
 기기 레지스트리·IL MQTT 어댑터·전송·타이머·규칙 파일 로딩은 `rustuya_local.host`로 옮겼다.
 버전별 변경은 [CHANGELOG.md](../CHANGELOG.md)에 기록한다. 이 문서는 실제 배포 서버의 최신 상태를 확인하는 자료가 아니다.

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/pyproject.toml

@@ -4,12 +4,12 @@ build-backend = "hatchling.build"
 
 [project]
 name = "rustuya-local"
-version = "0.1.0.dev5"
-description = "Local Tuya control: rustuya-bridge -> tuya2ildevice -> IL (ildevice). HA-independent core."
+version = "0.1.0.dev6"
+description = "Local Tuya control: rustuya-bridge -> tuya-interpreter -> IL (ildevice). HA-independent core."
 readme = "README.md"
 requires-python = ">=3.13"
 license = "MIT"
-dependencies = ["tuya2ildevice>=0.4.0.dev4", "pyrustuyabridge>=0.4", "paho-mqtt>=2.0"]
+dependencies = ["tuya-interpreter>=0.1.0a1", "pyrustuyabridge>=0.4", "paho-mqtt>=2.0"]
 # rustuya-manager (custom_components/rustuya's config flow) is optional at the package level (the HA manifest
 # pulls it in); declared here too so the venv used for this repo's tests has it. pyrustuyabridge is a base dependency
 # now (not just for the embedded bridge): rustuya-local's own bridge_client uses it to interpret rustuya-bridge's

rustuya_local-0.1.0.dev6/release-notes.md

@@ -0,0 +1,3 @@
+### Changed
+- Require tuya-interpreter 0.1.0a1 (tuya2ildevice renamed) in place of tuya2ildevice, in the package, the Home Assistant integration and the manager drop-in archive.
+- Fetch builtin rule updates from tuya-interpreter's `master` branch.

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/scripts/build_dropin.py

@@ -3,7 +3,7 @@
 
 The manager downloads the zip, checks its SHA-256 against its catalog, unpacks it into its plugin directory and calls
 the top-level package's `register(ctx)`. A dropped-in plugin cannot pip-install, so the zip has one top-level entry,
-`rustuya_local/`, with tuya2ildevice (Python binding, native library and rule pack) vendored under `rustuya_local/_vendor/`. paho-mqtt and
+`rustuya_local/`, with tuya-interpreter (Python binding, native library and rule pack) vendored under `rustuya_local/_vendor/`. paho-mqtt and
 pyrustuyabridge are not vendored: the manager depends on both.
 
 The bytes depend only on the file contents (sorted entries, fixed timestamps and modes, no compression), so the same
@@ -11,7 +11,7 @@ sources give the same SHA-256.
 
     python scripts/build_dropin.py [--outdir dist]
 
-tuya2ildevice is taken from the environment the script runs in (install rustuya-local first).
+tuya-interpreter is taken from the environment the script runs in (install rustuya-local first).
 """
 
 from __future__ import annotations
@@ -28,7 +28,7 @@ from pathlib import Path
 REPO_ROOT = Path(__file__).resolve().parent.parent
 PKG_DIR = REPO_ROOT / "src" / "rustuya_local"
 FIXED_DATE_TIME = (1980, 1, 1, 0, 0, 0)
-VENDORED = ("tuya2ildevice",)
+VENDORED = ("tuya_interpreter",)
 
 
 def _files(root: Path) -> list[Path]:
@@ -46,10 +46,10 @@ def _members() -> list[tuple[str, Path]]:
             sys.exit(f"error: {name} is not installed; install rustuya-local first")
         root = Path(next(iter(spec.submodule_search_locations)))
         out += [(f"rustuya_local/_vendor/{name}/{p.relative_to(root).as_posix()}", p) for p in _files(root)]
-        if name == "tuya2ildevice":
+        if name == "tuya_interpreter":
             # Editable checkouts keep build outputs and rule artifacts outside the Python package.
             # Installed wheels already contain them; include equivalent assets when building locally.
-            from tuya2ildevice.native import library
+            from tuya_interpreter.native import library
 
             from rustuya_local.host.rules import rule_files, rule_paths
 

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/__init__.py

@@ -3,8 +3,8 @@
 import sys
 from pathlib import Path
 
-# The rustuya-manager drop-in zip (scripts/build_dropin.py) carries tuya2ildevice here, since a dropped-in plugin cannot
-# pip-install. Appended, not prepended: an installed tuya2ildevice wins.
+# The rustuya-manager drop-in zip (scripts/build_dropin.py) carries tuya-interpreter here, since a dropped-in plugin cannot
+# pip-install. Appended, not prepended: an installed tuya-interpreter wins.
 _VENDOR = Path(__file__).parent / "_vendor"
 if _VENDOR.is_dir() and str(_VENDOR) not in sys.path:
     sys.path.append(str(_VENDOR))

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/bridge_client.py

@@ -30,7 +30,7 @@ from dataclasses import dataclass
 from typing import Any
 
 import pyrustuyabridge as pb
-from tuya2ildevice import Connected, Disconnected, Message
+from tuya_interpreter import Connected, Disconnected, Message
 
 from rustuya_local.host import BridgeCommand, Runner
 from rustuya_local.host.transport import Message as TransportMessage

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/config.py

@@ -15,7 +15,7 @@
 (overrides and declarative converters, see `rustuya_local.host.load_overrides`), followed the same
 way; `options.overrides` is merged over it. A device's settings written through IL (a cover's direction switches) are
 kept in that directory too; `options.device_settings: false` stops offering them. `pack` (on by default) copies
-tuya2ildevice's override pack, fixes published between releases, into that directory daily. Every key but `devices`
+tuya-interpreter's override pack, fixes published between releases, into that directory daily. Every key but `devices`
 has a default. The bridge's own topic templates are read from its retained `{root}/bridge/config` at start.
 """
 

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/host/__init__.py

@@ -1,4 +1,4 @@
-"""Run the host-owned `Hub` over tuya2ildevice 0.4 drivers: MQTT (or in-process) transports, timers, Last Will presence, reconnects,
+"""Run the host-owned `Hub` over tuya-interpreter drivers: MQTT (or in-process) transports, timers, Last Will presence, reconnects,
 runtime device changes, following rustuya-manager's `tuyadevices.json` and a directory of user rule files. TuyaDriver is Sans-I/O; this package owns file loading, clocks and transport operations.
 
     from rustuya_local.host import MqttTransport, Runner

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/host/devices.py

@@ -1,5 +1,5 @@
 """The device list: `tuyadevices.json`, which rustuya-manager keeps (its QR-login wizard writes it, atomically). Each
-entry is a Tuya cloud record with the schema tuya2ildevice needs (`category`, `product_id`, `function`,
+entry is a Tuya cloud record with the schema tuya-interpreter needs (`category`, `product_id`, `function`,
 `status_range`, `local_strategy`). rustuya-local reads it and follows it as it changes; it never writes it."""
 
 from __future__ import annotations

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/host/hub.py

@@ -7,8 +7,15 @@ from collections import Counter
 from collections.abc import Sequence
 from typing import Any
 
-from tuya2ildevice import Command, Connected, Disconnected, Message, Timer, TuyaDriver
-from tuya2ildevice.native import register_rules, unregister_rules
+from tuya_interpreter import (
+    Command,
+    Connected,
+    Disconnected,
+    Message,
+    Timer,
+    TuyaDriver,
+)
+from tuya_interpreter.native import register_rules, unregister_rules
 
 from .il import (
     IL,

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/host/il.py

@@ -1,11 +1,11 @@
-"""IL MQTT wire mapping and host actions. Tuya interpretation stays in tuya2ildevice."""
+"""IL MQTT wire mapping and host actions. Tuya interpretation stays in tuya-interpreter."""
 from __future__ import annotations
 
 import json
 from dataclasses import dataclass
 from typing import Any
 
-from tuya2ildevice import (
+from tuya_interpreter import (
     Absent,
     CancelTimer,
     Descriptor,

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/host/overrides.py

@@ -1,7 +1,7 @@
 """User rule files: a directory (or one `.json` file) of partial rule objects, loaded and followed as it changes.
 
 Each `*.json` is a rule layer (product/device fixes under `overrides`), merged in filename order over the rules
-tuya2ildevice ships and validated by its engine. `SETTINGS_FILE` (``zz_settings.json``) holds the settings written
+tuya-interpreter ships and validated by its engine. `SETTINGS_FILE` (``zz_settings.json``) holds the settings written
 through IL, a block per device (`OverrideWatcher.save_settings`); it can be edited like any other file.
 
 Files starting with `.` or `_` are skipped. Nothing here raises for a bad file: a file that does
@@ -18,7 +18,7 @@ from dataclasses import dataclass, field
 from pathlib import Path
 from typing import Any
 
-from tuya2ildevice import OverrideError, merge_all
+from tuya_interpreter import OverrideError, merge_all
 
 from rustuya_local.host.rules import load_rules_tolerant, rule_files, upgrade_overrides
 

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/host/pack.py

@@ -1,4 +1,4 @@
-"""The override pack: fixes for non-standard devices published on tuya2ildevice's `feat/rust-rule-engine` branch (`rules/builtin/`) and copied into
+"""The override pack: fixes for non-standard devices published on tuya-interpreter's `master` branch (`rules/builtin/`) and copied into
 the host's rule directory, so a fix reaches users without a release. `OverrideWatcher` then loads the copied files
 like the user's own. The files are rule layers (JSON); fetching them is the host's, the engine only merges them.
 
@@ -37,10 +37,10 @@ from .overrides import SETTINGS_FILE
 
 _LOGGER = logging.getLogger(__name__)
 
-LEVEL = 4                                         # 2: `cover` settings; 3: `delta`; 4: rule-layer files (tuya2ildevice 0.4)
-BASE_URL = "https://raw.githubusercontent.com/3735943886/tuya2ildevice/feat/rust-rule-engine/rules/builtin/"
+LEVEL = 4                                         # 2: `cover` settings; 3: `delta`; 4: rule-layer files (tuya2ildevice 0.4, tuya-interpreter)
+BASE_URL = "https://raw.githubusercontent.com/3735943886/tuya-interpreter/master/rules/builtin/"
 MANIFEST = "manifest.json"
-LEDGER = ".tuya2ildevice_pack.json"
+LEDGER = ".tuya2ildevice_pack.json"                # kept across the rename: existing installs own their files by it
 MAX_BYTES = 1024 * 1024
 TIMEOUT = 15
 _NAME = re.compile(r"^[A-Za-z0-9][A-Za-z0-9_.-]*\.json$")

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/host/rules.py

@@ -8,8 +8,8 @@ import logging
 import os
 from pathlib import Path
 
-import tuya2ildevice
-from tuya2ildevice import merge_rules
+import tuya_interpreter
+from tuya_interpreter import merge_rules
 
 _LOGGER = logging.getLogger(__name__)
 
@@ -63,7 +63,7 @@ def _upgrade_layer(data, where):
 
 
 def rule_paths(paths=(), *, bundled_path=None):
-    package = Path(tuya2ildevice.__file__).resolve().parent
+    package = Path(tuya_interpreter.__file__).resolve().parent
     bundled = package / 'rules' / 'builtin'
     checkout = package.parents[1] / 'rules' / 'builtin'
     location = bundled_path or (bundled if bundled.is_dir() else checkout)

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/host/runner.py

@@ -13,8 +13,8 @@ import secrets
 import time
 from collections.abc import Awaitable, Callable, Sequence
 
-from tuya2ildevice import Connected, Disconnected
-from tuya2ildevice import Message as DriverInput
+from tuya_interpreter import Connected, Disconnected
+from tuya_interpreter import Message as DriverInput
 
 from rustuya_local.host.il import (
     IL,

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/manager_plugin/__init__.py

@@ -15,7 +15,7 @@ its documented contract (api_version >= 4). What it takes from the manager:
     {"il": {"prefix": "il", "source": "tuya"},
      "options": {"allow_hazardous": false, "expose_unused": false, "use_quirks": true, "pack": true}}
 
-`pack` copies tuya2ildevice's override pack (fixes published between releases) into `custom_converters/` daily.
+`pack` copies tuya-interpreter's override pack (fixes published between releases) into `custom_converters/` daily.
 
 The tab shows what the service is doing (the plugin's state namespace) and edits the settings and the
 `custom_converters/` files through `/api/rustuya-local/...` (`api.py`). A settings change restarts the service in place;

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/manager_plugin/static/index.js

@@ -228,7 +228,7 @@ async function convertersBox(ctx) {
   box.append(
     el("p", { class: "text-sm text-gray-500 mb-2" },
       "Rule files (*.json: override blocks and declarative converters) for non-standard devices. ",
-      "See tuya2ildevice's README, \"User overrides\". Drop files here to copy them in."),
+      "See tuya-interpreter docs/device-customization.md, \"User overrides\". Drop files here to copy them in."),
     list, warnings,
     el("div", { class: "flex gap-2 mb-2 items-center" }, el("label", {}, "File ", name),
       el("button", { class: BTN, onclick: save }, "Save"), el("button", { class: BTN, onclick: remove }, "Delete"),

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/src/rustuya_local/service.py

@@ -16,10 +16,10 @@ integration, the rustuya-manager plugin or a daemon) serves them, since every de
 `online` that nobody answers for (a Last Will lost with the broker, or a producer on tuya2ildevice < 0.3.5) does not
 stop the start.
 
-With `pack` on, the override pack (tuya2ildevice's `rules/builtin/`) is copied into the overrides directory in the background at
+With `pack` on, the override pack (tuya-interpreter's `rules/builtin/`) is copied into the overrides directory in the background at
 start and every `pack_interval` seconds; the directory watcher loads what it brings. Manual requests work with `pack` off.
 
-A device's settings (a cover's direction toggles, tuya2ildevice's `device_settings`) are IL properties like any other;
+A device's settings (a cover's direction toggles, tuya-interpreter's `device_settings`) are IL properties like any other;
 writing one saves it into the overrides directory (`rustuya_local.host.SETTINGS_FILE`), which the watcher applies at
 once. Without an overrides directory there is nowhere to keep them, so the Hub does not offer them.
 """
@@ -36,7 +36,7 @@ from dataclasses import dataclass, field
 from pathlib import Path
 from typing import Any
 
-from tuya2ildevice import preload
+from tuya_interpreter import preload
 
 from rustuya_local.host import (
     BridgeCommand,
@@ -117,7 +117,7 @@ class Settings:
     watch_interval: float = 5.0
     pack: bool = False                         # automatically sync rules; manual sync remains available
     pack_interval: float = 86400.0
-    pack_url: str | None = None                # the pack's base URL; tuya2ildevice's `master` when None
+    pack_url: str | None = None                # the pack's base URL; tuya-interpreter's `master` when None
     hub_options: dict[str, Any] = field(default_factory=dict)
     """`rustuya_local.host.Hub` keyword arguments: `allow_hazardous`, `expose_unused`, `use_quirks`, `device_settings` (on
     by default, and only with an overrides directory), `overrides` (inline, merged over the directory's), `rules`."""

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/tests/e2e/devices.py

@@ -48,7 +48,7 @@ def status_reply(ids, offset=0, has_more=False, total=None):
                        "returned": len(ids), "has_more": has_more, **({"device_count": total} if total is not None else {})})
 
 
-GOLDEN = pathlib.Path(__file__).resolve().parents[3] / "tuya2ildevice/tests/golden"      # the sibling checkout
+GOLDEN = pathlib.Path(__file__).resolve().parents[3] / "tuya-interpreter/tests/golden"      # the sibling checkout
 WIRE = {"Boolean": "Boolean", "Integer": "Integer", "Enum": "Enum", "String": "String", "Raw": "Raw", "Json": "Json",
         "Bitmap": "Bitmap"}
 

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/tests/e2e/test_full_stack_devices.py

@@ -1,6 +1,6 @@
 """Differential test over the real bridge: many real device shapes (Home Assistant core's tuya fixtures) each get a
 tuyamock device with the fixture's dps, go through the real rustuya-bridge and the rustuya-local daemon, and the IL values
-that come out must equal what tuya2ildevice produces when it is fed the same dps directly.
+that come out must equal what tuya-interpreter produces when it is fed the same dps directly.
 
 What this catches that the in-process tests cannot: how the bridge serialises each Tuya type on the wire (booleans,
 scaled integers, enums, strings, raw/base64, json), and anything the daemon does to a message on the way through.
@@ -20,12 +20,12 @@ import pytest
 pyrustuyabridge = pytest.importorskip("pyrustuyabridge")
 tuyamock = pytest.importorskip("tuyamock")
 
-GOLDEN = pathlib.Path(__file__).resolve().parents[3] / "tuya2ildevice/tests/golden"      # the sibling checkout
+GOLDEN = pathlib.Path(__file__).resolve().parents[3] / "tuya-interpreter/tests/golden"      # the sibling checkout
 sys.path.insert(0, str(GOLDEN))
 import fixtures
 from devices import fixture_record as record
 from test_full_stack import Observer, wait
-from tuya2ildevice import Connected, Message, TuyaDriver, Value
+from tuya_interpreter import Connected, Message, TuyaDriver, Value
 
 from rustuya_local.host.il import encode_value
 from rustuya_local.host.rules import rules

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/tests/e2e/test_manager_plugin.py

@@ -99,9 +99,9 @@ plugin_dir = Path(sys.argv[1])
 vendor = plugin_dir / "rustuya_local" / "_vendor"
 
 class OnlyVendored:
-    # tuya2ildevice may be installed here; a manager's environment has none, so resolve it from the zip only
+    # tuya-interpreter may be installed here; a manager's environment has none, so resolve it from the zip only
     def find_spec(self, name, path=None, target=None):
-        if name.split(".")[0] != "tuya2ildevice" or path is not None:
+        if name.split(".")[0] != "tuya_interpreter" or path is not None:
             return None
         spec = importlib.machinery.PathFinder.find_spec(name, [str(vendor)])
         if spec is None:
@@ -118,12 +118,12 @@ ctx = plugins.PluginContext(plugins.PluginRegistry(), state=state, data_root=Pat
                             bridge_client=BridgeClient("mqtt://127.0.0.1:1", "r", state))
 for r in registers:
     r(ctx)
-import rustuya_local, tuya2ildevice
+import rustuya_local, tuya_interpreter
 from rustuya_local.service import Service
 from rustuya_local.host import MqttTransport
 assert Path(rustuya_local.__file__).is_relative_to(plugin_dir), rustuya_local.__file__
-assert Path(tuya2ildevice.__file__).is_relative_to(vendor), tuya2ildevice.__file__
-from tuya2ildevice import TuyaDriver, Connected, Command, SendMessage
+assert Path(tuya_interpreter.__file__).is_relative_to(vendor), tuya_interpreter.__file__
+from tuya_interpreter import TuyaDriver, Connected, Command, SendMessage
 from rustuya_local.host.rules import rules
 check = TuyaDriver({"id": "vendored", "category": "kg",
                     "function": {"switch_1": {"type": "Boolean", "values": {}}}},
@@ -135,7 +135,7 @@ print(len(registers), [p["id"] for p in ctx._registry.pages], len(ctx._registry.
 """
 
 
-def test_the_drop_in_zip_loads_in_the_manager_with_its_vendored_tuya2ildevice(tmp_path):
+def test_the_drop_in_zip_loads_in_the_manager_with_its_vendored_tuya_interpreter(tmp_path):
     import importlib.util
     import subprocess
     import sys

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/tests/ha/test_init.py

@@ -162,7 +162,7 @@ async def test_driving_the_first_device_does_no_blocking_io_in_the_event_loop(ha
                                                                                monkeypatch):
     """The host reads rule files and the binding loads its engine: the service preloads them in a worker
     thread, so Home Assistant sees no blocking call when the first device's driver is made."""
-    from tuya2ildevice import native
+    from tuya_interpreter import native
 
     from rustuya_local.host.rules import rules
 
@@ -175,7 +175,7 @@ async def test_driving_the_first_device_does_no_blocking_io_in_the_event_loop(ha
     real_read = pathlib.Path.read_text
 
     def read_text(self, *args, **kwargs):      # what Home Assistant's blocking-call detector flags, recorded instead
-        if threading.current_thread() is loop_thread and "tuya2ildevice" in str(self):
+        if threading.current_thread() is loop_thread and "tuya_interpreter" in str(self):
             in_loop.append(self.name)
         return real_read(self, *args, **kwargs)
     monkeypatch.setattr(pathlib.Path, "read_text", read_text)

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/tests/unit/test_cover_settings.py

@@ -5,7 +5,7 @@ import json
 import threading
 
 import pytest
-from tuya2ildevice import Command, Connected, Message
+from tuya_interpreter import Command, Connected, Message
 
 from rustuya_local.host import (
     SETTINGS_FILE,

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/tests/unit/test_dropin.py

@@ -1,4 +1,4 @@
-"""The rustuya-manager drop-in zip: one top-level package with tuya2ildevice vendored, byte-identical rebuilds."""
+"""The rustuya-manager drop-in zip: one top-level package with tuya-interpreter vendored, byte-identical rebuilds."""
 import hashlib
 import importlib.util
 import os
@@ -14,15 +14,15 @@ sys.modules["build_dropin"] = build_dropin
 spec.loader.exec_module(build_dropin)
 
 
-def test_one_package_with_tuya2ildevice_inside(tmp_path):
+def test_one_package_with_tuya_interpreter_inside(tmp_path):
     zf = zipfile.ZipFile(build_dropin.build(tmp_path))
     names = zf.namelist()
     assert {n.split("/", 1)[0] for n in names} == {"rustuya_local"}          # the manager imports each top-level entry
     for needed in ("rustuya_local/__init__.py", "rustuya_local/manager_plugin/static/index.js",
-                   "rustuya_local/_vendor/tuya2ildevice/__init__.py", "rustuya_local/_vendor/tuya2ildevice/native.py"):
+                   "rustuya_local/_vendor/tuya_interpreter/__init__.py", "rustuya_local/_vendor/tuya_interpreter/native.py"):
         assert needed in names
-    assert "rustuya_local/_vendor/tuya2ildevice/rules/builtin/00-default.json" in names
-    assert any(n.startswith("rustuya_local/_vendor/tuya2ildevice/") and n.endswith((".so", ".dll", ".dylib"))
+    assert "rustuya_local/_vendor/tuya_interpreter/rules/builtin/00-default.json" in names
+    assert any(n.startswith("rustuya_local/_vendor/tuya_interpreter/") and n.endswith((".so", ".dll", ".dylib"))
                for n in names)
     assert not any("__pycache__" in n or n.startswith("rustuya_local/_vendor/paho") for n in names)
 
@@ -33,7 +33,7 @@ def test_rebuilds_are_byte_identical(tmp_path):
     assert hashlib.sha256(a).digest() == hashlib.sha256(b).digest()
 
 
-def test_archive_runs_driver_without_installed_tuya2ildevice(tmp_path):
+def test_archive_runs_driver_without_installed_tuya_interpreter(tmp_path):
     with zipfile.ZipFile(build_dropin.build(tmp_path)) as archive:
         archive.extractall(tmp_path)
     # -I -S excludes editable installs and site-packages: both native code and rules
@@ -43,9 +43,9 @@ import sys
 from pathlib import Path
 sys.path.insert(0, sys.argv[1])
 from rustuya_local.host import Hub, BridgeCommand
-from tuya2ildevice import Connected, Message
-import tuya2ildevice
-assert Path(tuya2ildevice.__file__).is_relative_to(Path(sys.argv[1]))
+from tuya_interpreter import Connected, Message
+import tuya_interpreter
+assert Path(tuya_interpreter.__file__).is_relative_to(Path(sys.argv[1]))
 device = {'id': 'd', 'category': 'kg',
           'function': {'switch_1': {'type': 'Boolean', 'values': {}}},
           'local_strategy': {'1': {'value_convert': 'default', 'status_code': 'switch_1',

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/tests/unit/test_host.py

@@ -1,4 +1,4 @@
-"""The host-owned Hub around tuya2ildevice drivers (`rustuya_local.host`): Runner on the IL transport, the device file, the rule
+"""The host-owned Hub around tuya-interpreter drivers (`rustuya_local.host`): Runner on the IL transport, the device file, the rule
 directory, and paho against a real broker (mosquitto, skipped when it is not installed). The bridge side is simulated
 with `runner.on_bridge_message`; `BridgeCommand` outputs are captured via the injected `on_bridge_command` callback."""
 import asyncio
@@ -9,7 +9,7 @@ import subprocess
 import time
 
 import pytest
-from tuya2ildevice import Connected, Message, OverrideError
+from tuya_interpreter import Connected, Message, OverrideError
 
 from rustuya_local.host import (
     BridgeCommand,

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/tests/unit/test_hub.py

@@ -1,7 +1,7 @@
 import json
 
 import pytest
-from tuya2ildevice import Connected, Disconnected, Message
+from tuya_interpreter import Connected, Disconnected, Message
 
 from rustuya_local.host import BridgeCommand, Hub, Publish
 from tests.unit.tuya_samples import curtain, light
@@ -75,7 +75,7 @@ def test_a_multi_segment_il_prefix_still_parses_writes():
 
 
 def test_reload_overrides_republishes_and_clears_removed_props():
-    from tuya2ildevice import OverrideError
+    from tuya_interpreter import OverrideError
 
     hub = Hub([curtain()])
     hub.start()

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/tests/unit/test_il_vectors.py

@@ -1,11 +1,11 @@
 """The host wire mapping follows ildevice conformance vectors (../ildevice/vectors, or $ILDEVICE): payloads on the
-wire and topics. (Command checks and descriptor schemas are exercised by tuya2ildevice.)"""
+wire and topics. (Command checks and descriptor schemas are exercised by tuya-interpreter.)"""
 import json
 import os
 from pathlib import Path
 
 import pytest
-from tuya2ildevice import Rejected, check_command
+from tuya_interpreter import Rejected, check_command
 
 from rustuya_local.host import Hub, IlTopics
 from rustuya_local.host.il import decode_write, encode_value

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/tests/unit/test_pack.py

@@ -1,4 +1,4 @@
-"""The override pack: `host.pack.sync` against a pack served from a directory (file://), and the one tuya2ildevice
+"""The override pack: `host.pack.sync` against a pack served from a directory (file://), and the one tuya-interpreter
 publishes (its sibling checkout, when there is one)."""
 
 import hashlib
@@ -10,7 +10,7 @@ import pytest
 from rustuya_local.host import load_overrides, pack
 from rustuya_local.host.pack import LEDGER, PackError, read_ledger, sync
 
-PUBLISHED = Path(__file__).resolve().parents[3] / "tuya2ildevice" / "rules" / "builtin"       # the sibling checkout
+PUBLISHED = Path(__file__).resolve().parents[3] / "tuya-interpreter" / "rules" / "builtin"       # the sibling checkout
 
 
 def sha(text: str) -> str:
@@ -104,7 +104,7 @@ def test_a_bad_file_is_skipped_and_the_copy_there_stays(served):
 
 def test_files_are_bounded_by_level(served):
     src, dest = served
-    src.put("00_pack_new.json", FIX, requires=pack.LEVEL + 1)          # needs a newer tuya2ildevice
+    src.put("00_pack_new.json", FIX, requires=pack.LEVEL + 1)          # needs a newer tuya-interpreter
     src.put("00_pack_old.json", FIX, until=pack.LEVEL)                  # built into this one
     src.put("00_pack_now.json", FIX, requires=pack.LEVEL, until=pack.LEVEL + 1)
     assert sync(dest, base_url=src.url).added == ["00_pack_now.json"]
@@ -130,7 +130,7 @@ def test_unsafe_names_in_the_manifest_are_ignored(served):
     assert not r.changed and not (dest.parent / "escape.json").exists()
 
 
-@pytest.mark.skipif(not PUBLISHED.is_dir(), reason="no tuya2ildevice checkout next to this one")
+@pytest.mark.skipif(not PUBLISHED.is_dir(), reason="no tuya-interpreter checkout next to this one")
 def test_the_published_pack_loads(tmp_path):
     r = sync(tmp_path / "d", base_url=PUBLISHED.as_uri() + "/")
     assert not r.failed

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev6}/tests/unit/test_rule_files.py

@@ -5,7 +5,7 @@ import json
 import weakref
 
 import pytest
-from tuya2ildevice import Connected, TuyaDriver, merge_rules
+from tuya_interpreter import Connected, TuyaDriver, merge_rules
 
 from rustuya_local.host import Hub, OverrideWatcher, load_overrides
 from rustuya_local.host.hub import _pack_users
@@ -84,7 +84,7 @@ def test_inline_overrides_with_older_keys_are_upgraded():
 
 
 def test_a_rule_pack_the_hub_moves_off_is_released_once_no_hub_uses_it():
-    from tuya2ildevice.native import unregister_rules
+    from tuya_interpreter.native import unregister_rules
 
     own, other = labelled('only this test'), labelled('Other')
     first, second = Hub([dict(DEVICE)], rules=own), Hub([dict(DEVICE, id='e')], rules=own)
@@ -101,7 +101,7 @@ def labelled(label):
 
 
 def test_close_releases_only_the_last_owner_and_is_idempotent():
-    from tuya2ildevice.native import unregister_rules
+    from tuya_interpreter.native import unregister_rules
 
     pack = labelled('shared close regression')
     first, second = Hub([DEVICE], rules=pack), Hub([DEVICE], rules=pack)
@@ -121,7 +121,7 @@ def test_close_releases_only_the_last_owner_and_is_idempotent():
 
 
 def test_a_discarded_hub_releases_its_pack():
-    from tuya2ildevice.native import unregister_rules
+    from tuya_interpreter.native import unregister_rules
 
     hub = Hub([DEVICE], rules=labelled('garbage collection regression'))
     key, reference = hub._rules_id, weakref.ref(hub)
@@ -132,8 +132,8 @@ def test_a_discarded_hub_releases_its_pack():
 
 
 def test_failed_construction_releases_its_pack():
-    from tuya2ildevice import OverrideError
-    from tuya2ildevice.native import register_rules, unregister_rules
+    from tuya_interpreter import OverrideError
+    from tuya_interpreter.native import register_rules, unregister_rules
 
     pack = labelled('failed construction regression')
     key = register_rules(pack)
@@ -145,7 +145,7 @@ def test_failed_construction_releases_its_pack():
 
 
 def test_failed_adoption_releases_the_candidate_and_keeps_the_existing_drivers(monkeypatch):
-    from tuya2ildevice.native import register_rules, unregister_rules
+    from tuya_interpreter.native import register_rules, unregister_rules
 
     hub = Hub([DEVICE, dict(DEVICE, id='e')], rules=labelled('before failed adoption'))
     pack = labelled('failed adoption regression')

rustuya_local-0.1.0.dev5/release-notes.md

@@ -1,8 +0,0 @@
-### Fixed
-- Share the running service's complete bridge registry and MQTT command connection with the panel, so panel listing and edits do not open a second registry requester. Require complete contiguous registry pages for standalone setup sessions.
-- Keep explicit offline connection errors from being overwritten by replayed device state snapshots in the panel.
-
-### Changed
-- Split the HA panel synced filter into online and offline, with live sub-device/gateway state and migration of saved filters.
-- Check builtin rules when opening the HA panel; automatically install available updates when enabled, or enable the manual update button with a yellow dot when automatic updates are off.
-- Allow manual builtin rule updates while automatic updates are disabled.