@mhome/app-facade-protocol 1.115.0 → 1.116.0
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/contract/resource-read-v1.md +7 -0
- package/manifest/app-facade.v1.json +1 -1
- package/manifest/authorization.v1.json +1 -1
- package/manifest/host-provision-targets.v1.json +1 -1
- package/manifest/hub-targets.v1.json +1 -1
- package/manifest/pod-targets.v1.json +1 -1
- package/manifest/routing.v1.json +1 -1
- package/manifest/targets.v1.json +1 -1
- package/package.json +1 -1
- package/protocol.json +1 -1
|
@@ -124,3 +124,10 @@ values, Duration values and schedule wall-clock times are not inferred to be dat
|
|
|
124
124
|
Widget resources use `displayName` as their only human-readable name. Display names
|
|
125
125
|
may repeat; identity and references use Widget IDs. Configuration patches may omit
|
|
126
126
|
`displayName` to preserve it. Essential and Full both retain this name.
|
|
127
|
+
|
|
128
|
+
Device definition list/detail rows may carry `parent`, a provider-local physical
|
|
129
|
+
device grouping key scoped by Space, Integration and Connection. It does not name
|
|
130
|
+
a Core Device Group or require a separate parent Entity. Optional `setupStatus`
|
|
131
|
+
(`pending`, `failed`, `ready`) describes initial provider admission independently
|
|
132
|
+
of user enablement and subsequent online/offline observations. Essential device
|
|
133
|
+
lists retain both fields.
|
package/manifest/routing.v1.json
CHANGED
package/manifest/targets.v1.json
CHANGED
package/package.json
CHANGED