@kusinta/iot-schema 0.2.0-beta.45 → 0.2.0-beta.47

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kusinta/iot-schema",
-  "version": "0.2.0-beta.45",
+  "version": "0.2.0-beta.47",
   "type": "module",
   "license": "MIT",
   "files": ["src"],

package/src/kusinta/iot/access/v1/acl_pb.d.ts

@@ -447,7 +447,10 @@ export enum ServiceSignal {
 
   /**
    * How the home is set up: the apartment and its rooms, their names and descriptions, the
-   * rooms' limits, and the building's sensors in them.
+   * rooms' outer limits with when each was set, and the role that set each save an installer
+   * under a grant — never the household's inner limits — and the building's sensors in them.
+   * While the home stood empty, before anyone moved in, its property owner and gateway
+   * administrators saw its rooms and modes in full (webrtc.v1 household.proto, EMPTY HOME).
    *
    * @generated from enum value: SERVICE_SIGNAL_ROOM_SETUP = 7;
    */

package/src/kusinta/iot/access/v1/roles_pb.d.ts

@@ -223,7 +223,9 @@ export declare const PermissionActionSchema: GenEnum<PermissionAction>;
  *     operate none of them. Of what they reach of the home — from the room they are filed
  *     on, or all of it — they see how its rooms are set up, with
  *     RoomClimate.state_withheld marking what is not shown, and its links with
- *     DeviceLink.details_withheld; modes on a home are not sent to them at all. Service
+ *     DeviceLink.details_withheld; modes on a home are not sent to them at all — save that the
+ *     property owner and the gateway administrators are sent an empty home's rooms and modes
+ *     in full (webrtc.v1 household.proto, EMPTY HOME). Service
  *     that reaches the apartment itself also gets its climate summary over the disclosed
  *     period. What they newly see of the home reaches them as it happens; what they lose,
  *     at once.

package/src/kusinta/iot/access/v1/roles_pb.js

@@ -127,7 +127,9 @@ export const MembershipRelationSchema = /*@__PURE__*/
  *     operate none of them. Of what they reach of the home — from the room they are filed
  *     on, or all of it — they see how its rooms are set up, with
  *     RoomClimate.state_withheld marking what is not shown, and its links with
- *     DeviceLink.details_withheld; modes on a home are not sent to them at all. Service
+ *     DeviceLink.details_withheld; modes on a home are not sent to them at all — save that the
+ *     property owner and the gateway administrators are sent an empty home's rooms and modes
+ *     in full (webrtc.v1 household.proto, EMPTY HOME). Service
  *     that reaches the apartment itself also gets its climate summary over the disclosed
  *     period. What they newly see of the home reaches them as it happens; what they lose,
  *     at once.

package/src/kusinta/iot/accountlink/v1/account_link_pb.d.ts

@@ -395,6 +395,13 @@ export declare const TokenRefreshedSchema: GenMessage<TokenRefreshed>;
  * and it outlives a household handover's wipe and a gateway-wide wipe, which delete the
  * grant itself: it is the only means left of ending the link at the service.
  *
+ * A service with no means of revoking a grant is answered REJECTED by the api-server without
+ * asking the service. The gateway drops the token as for any REJECTED, and the grant stays
+ * valid at the service until it expires or the account holder removes the access there. So an
+ * app never tells the household that the service revoked the access, only that the home no
+ * longer holds it; where the service has no revocation, it may say that the access is removed
+ * at the service by the account holder.
+ *
  * @generated from message kusinta.iot.accountlink.v1.RevokeToken
  */
 export declare type RevokeToken = Message<"kusinta.iot.accountlink.v1.RevokeToken"> & {
@@ -434,8 +441,9 @@ export declare type TokenRevoked = Message<"kusinta.iot.accountlink.v1.TokenRevo
   requestId: string;
 
   /**
-   * OK: revoked. REJECTED: the service no longer knew the token, which is as good.
-   * UNAVAILABLE: ask again after retry_after.
+   * OK: revoked. REJECTED: the service no longer knew the token, which is as good — or it has
+   * no means of revoking one, which the api-server answers without asking it (RevokeToken);
+   * either way the gateway drops the token. UNAVAILABLE: ask again after retry_after.
    *
    * @generated from field: kusinta.iot.accountlink.v1.TokenOutcome outcome = 2;
    */