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

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

@@ -3,7 +3,7 @@ name: Test (reusable)
 # Single source of truth for rustuya-local's pre-merge / pre-publish checks. Called from ci.yml
 # on push/PR and as a gate from release.yml, so a commit that fails these can't reach PyPI.
 #
-# il-ha is not on PyPI yet, so check out ildevice-homeassistant and explicitly
+# ildevice-homeassistant is not on PyPI yet, so check out ildevice-homeassistant and explicitly
 # install that checkout together with rustuya-local's test extras.
 # Other package dependencies are installed from PyPI.
 
@@ -20,7 +20,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        # il-ha (the test/fullstack sibling dep) requires Python>=3.14; rustuya-local's own
+        # ildevice-homeassistant (the test/fullstack sibling dep) requires Python>=3.14; rustuya-local's own
         # requires-python floor (3.13, in pyproject.toml) stays lower since only the test extras
         # need 3.14, not the base package.
         python-version: ["3.14"]
@@ -31,21 +31,21 @@ jobs:
         with:
           path: rustuya-local
 
-      # The repository publishes its Python package under the name il-ha.
+      # Install the integration checkout as the test consumer package.
       - name: Check out ildevice-homeassistant
         uses: actions/checkout@v7
         with:
           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
@@ -91,7 +91,7 @@ jobs:
         run: pytest -q
 
   package:
-    # The test job uses an il-ha checkout; this one checks what a user gets: the wheel in a fresh
+    # The test job uses an ildevice-homeassistant checkout; this one checks what a user gets: the wheel in a fresh
     # environment, every dependency from PyPI, importing and starting the CLI.
     name: installs from PyPI alone
     runs-on: ubuntu-latest
@@ -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.dev7}/.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.dev7}/CHANGELOG.md

@@ -8,6 +8,18 @@ stable release.
 
 ## [Unreleased]
 
+## [0.1.0.dev7] — 2026-10-12
+
+### Changed
+- Use ildevice-homeassistant consistently in documentation, UI text and code comments.
+- Require tuya-interpreter 0.1.0a2 in the package and the Home Assistant integration.
+
+## [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.dev7}/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.dev7
+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,14 +10,14 @@ 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.0a2
 Provides-Extra: fullstack
 Requires-Dist: tuyamock; extra == 'fullstack'
 Provides-Extra: manager
 Requires-Dist: rustuya-manager[web]>=0.2.2; extra == 'manager'
 Provides-Extra: test
 Requires-Dist: httpx2; extra == 'test'
-Requires-Dist: il-ha; extra == 'test'
+Requires-Dist: ildevice-homeassistant; extra == 'test'
 Requires-Dist: pytest; extra == 'test'
 Requires-Dist: pytest-asyncio; extra == 'test'
 Provides-Extra: test-ha
@@ -32,17 +32,17 @@ Local control of Tuya devices through [rustuya-bridge](https://github.com/373594
 ([ildevice](https://github.com/3735943886/ildevice)) devices, and in Home Assistant. It replaces rustuya-homeassistant.
 
 ```
-rustuya-bridge ──MQTT──► rustuya-local ──MQTT (il/…)──► il-ha (Home Assistant integration), or any IL consumer
+rustuya-bridge ──MQTT──► rustuya-local ──MQTT (il/…)──► ildevice-homeassistant (Home Assistant integration), or any IL consumer
  raw LAN dps             Service:
                          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
   plugin. Its `host` package owns the runner, transports and file watchers. It only produces IL and knows nothing of Home Assistant entities.
-- **[il-ha](https://github.com/3735943886/ildevice-homeassistant)** turns IL descriptors into Home Assistant entities.
+- **[ildevice-homeassistant](https://github.com/3735943886/ildevice-homeassistant)** turns IL descriptors into Home Assistant entities.
 
 ## Daemon
 
@@ -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;
@@ -75,7 +75,7 @@ MQTT and in-process transport tests exercise the same adapter and the bidirectio
 
 Coming from rustuya-homeassistant: [docs/MIGRATING.md](docs/MIGRATING.md).
 
-Install il-ha, and run one IL producer per bridge: the daemon, the integration below, or the manager plugin. A second
+Install ildevice-homeassistant, and run one IL producer per bridge: the daemon, the integration below, or the manager plugin. A second
 one with the same IL prefix and source refuses to start while the first runs (every device would show twice): the
 daemon exits, the integration is retried by Home Assistant, the plugin's tab shows it and retries. To move from one to
 another, stop the old one first.
@@ -87,7 +87,7 @@ bridge mode, the broker and the IL prefix (it checks an external bridge answers
 is not on the default one), then offers to fetch the devices from Tuya Cloud (a saved login is reused; a QR login
 only when there is none), which closing its window skips (it is in *Configure* later, and in the panel); the rest
 starts at its defaults and is changed in the panel's *Settings*. Deleting the integration takes its devices out of IL
-(so il-ha removes them); with the embedded bridge it also clears that bridge's retained topics and its state file.
+(so ildevice-homeassistant removes them); with the embedded bridge it also clears that bridge's retained topics and its state file.
 The device list and Tuya login it kept under `.storage/rustuya/` are deleted; a device file you pointed elsewhere, and
 everything on an external bridge, are left as they are.
 
@@ -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,17 +178,17 @@ 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).
-- `tests/e2e/test_chain_*.py`, `test_daemon.py`: the runner with il-ha's consumer model on the other side, in one process
+- `tests/e2e/test_chain_*.py`, `test_daemon.py`: the runner with ildevice-homeassistant's consumer model on the other side, in one process
   and over a real broker; the daemon as a subprocess.
 - `tests/e2e/test_manager_plugin.py`: the plugin under rustuya-manager's real plugin host (skipped without it).
 - `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.dev7}/README.md

@@ -6,17 +6,17 @@ Local control of Tuya devices through [rustuya-bridge](https://github.com/373594
 ([ildevice](https://github.com/3735943886/ildevice)) devices, and in Home Assistant. It replaces rustuya-homeassistant.
 
 ```
-rustuya-bridge ──MQTT──► rustuya-local ──MQTT (il/…)──► il-ha (Home Assistant integration), or any IL consumer
+rustuya-bridge ──MQTT──► rustuya-local ──MQTT (il/…)──► ildevice-homeassistant (Home Assistant integration), or any IL consumer
  raw LAN dps             Service:
                          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
   plugin. Its `host` package owns the runner, transports and file watchers. It only produces IL and knows nothing of Home Assistant entities.
-- **[il-ha](https://github.com/3735943886/ildevice-homeassistant)** turns IL descriptors into Home Assistant entities.
+- **[ildevice-homeassistant](https://github.com/3735943886/ildevice-homeassistant)** turns IL descriptors into Home Assistant entities.
 
 ## Daemon
 
@@ -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;
@@ -49,7 +49,7 @@ MQTT and in-process transport tests exercise the same adapter and the bidirectio
 
 Coming from rustuya-homeassistant: [docs/MIGRATING.md](docs/MIGRATING.md).
 
-Install il-ha, and run one IL producer per bridge: the daemon, the integration below, or the manager plugin. A second
+Install ildevice-homeassistant, and run one IL producer per bridge: the daemon, the integration below, or the manager plugin. A second
 one with the same IL prefix and source refuses to start while the first runs (every device would show twice): the
 daemon exits, the integration is retried by Home Assistant, the plugin's tab shows it and retries. To move from one to
 another, stop the old one first.
@@ -61,7 +61,7 @@ bridge mode, the broker and the IL prefix (it checks an external bridge answers
 is not on the default one), then offers to fetch the devices from Tuya Cloud (a saved login is reused; a QR login
 only when there is none), which closing its window skips (it is in *Configure* later, and in the panel); the rest
 starts at its defaults and is changed in the panel's *Settings*. Deleting the integration takes its devices out of IL
-(so il-ha removes them); with the embedded bridge it also clears that bridge's retained topics and its state file.
+(so ildevice-homeassistant removes them); with the embedded bridge it also clears that bridge's retained topics and its state file.
 The device list and Tuya login it kept under `.storage/rustuya/` are deleted; a device file you pointed elsewhere, and
 everything on an external bridge, are left as they are.
 
@@ -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,17 +152,17 @@ 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).
-- `tests/e2e/test_chain_*.py`, `test_daemon.py`: the runner with il-ha's consumer model on the other side, in one process
+- `tests/e2e/test_chain_*.py`, `test_daemon.py`: the runner with ildevice-homeassistant's consumer model on the other side, in one process
   and over a real broker; the daemon as a subprocess.
 - `tests/e2e/test_manager_plugin.py`: the plugin under rustuya-manager's real plugin host (skipped without it).
 - `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.dev7}/custom_components/rustuya/__init__.py

@@ -1,7 +1,7 @@
 """Rustuya as a Home Assistant integration: runs the same `rustuya_local.service.Service` the standalone
 `rustuya-local` daemon does, tied to this config entry, with an optional embedded rustuya-bridge (`pyrustuyabridge`)
-and user overrides from `<config>/rustuya_converters`. It creates no entities and does not depend on il-ha: it is only an IL
-*producer* — install il-ha (or any IL consumer) separately to turn its devices into entities.
+and user overrides from `<config>/rustuya_converters`. It creates no entities and does not depend on ildevice-homeassistant: it is only an IL
+*producer* — install ildevice-homeassistant (or any IL consumer) separately to turn its devices into entities.
 """
 
 from __future__ import annotations
@@ -105,7 +105,7 @@ async def async_setup(hass: HomeAssistant, config: dict) -> bool:
 
 def _tuya_id(hass: HomeAssistant, service: Any, device_id: str) -> str:
     """`device_id` as the Tuya device id: as given when the service drives it, else a Home Assistant device's. An IL
-    consumer registers a device with the IL id (the Tuya id) among its identifiers — il-ha as `("ildevice", id)`, under
+    consumer registers a device with the IL id (the Tuya id) among its identifiers — ildevice-homeassistant as `("ildevice", id)`, under
     whatever platform name it runs as — so any identifier value the service drives is taken, when there is exactly one.
     Unresolved, it is returned as given (and refused as an unknown device)."""
     from homeassistant.helpers import device_registry as dr
@@ -264,7 +264,7 @@ async def async_unload_entry(hass: HomeAssistant, entry: ConfigEntry) -> bool:
 
 async def async_remove_entry(hass: HomeAssistant, entry: ConfigEntry) -> None:
     """Deleted, not just unloaded (which only says `offline`, keeping everything for the next start). Clears what this
-    entry leaves behind: its IL devices (retained descriptors and values, so il-ha and other IL consumers drop them),
+    entry leaves behind: its IL devices (retained descriptors and values, so ildevice-homeassistant and other IL consumers drop them),
     with the embedded bridge also that bridge's retained topics and its state file, and the files it kept in its own
     storage directory (the device list and the Tuya login). A path the user pointed elsewhere is left alone, as is
     everything on an external bridge. A broker that cannot be reached only leaves the retained topics behind; the

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev7}/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.dev7}/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.dev7}/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.0a2",
     "paho-mqtt>=2.0",
     "rustuya-manager>=0.2.2",
     "pyrustuyabridge>=0.4",
-    "rustuya-local>=0.1.0.dev5"
+    "rustuya-local>=0.1.0.dev7"
   ],
   "single_config_entry": true,
-  "version": "0.1.0.dev5"
+  "version": "0.1.0.dev7"
 }

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev7}/custom_components/rustuya/strings.json

@@ -19,7 +19,7 @@
           "il_prefix": "IL topic prefix"
         },
         "data_description": {
-          "il_prefix": "Where the devices are published for il-ha (or any IL consumer); il-ha reads il by default."
+          "il_prefix": "Where the devices are published for ildevice-homeassistant (or any IL consumer); ildevice-homeassistant reads il by default."
         }
       },
       "embedded": {
@@ -33,7 +33,7 @@
           "il_prefix": "IL topic prefix"
         },
         "data_description": {
-          "il_prefix": "Where the devices are published for il-ha (or any IL consumer); il-ha reads il by default."
+          "il_prefix": "Where the devices are published for ildevice-homeassistant (or any IL consumer); ildevice-homeassistant reads il by default."
         }
       },
       "onboard": {
@@ -152,7 +152,7 @@
       "fields": {
         "device_id": {
           "name": "Device ID",
-          "description": "The Tuya device ID (as in the device list), or the Home Assistant device an IL consumer such as il-ha made of it."
+          "description": "The Tuya device ID (as in the device list), or the Home Assistant device an IL consumer such as ildevice-homeassistant made of it."
         },
         "dp": {
           "name": "DP",

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev7}/custom_components/rustuya/translations/en.json

@@ -19,7 +19,7 @@
           "il_prefix": "IL topic prefix"
         },
         "data_description": {
-          "il_prefix": "Where the devices are published for il-ha (or any IL consumer); il-ha reads il by default."
+          "il_prefix": "Where the devices are published for ildevice-homeassistant (or any IL consumer); ildevice-homeassistant reads il by default."
         }
       },
       "embedded": {
@@ -33,7 +33,7 @@
           "il_prefix": "IL topic prefix"
         },
         "data_description": {
-          "il_prefix": "Where the devices are published for il-ha (or any IL consumer); il-ha reads il by default."
+          "il_prefix": "Where the devices are published for ildevice-homeassistant (or any IL consumer); ildevice-homeassistant reads il by default."
         }
       },
       "onboard": {
@@ -152,7 +152,7 @@
       "fields": {
         "device_id": {
           "name": "Device ID",
-          "description": "The Tuya device ID (as in the device list), or the Home Assistant device an IL consumer such as il-ha made of it."
+          "description": "The Tuya device ID (as in the device list), or the Home Assistant device an IL consumer such as ildevice-homeassistant made of it."
         },
         "dp": {
           "name": "DP",

{rustuya_local-0.1.0.dev5 → rustuya_local-0.1.0.dev7}/custom_components/rustuya/translations/ko.json

@@ -19,7 +19,7 @@
           "il_prefix": "IL 토픽 prefix"
         },
         "data_description": {
-          "il_prefix": "il-ha(또는 다른 IL 소비자)가 읽을 기기를 게시하는 곳입니다. il-ha는 기본으로 il을 읽습니다."
+          "il_prefix": "ildevice-homeassistant(또는 다른 IL 소비자)가 읽을 기기를 게시하는 곳입니다. ildevice-homeassistant는 기본으로 il을 읽습니다."
         }
       },
       "embedded": {
@@ -33,7 +33,7 @@
           "il_prefix": "IL 토픽 prefix"
         },
         "data_description": {
-          "il_prefix": "il-ha(또는 다른 IL 소비자)가 읽을 기기를 게시하는 곳입니다. il-ha는 기본으로 il을 읽습니다."
+          "il_prefix": "ildevice-homeassistant(또는 다른 IL 소비자)가 읽을 기기를 게시하는 곳입니다. ildevice-homeassistant는 기본으로 il을 읽습니다."
         }
       },
       "onboard": {
@@ -152,7 +152,7 @@
       "fields": {
         "device_id": {
           "name": "기기 ID",
-          "description": "Tuya 기기 ID (기기 목록의 것), 또는 il-ha 같은 IL consumer가 만든 Home Assistant 기기 ID."
+          "description": "Tuya 기기 ID (기기 목록의 것), 또는 ildevice-homeassistant 같은 IL consumer가 만든 Home Assistant 기기 ID."
         },
         "dp": {
           "name": "DP",

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

@@ -176,7 +176,7 @@ const I18N = {
     act_add: "Add", act_update: "Update", act_remove: "Remove",
     confirm_remove_device: "Remove {who} from the bridge?",
     set_bridge_root: "Bridge topic root", set_bridge_root_hint: "The MQTT root rustuya-bridge uses (its mqtt_root_topic).",
-    set_il_prefix: "IL topic prefix", set_il_prefix_hint: "Where the IL devices are published; il-ha reads il by default.",
+    set_il_prefix: "IL topic prefix", set_il_prefix_hint: "Where the IL devices are published; ildevice-homeassistant reads il by default.",
     set_il_source: "IL source name", set_il_source_hint: "This producer's name on IL (one topic level).",
     set_devices_path: "Device file", set_devices_path_hint: "The tuyadevices.json rustuya-manager keeps; relative to the config directory.",
     set_bridge_state_file: "Bridge state file", set_bridge_state_file_hint: "Where the embedded bridge keeps its device registry.",
@@ -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.",
@@ -247,7 +247,7 @@ const I18N = {
     act_add: "추가", act_update: "갱신", act_remove: "삭제",
     confirm_remove_device: "{who}을(를) 브리지에서 삭제할까요?",
     set_bridge_root: "브리지 토픽 root", set_bridge_root_hint: "rustuya-bridge가 쓰는 MQTT root(mqtt_root_topic).",
-    set_il_prefix: "IL 토픽 prefix", set_il_prefix_hint: "IL 기기를 게시하는 곳. il-ha는 기본으로 il을 읽습니다.",
+    set_il_prefix: "IL 토픽 prefix", set_il_prefix_hint: "IL 기기를 게시하는 곳. ildevice-homeassistant는 기본으로 il을 읽습니다.",
     set_il_source: "IL source 이름", set_il_source_hint: "IL에서 이 생산자의 이름(토픽 한 단계).",
     set_devices_path: "기기 파일", set_devices_path_hint: "rustuya-manager가 관리하는 tuyadevices.json. config 디렉터리 기준 상대 경로.",
     set_bridge_state_file: "브리지 상태 파일", set_bridge_state_file_hint: "내장 브리지가 기기 목록을 저장하는 곳.",
@@ -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.dev7}/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:
@@ -21,7 +21,7 @@ rustuya-manager plugin. It is retired. Its replacement is two pieces:
 - **rustuya-local** turns the devices on rustuya-bridge into IL devices (MQTT topics under a prefix such as `il/tuya`).
   Run it one way: the `rustuya` Home Assistant integration (HACS), the rustuya-manager plugin (catalog: *Tuya (IL)*),
   or the `rustuya-local run` daemon.
-- **il-ha** ([ildevice-homeassistant](https://github.com/3735943886/ildevice-homeassistant), HACS) turns IL devices
+- **[ildevice-homeassistant](https://github.com/3735943886/ildevice-homeassistant)** (HACS) turns IL devices
   into Home Assistant entities. MQTT discovery is no longer used.
 
 ## What changes for you
@@ -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.
 
@@ -48,7 +48,7 @@ rustuya-manager plugin. It is retired. Its replacement is two pieces:
 2. **Install rustuya-local** one way (see the [README](../README.md#home-assistant)). Keep the same rustuya-bridge and
    device file (`tuyadevices.json`).
 
-3. **Install il-ha** from HACS and add the **IL device** integration with the prefix rustuya-local publishes under
+3. **Install ildevice-homeassistant** from HACS and add the **IL device** integration with the prefix rustuya-local publishes under
    (`il` unless you set another one in rustuya-local; both sides must match). Add the devices it offers, or turn on
    *Add discovered devices automatically*.
 
@@ -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.