@camstack/addon-provider-tuya 0.2.7 → 0.2.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/addon.js +12 -0
- package/dist/addon.mjs +12 -0
- package/package.json +1 -1
package/dist/addon.js
CHANGED
|
@@ -14010,6 +14010,18 @@ var motionCapability = {
|
|
|
14010
14010
|
name: "motion",
|
|
14011
14011
|
scope: "device",
|
|
14012
14012
|
mode: "singleton",
|
|
14013
|
+
/**
|
|
14014
|
+
* Providers register per-device natives via `ctx.registerNativeCap`
|
|
14015
|
+
* (Hikvision/Reolink/Amcrest/Wyze/HA/Homematic/Alexa/Matter) — there is
|
|
14016
|
+
* NO system singleton provider. Without this flag `resolveCapMount`
|
|
14017
|
+
* derived `{ kind: 'singleton' }`, so `motion.getStatus`/`isDetected`
|
|
14018
|
+
* resolved via `registry.getSingleton('motion')` (always null) and every
|
|
14019
|
+
* call 412'd "provider not available" while bindings listed a live
|
|
14020
|
+
* `motion` native (2026-08-02). The flag routes the router through
|
|
14021
|
+
* `requireDeviceScoped` → `getProviderForDevice`, like `motion-trigger`,
|
|
14022
|
+
* `snapshot` and every other per-device native cap.
|
|
14023
|
+
*/
|
|
14024
|
+
deviceNative: true,
|
|
14013
14025
|
deviceTypes: [DeviceType.Camera, DeviceType.Sensor],
|
|
14014
14026
|
methods: {
|
|
14015
14027
|
/**
|
package/dist/addon.mjs
CHANGED
|
@@ -14009,6 +14009,18 @@ var motionCapability = {
|
|
|
14009
14009
|
name: "motion",
|
|
14010
14010
|
scope: "device",
|
|
14011
14011
|
mode: "singleton",
|
|
14012
|
+
/**
|
|
14013
|
+
* Providers register per-device natives via `ctx.registerNativeCap`
|
|
14014
|
+
* (Hikvision/Reolink/Amcrest/Wyze/HA/Homematic/Alexa/Matter) — there is
|
|
14015
|
+
* NO system singleton provider. Without this flag `resolveCapMount`
|
|
14016
|
+
* derived `{ kind: 'singleton' }`, so `motion.getStatus`/`isDetected`
|
|
14017
|
+
* resolved via `registry.getSingleton('motion')` (always null) and every
|
|
14018
|
+
* call 412'd "provider not available" while bindings listed a live
|
|
14019
|
+
* `motion` native (2026-08-02). The flag routes the router through
|
|
14020
|
+
* `requireDeviceScoped` → `getProviderForDevice`, like `motion-trigger`,
|
|
14021
|
+
* `snapshot` and every other per-device native cap.
|
|
14022
|
+
*/
|
|
14023
|
+
deviceNative: true,
|
|
14012
14024
|
deviceTypes: [DeviceType.Camera, DeviceType.Sensor],
|
|
14013
14025
|
methods: {
|
|
14014
14026
|
/**
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@camstack/addon-provider-tuya",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.9",
|
|
4
4
|
"description": "Tuya / Smart Life device-provider addon for CamStack — account-onboarded (Tuya IoT cloud fetch of device localKeys) + LOCAL DP control via the @apocaliss92/nodetuya encrypted-LAN client, exposing switch / water-heater-family kettle entities",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"camstack",
|