@kusinta/iot-schema 0.1.0-beta.9 → 0.2.0-beta.10

package/src/kusinta/iot/signaling/v1/signaling_service_pb.d.ts

@@ -0,0 +1,34 @@
+// @generated by protoc-gen-es v2.12.0 with parameter "target=js+dts,import_extension=js"
+// @generated from file kusinta/iot/signaling/v1/signaling_service.proto (package kusinta.iot.signaling.v1, syntax proto3)
+/* eslint-disable */
+
+import type { GenFile, GenService } from "@bufbuild/protobuf/codegenv2";
+import type { GatewayConnectRequestSchema, GatewayConnectResponseSchema, UserConnectRequestSchema, UserConnectResponseSchema } from "./signaling_pb.js";
+
+/**
+ * Describes the file kusinta/iot/signaling/v1/signaling_service.proto.
+ */
+export declare const file_kusinta_iot_signaling_v1_signaling_service: GenFile;
+
+/**
+ * @generated from service kusinta.iot.signaling.v1.GatewaySignalingService
+ */
+export declare const GatewaySignalingService: GenService<{
+  /**
+   * @generated from rpc kusinta.iot.signaling.v1.GatewaySignalingService.GatewayConnect
+   */
+  gatewayConnect: {
+    methodKind: "bidi_streaming";
+    input: typeof GatewayConnectRequestSchema;
+    output: typeof GatewayConnectResponseSchema;
+  },
+  /**
+   * @generated from rpc kusinta.iot.signaling.v1.GatewaySignalingService.UserConnect
+   */
+  userConnect: {
+    methodKind: "bidi_streaming";
+    input: typeof UserConnectRequestSchema;
+    output: typeof UserConnectResponseSchema;
+  },
+}>;
+

package/src/kusinta/iot/signaling/v1/signaling_service_pb.js

@@ -0,0 +1,19 @@
+// @generated by protoc-gen-es v2.12.0 with parameter "target=js+dts,import_extension=js"
+// @generated from file kusinta/iot/signaling/v1/signaling_service.proto (package kusinta.iot.signaling.v1, syntax proto3)
+/* eslint-disable */
+
+import { fileDesc, serviceDesc } from "@bufbuild/protobuf/codegenv2";
+import { file_kusinta_iot_signaling_v1_signaling } from "./signaling_pb.js";
+
+/**
+ * Describes the file kusinta/iot/signaling/v1/signaling_service.proto.
+ */
+export const file_kusinta_iot_signaling_v1_signaling_service = /*@__PURE__*/
+  fileDesc("CjBrdXNpbnRhL2lvdC9zaWduYWxpbmcvdjEvc2lnbmFsaW5nX3NlcnZpY2UucHJvdG8SGGt1c2ludGEuaW90LnNpZ25hbGluZy52MTKCAgoXR2F0ZXdheVNpZ25hbGluZ1NlcnZpY2USdwoOR2F0ZXdheUNvbm5lY3QSLy5rdXNpbnRhLmlvdC5zaWduYWxpbmcudjEuR2F0ZXdheUNvbm5lY3RSZXF1ZXN0GjAua3VzaW50YS5pb3Quc2lnbmFsaW5nLnYxLkdhdGV3YXlDb25uZWN0UmVzcG9uc2UoATABEm4KC1VzZXJDb25uZWN0Eiwua3VzaW50YS5pb3Quc2lnbmFsaW5nLnYxLlVzZXJDb25uZWN0UmVxdWVzdBotLmt1c2ludGEuaW90LnNpZ25hbGluZy52MS5Vc2VyQ29ubmVjdFJlc3BvbnNlKAEwAUICSAFiBnByb3RvMw", [file_kusinta_iot_signaling_v1_signaling]);
+
+/**
+ * @generated from service kusinta.iot.signaling.v1.GatewaySignalingService
+ */
+export const GatewaySignalingService = /*@__PURE__*/
+  serviceDesc(file_kusinta_iot_signaling_v1_signaling_service, 0);
+

package/src/kusinta/iot/vendor/homematic/v1/homematic_pb.d.ts

@@ -11,40 +11,140 @@ import type { Message } from "@bufbuild/protobuf";
 export declare const file_kusinta_iot_vendor_homematic_v1_homematic: GenFile;
 
 /**
- * HomeMatic-specific thermostat properties not available in Matter Thermostat cluster.
- * Add new fields at the next available field number — never reuse a removed number.
+ * Who a HomeMatic device is, in its own terms. Identity, not readings — it describes the
+ * physical device, so it hangs off device.v1.DeviceDescriptor rather than off any one
+ * endpoint.
+ *
+ * @generated from message kusinta.iot.vendor.homematic.v1.HomematicDeviceIdentity
+ */
+export declare type HomematicDeviceIdentity = Message<"kusinta.iot.vendor.homematic.v1.HomematicDeviceIdentity"> & {
+  /**
+   * upstream device address, e.g. "MEQ1234567"
+   *
+   * @generated from field: string address = 1;
+   */
+  address: string;
+
+  /**
+   * aiohomematic device type string, e.g. "HmIP-eTRV-C"
+   *
+   * @generated from field: string type = 2;
+   */
+  type: string;
+};
+
+/**
+ * Describes the message kusinta.iot.vendor.homematic.v1.HomematicDeviceIdentity.
+ * Use `create(HomematicDeviceIdentitySchema)` to create a new message.
+ */
+export declare const HomematicDeviceIdentitySchema: GenMessage<HomematicDeviceIdentity>;
+
+/**
+ * HomeMatic thermostat parameters with no Matter equivalent, carried on the same endpoint
+ * as that thermostat's Matter properties rather than instead of them.
+ *
+ * "No Matter equivalent" is the entry test, and it is the one to apply before adding a
+ * field here. Valve position failed it: LEVEL is Thermostat/PIHeatingDemand, and it lived
+ * here for a while under the claim that Matter had nothing for it. It is now
+ * device.v1.ThermostatProperties.pi_heating_demand, and field 6 is burned.
+ *
+ * Battery state is deliberately NOT here. LOW_BAT and OPERATING_VOLTAGE are Matter's
+ * PowerSource cluster, which every battery device from every technology needs, so they
+ * belong on a Power Source endpoint. See device/v1/properties.proto.
+ *
+ * Every field is `optional`, for the same reason as device/v1/properties.proto: these are
+ * assembled from a PropertyUpdate stream, and zero is a real reading here too — boost_mode
+ * false means not boosting, control_mode 0 is an HmIP ControlMode value. Absent means never
+ * reported; present means a reading, including zero.
+ *
+ * Enum parameters cross the wire as the CCU's own index, not as a type this schema defines,
+ * so each one lists its values in its comment. The order is the CCU's; do not renumber it.
+ *
+ * Add new fields at the next available number — never reuse a removed one.
  *
  * @generated from message kusinta.iot.vendor.homematic.v1.HmThermostatProps
  */
 export declare type HmThermostatProps = Message<"kusinta.iot.vendor.homematic.v1.HmThermostatProps"> & {
   /**
-   * @generated from field: bool boost_mode = 1;
+   * @generated from field: optional bool boost_mode = 1;
+   */
+  boostMode?: boolean | undefined;
+
+  /**
+   * Seconds remaining, 0-2048 — the CCU counts boost in whole seconds, not minutes.
+   * Default boost is 5 min (300), maximum 30 min (1800).
+   *
+   * @generated from field: optional uint32 boost_time_remaining = 2;
+   */
+  boostTimeRemaining?: number | undefined;
+
+  /**
+   * Write-only on the CCU: it accepts a ControlMode and never reports one back. Carried
+   * here for a future write path, not as a reading — a connector that emits it as a
+   * PropertyUpdate is sending a value the device never gave. 0-3.
+   *
+   * @generated from field: optional uint32 control_mode = 3;
+   */
+  controlMode?: number | undefined;
+
+  /**
+   * @generated from field: optional bool frost_protection = 4;
+   */
+  frostProtection?: boolean | undefined;
+
+  /**
+   * Party mode active. A boolean, whatever the old field name suggested.
+   *
+   * @generated from field: optional bool party_mode = 5;
+   */
+  partyMode?: boolean | undefined;
+
+  /**
+   * CLOSED = 0, OPEN = 1
+   *
+   * @generated from field: optional uint32 window_state = 7;
    */
-  boostMode: boolean;
+  windowState?: number | undefined;
 
   /**
-   * minutes remaining in boost
+   * Valve fault and adaption state, nine CCU-defined values. Radiator valves only — a wall
+   * thermostat drives no valve and never reports it.
    *
-   * @generated from field: float boost_time_period = 2;
+   * @generated from field: optional uint32 valve_state = 8;
    */
-  boostTimePeriod: number;
+  valveState?: number | undefined;
 
   /**
-   * HmIP ControlMode enum
+   * Which schedule the thermostat is following: AUTO = 0, MANU = 1, AWAY = 2, plus a
+   * fourth CCU value. NOT webrtc.v1.SetpointAdjustMode, which names which setpoint a
+   * command targets — a different enum over a different set of concepts.
    *
-   * @generated from field: uint32 control_mode = 3;
+   * @generated from field: optional uint32 set_point_mode = 9;
    */
-  controlMode: number;
+  setPointMode?: number | undefined;
 
   /**
-   * @generated from field: bool frost_protection = 4;
+   * The active weekly profile: 1-3 on a radiator valve, 1-6 on a wall thermostat. The
+   * upper bound is the device's, not the protocol's.
+   *
+   * @generated from field: optional uint32 active_profile = 10;
    */
-  frostProtection: boolean;
+  activeProfile?: number | undefined;
 
   /**
-   * @generated from field: float current_profile_period = 5;
+   * Whether the measured temperature is usable: NORMAL = 0, UNKNOWN = 1, OVERFLOW = 2,
+   * UNDERFLOW = 3. A reading beside ACTUAL_TEMPERATURE, not a substitute for it.
+   *
+   * @generated from field: optional uint32 actual_temperature_status = 11;
+   */
+  actualTemperatureStatus?: number | undefined;
+
+  /**
+   * Valve adaption run: writing true starts the valve's stroke calibration.
+   *
+   * @generated from field: optional bool valve_adaption = 12;
    */
-  currentProfilePeriod: number;
+  valveAdaption?: boolean | undefined;
 };
 
 /**
@@ -54,41 +154,108 @@ export declare type HmThermostatProps = Message<"kusinta.iot.vendor.homematic.v1
 export declare const HmThermostatPropsSchema: GenMessage<HmThermostatProps>;
 
 /**
- * Top-level vendor extension attached to Device.properties field 50.
- * Carries the CCU3 device address + aiohomematic type string + device-type-specific props.
+ * The maintenance channel every HomeMatic device carries — device health and radio state,
+ * not what the device measures or controls.
  *
- * @generated from message kusinta.iot.vendor.homematic.v1.HomematicVendorExtension
+ * It is device-agnostic: a radiator valve, a wall thermostat and a switch actuator all
+ * report the same core set on the same channel, which is why this is one message rather
+ * than a per-device-type one. Which of these a given device actually has is model-
+ * dependent, and stated per device in device.v1.Endpoint.vendor_attribute_names — SABOTAGE
+ * especially, where "no tamper detected" and "cannot detect tamper" must not render alike.
+ *
+ * Not a Matter endpoint of its own: the maintenance channel is channel 0 upstream, and
+ * Matter reserves endpoint 0 for the root node. A connector puts these readings on the
+ * endpoint whose Matter properties they belong beside — the Power Source endpoint, whose
+ * battery attributes are derived from this same channel's LOW_BAT and OPERATING_VOLTAGE.
+ *
+ * LOW_BAT, OPERATING_VOLTAGE and OPERATING_VOLTAGE_LEVEL are deliberately absent: they are
+ * Matter's PowerSource cluster, and PowerSourceProperties carries them. Only the derived
+ * Matter value has a home there, so the raw OPERATING_VOLTAGE_STATUS enum is kept here.
+ *
+ * Every field is `optional`, for the reason HmThermostatProps gives: ERROR_CODE 0 is "no
+ * error", a reading, and SABOTAGE false is a safety claim.
+ *
+ * @generated from message kusinta.iot.vendor.homematic.v1.HmMaintenanceProps
  */
-export declare type HomematicVendorExtension = Message<"kusinta.iot.vendor.homematic.v1.HomematicVendorExtension"> & {
+export declare type HmMaintenanceProps = Message<"kusinta.iot.vendor.homematic.v1.HmMaintenanceProps"> & {
+  /**
+   * Device-defined fault code, 0-255, where 0 is no error. Present only on models that
+   * have one.
+   *
+   * @generated from field: optional uint32 error_code = 1;
+   */
+  errorCode?: number | undefined;
+
+  /**
+   * Tamper detection: true means the device reports having been removed or opened. Present
+   * only on models with the hardware for it.
+   *
+   * @generated from field: optional bool sabotage = 2;
+   */
+  sabotage?: boolean | undefined;
+
+  /**
+   * Received signal strength in dBm, -128 to 127, as this device measures it.
+   *
+   * sint32, not uint32: these are negative in normal operation, and an unsigned field would
+   * carry -72 dBm as 4294967224.
+   *
+   * @generated from field: optional sint32 rssi_device = 3;
+   */
+  rssiDevice?: number | undefined;
+
+  /**
+   * The same measurement made at the other end of the link, as reported back.
+   *
+   * @generated from field: optional sint32 rssi_peer = 4;
+   */
+  rssiPeer?: number | undefined;
+
   /**
-   * e.g. "MEQ1234567" (CCU3 device address)
+   * Supply state as the CCU reports it: NORMAL = 0, UNKNOWN = 1, OVERFLOW = 2,
+   * EXTERNAL = 3. The raw enum; PowerSourceProperties.status carries the Matter
+   * PowerSourceStatusEnum value derived from it, and the two are not interchangeable.
    *
-   * @generated from field: string homematic_address = 1;
+   * @generated from field: optional uint32 operating_voltage_status = 5;
    */
-  homematicAddress: string;
+  operatingVoltageStatus?: number | undefined;
 
   /**
-   * aiohomematic device type string e.g. "HmIP-eTRV-C"
+   * True when the gateway has lost contact with the device. Reachability as the upstream
+   * system sees it, which is not the same claim as device.v1.Device.last_seen — that is
+   * when the gateway last had evidence of the device, observed one hop further out.
    *
-   * @generated from field: string homematic_type = 2;
+   * @generated from field: optional bool unreach = 6;
    */
-  homematicType: string;
+  unreach?: boolean | undefined;
 
   /**
-   * @generated from oneof kusinta.iot.vendor.homematic.v1.HomematicVendorExtension.homematic_props
+   * True while a configuration change is queued for a device that has not yet woken to
+   * take it. A battery device can sit here for its whole report interval.
+   *
+   * @generated from field: optional bool config_pending = 7;
+   */
+  configPending?: boolean | undefined;
+
+  /**
+   * True while the device has spent its share of the radio band's transmit budget and
+   * must wait before sending again. The 868 MHz band permits roughly one percent duty
+   * cycle, and it regenerates at about that rate per half minute.
+   *
+   * Worth carrying rather than leaving to the connector, because a spent budget is
+   * indistinguishable from a working device that simply has nothing to say: it stays
+   * reachable, reports no error, and silently drops what it was asked to do. Anything
+   * that writes on a schedule needs to be able to see this before it concludes a device
+   * is ignoring it.
+   *
+   * @generated from field: optional bool duty_cycle = 8;
    */
-  homematicProps: {
-    /**
-     * @generated from field: kusinta.iot.vendor.homematic.v1.HmThermostatProps hm_thermostat = 10;
-     */
-    value: HmThermostatProps;
-    case: "hmThermostat";
-  } | { case: undefined; value?: undefined };
+  dutyCycle?: boolean | undefined;
 };
 
 /**
- * Describes the message kusinta.iot.vendor.homematic.v1.HomematicVendorExtension.
- * Use `create(HomematicVendorExtensionSchema)` to create a new message.
+ * Describes the message kusinta.iot.vendor.homematic.v1.HmMaintenanceProps.
+ * Use `create(HmMaintenancePropsSchema)` to create a new message.
  */
-export declare const HomematicVendorExtensionSchema: GenMessage<HomematicVendorExtension>;
+export declare const HmMaintenancePropsSchema: GenMessage<HmMaintenanceProps>;
 

package/src/kusinta/iot/vendor/homematic/v1/homematic_pb.js

@@ -3,24 +3,32 @@
 /* eslint-disable */
 
 import { fileDesc, messageDesc } from "@bufbuild/protobuf/codegenv2";
+import { file_kusinta_iot_vendor_v1_vendor_options } from "../../v1/vendor_options_pb.js";
 
 /**
  * Describes the file kusinta/iot/vendor/homematic/v1/homematic.proto.
  */
 export const file_kusinta_iot_vendor_homematic_v1_homematic = /*@__PURE__*/
-  fileDesc("Ci9rdXNpbnRhL2lvdC92ZW5kb3IvaG9tZW1hdGljL3YxL2hvbWVtYXRpYy5wcm90bxIfa3VzaW50YS5pb3QudmVuZG9yLmhvbWVtYXRpYy52MSKSAQoRSG1UaGVybW9zdGF0UHJvcHMSEgoKYm9vc3RfbW9kZRgBIAEoCBIZChFib29zdF90aW1lX3BlcmlvZBgCIAEoAhIUCgxjb250cm9sX21vZGUYAyABKA0SGAoQZnJvc3RfcHJvdGVjdGlvbhgEIAEoCBIeChZjdXJyZW50X3Byb2ZpbGVfcGVyaW9kGAUgASgCIq0BChhIb21lbWF0aWNWZW5kb3JFeHRlbnNpb24SGQoRaG9tZW1hdGljX2FkZHJlc3MYASABKAkSFgoOaG9tZW1hdGljX3R5cGUYAiABKAkSSwoNaG1fdGhlcm1vc3RhdBgKIAEoCzIyLmt1c2ludGEuaW90LnZlbmRvci5ob21lbWF0aWMudjEuSG1UaGVybW9zdGF0UHJvcHNIAEIRCg9ob21lbWF0aWNfcHJvcHNCAkgBYgZwcm90bzM");
+  fileDesc("Ci9rdXNpbnRhL2lvdC92ZW5kb3IvaG9tZW1hdGljL3YxL2hvbWVtYXRpYy5wcm90bxIfa3VzaW50YS5pb3QudmVuZG9yLmhvbWVtYXRpYy52MSI4ChdIb21lbWF0aWNEZXZpY2VJZGVudGl0eRIPCgdhZGRyZXNzGAEgASgJEgwKBHR5cGUYAiABKAki/wYKEUhtVGhlcm1vc3RhdFByb3BzEisKCmJvb3N0X21vZGUYASABKAhCEqK1GApCT09TVF9NT0RF0LUYBkgAiAEBEjUKFGJvb3N0X3RpbWVfcmVtYWluaW5nGAIgASgNQhKitRgKQk9PU1RfVElNRdC1GAVIAYgBARIvCgxjb250cm9sX21vZGUYAyABKA1CFKK1GAxDT05UUk9MX01PREXQtRgCSAKIAQESNwoQZnJvc3RfcHJvdGVjdGlvbhgEIAEoCEIYorUYEEZST1NUX1BST1RFQ1RJT07QtRgFSAOIAQESKwoKcGFydHlfbW9kZRgFIAEoCEISorUYClBBUlRZX01PREXQtRgFSASIAQESLwoMd2luZG93X3N0YXRlGAcgASgNQhSitRgMV0lORE9XX1NUQVRF0LUYB0gFiAEBEi0KC3ZhbHZlX3N0YXRlGAggASgNQhOitRgLVkFMVkVfU1RBVEXQtRgFSAaIAQESMwoOc2V0X3BvaW50X21vZGUYCSABKA1CFqK1GA5TRVRfUE9JTlRfTU9ERdC1GAdIB4gBARIzCg5hY3RpdmVfcHJvZmlsZRgKIAEoDUIWorUYDkFDVElWRV9QUk9GSUxF0LUYB0gIiAEBEkkKGWFjdHVhbF90ZW1wZXJhdHVyZV9zdGF0dXMYCyABKA1CIaK1GBlBQ1RVQUxfVEVNUEVSQVRVUkVfU1RBVFVT0LUYBUgJiAEBEjMKDnZhbHZlX2FkYXB0aW9uGAwgASgIQhaitRgOVkFMVkVfQURBUFRJT07QtRgHSAqIAQE6GKq1GBRob21lbWF0aWMudGhlcm1vc3RhdEINCgtfYm9vc3RfbW9kZUIXChVfYm9vc3RfdGltZV9yZW1haW5pbmdCDwoNX2NvbnRyb2xfbW9kZUITChFfZnJvc3RfcHJvdGVjdGlvbkINCgtfcGFydHlfbW9kZUIPCg1fd2luZG93X3N0YXRlQg4KDF92YWx2ZV9zdGF0ZUIRCg9fc2V0X3BvaW50X21vZGVCEQoPX2FjdGl2ZV9wcm9maWxlQhwKGl9hY3R1YWxfdGVtcGVyYXR1cmVfc3RhdHVzQhEKD192YWx2ZV9hZGFwdGlvbkoECAYQB1IFbGV2ZWxSFmN1cnJlbnRfcHJvZmlsZV9wZXJpb2RSEWJvb3N0X3RpbWVfcGVyaW9kIrYEChJIbU1haW50ZW5hbmNlUHJvcHMSKwoKZXJyb3JfY29kZRgBIAEoDUISorUYCkVSUk9SX0NPREXQtRgFSACIAQESJwoIc2Fib3RhZ2UYAiABKAhCEKK1GAhTQUJPVEFHRdC1GAVIAYgBARItCgtyc3NpX2RldmljZRgDIAEoEUITorUYC1JTU0lfREVWSUNF0LUYBUgCiAEBEikKCXJzc2lfcGVlchgEIAEoEUIRorUYCVJTU0lfUEVFUtC1GAVIA4gBARJHChhvcGVyYXRpbmdfdm9sdGFnZV9zdGF0dXMYBSABKA1CIKK1GBhPUEVSQVRJTkdfVk9MVEFHRV9TVEFUVVPQtRgFSASIAQESJQoHdW5yZWFjaBgGIAEoCEIPorUYB1VOUkVBQ0jQtRgFSAWIAQESMwoOY29uZmlnX3BlbmRpbmcYByABKAhCFqK1GA5DT05GSUdfUEVORElOR9C1GAVIBogBARIrCgpkdXR5X2N5Y2xlGAggASgIQhKitRgKRFVUWV9DWUNMRdC1GAVIB4gBAToZqrUYFWhvbWVtYXRpYy5tYWludGVuYW5jZUINCgtfZXJyb3JfY29kZUILCglfc2Fib3RhZ2VCDgoMX3Jzc2lfZGV2aWNlQgwKCl9yc3NpX3BlZXJCGwoZX29wZXJhdGluZ192b2x0YWdlX3N0YXR1c0IKCghfdW5yZWFjaEIRCg9fY29uZmlnX3BlbmRpbmdCDQoLX2R1dHlfY3ljbGVCAkgBYgZwcm90bzM", [file_kusinta_iot_vendor_v1_vendor_options]);
+
+/**
+ * Describes the message kusinta.iot.vendor.homematic.v1.HomematicDeviceIdentity.
+ * Use `create(HomematicDeviceIdentitySchema)` to create a new message.
+ */
+export const HomematicDeviceIdentitySchema = /*@__PURE__*/
+  messageDesc(file_kusinta_iot_vendor_homematic_v1_homematic, 0);
 
 /**
  * Describes the message kusinta.iot.vendor.homematic.v1.HmThermostatProps.
  * Use `create(HmThermostatPropsSchema)` to create a new message.
  */
 export const HmThermostatPropsSchema = /*@__PURE__*/
-  messageDesc(file_kusinta_iot_vendor_homematic_v1_homematic, 0);
+  messageDesc(file_kusinta_iot_vendor_homematic_v1_homematic, 1);
 
 /**
- * Describes the message kusinta.iot.vendor.homematic.v1.HomematicVendorExtension.
- * Use `create(HomematicVendorExtensionSchema)` to create a new message.
+ * Describes the message kusinta.iot.vendor.homematic.v1.HmMaintenanceProps.
+ * Use `create(HmMaintenancePropsSchema)` to create a new message.
  */
-export const HomematicVendorExtensionSchema = /*@__PURE__*/
-  messageDesc(file_kusinta_iot_vendor_homematic_v1_homematic, 1);
+export const HmMaintenancePropsSchema = /*@__PURE__*/
+  messageDesc(file_kusinta_iot_vendor_homematic_v1_homematic, 2);
 

package/src/kusinta/iot/vendor/v1/vendor_options_pb.d.ts

@@ -0,0 +1,71 @@
+// @generated by protoc-gen-es v2.12.0 with parameter "target=js+dts,import_extension=js"
+// @generated from file kusinta/iot/vendor/v1/vendor_options.proto (package kusinta.iot.vendor.v1, syntax proto3)
+/* eslint-disable */
+
+import type { GenExtension, GenFile } from "@bufbuild/protobuf/codegenv2";
+import type { FieldOptions, MessageOptions } from "@bufbuild/protobuf/wkt";
+
+/**
+ * Describes the file kusinta/iot/vendor/v1/vendor_options.proto.
+ */
+export declare const file_kusinta_iot_vendor_v1_vendor_options: GenFile;
+
+/**
+ * The vendor parameter this field carries, in the vendor's own spelling — e.g.
+ * "LEVEL", not "level". Matches device.v1.PropertyUpdate.attribute_name byte for byte
+ * when that update names a vendor extension.
+ *
+ * This and the Matter annotations are mutually exclusive: a field is either a Matter
+ * attribute or a vendor parameter. Which branch a PropertyUpdate takes is decided by
+ * whether it names a vendor extension, never by inspecting both.
+ *
+ * Must be unique within the message it appears in — the vendor branch matches one
+ * field of one message, so a repeat would make resolution ambiguous.
+ *
+ * @generated from extension: string vendor_attribute = 50004;
+ */
+export declare const vendor_attribute: GenExtension<FieldOptions, string>;
+
+/**
+ * What this vendor parameter supports, as the same bitmask device/v1/matter_options.proto
+ * defines: READ = 1, WRITE = 2, REPORT = 4.
+ *
+ * One mask across both branches on purpose. Bit 4 is Matter's reportable quality and, for
+ * HomeMatic, the parameter's EVENT bit — the same fact under two names, so a consumer
+ * deciding whether to draw a control or a reading asks one question either way.
+ *
+ * Where the value comes from is the difference. The Matter side reads its mask off the
+ * specification; a vendor parameter has no spec to defer to, so this is the upstream
+ * system's own answer about its own parameter — for HomeMatic, the OPERATIONS value the
+ * CCU reports in getParamsetDescription().
+ *
+ * Not permission, and not the implemented set: see matter_attribute_capabilities for both
+ * distinctions. The vendor mirror of the implemented set is
+ * device.v1.Endpoint.vendor_attribute_names.
+ *
+ * @generated from extension: uint32 vendor_attribute_capabilities = 50010;
+ */
+export declare const vendor_attribute_capabilities: GenExtension<FieldOptions, number>;
+
+/**
+ * The stable key identifying a vendor extension message, e.g. "homematic.thermostat".
+ * Matches device.v1.PropertyUpdate.vendor_extension byte for byte, and is what selects
+ * the Endpoint.vendor_properties case.
+ *
+ * One key per message carried in Endpoint.vendor_properties, so the vendor branch of the
+ * resolution rule is the same shape as the Matter branch: pick a message by a message
+ * option, then one field by a field option. Nothing nests.
+ *
+ * Form: "<vendor>.<what the message models>", lower_snake_case on both sides —
+ * "homematic.thermostat", and a humidity one would be "homematic.humidity_sensor". The
+ * vendor half alone is NOT a key: a vendor has one message per device type it extends,
+ * and two sharing a key would make the branch non-deterministic. A test asserts they
+ * are distinct, but it cannot tell you which of two is wrong, so keep to the form.
+ *
+ * Not derived from the package or message name — this is the authoritative spelling,
+ * exactly as matter_attribute is on the Matter side.
+ *
+ * @generated from extension: string vendor_extension = 50005;
+ */
+export declare const vendor_extension: GenExtension<MessageOptions, string>;
+

package/src/kusinta/iot/vendor/v1/vendor_options_pb.js

@@ -0,0 +1,75 @@
+// @generated by protoc-gen-es v2.12.0 with parameter "target=js+dts,import_extension=js"
+// @generated from file kusinta/iot/vendor/v1/vendor_options.proto (package kusinta.iot.vendor.v1, syntax proto3)
+/* eslint-disable */
+
+import { extDesc, fileDesc } from "@bufbuild/protobuf/codegenv2";
+import { file_google_protobuf_descriptor } from "@bufbuild/protobuf/wkt";
+
+/**
+ * Describes the file kusinta/iot/vendor/v1/vendor_options.proto.
+ */
+export const file_kusinta_iot_vendor_v1_vendor_options = /*@__PURE__*/
+  fileDesc("CiprdXNpbnRhL2lvdC92ZW5kb3IvdjEvdmVuZG9yX29wdGlvbnMucHJvdG8SFWt1c2ludGEuaW90LnZlbmRvci52MTpKChB2ZW5kb3JfYXR0cmlidXRlEh0uZ29vZ2xlLnByb3RvYnVmLkZpZWxkT3B0aW9ucxjUhgMgASgJUg92ZW5kb3JBdHRyaWJ1dGU6YwoddmVuZG9yX2F0dHJpYnV0ZV9jYXBhYmlsaXRpZXMSHS5nb29nbGUucHJvdG9idWYuRmllbGRPcHRpb25zGNqGAyABKA1SG3ZlbmRvckF0dHJpYnV0ZUNhcGFiaWxpdGllczpMChB2ZW5kb3JfZXh0ZW5zaW9uEh8uZ29vZ2xlLnByb3RvYnVmLk1lc3NhZ2VPcHRpb25zGNWGAyABKAlSD3ZlbmRvckV4dGVuc2lvbmIGcHJvdG8z", [file_google_protobuf_descriptor]);
+
+/**
+ * The vendor parameter this field carries, in the vendor's own spelling — e.g.
+ * "LEVEL", not "level". Matches device.v1.PropertyUpdate.attribute_name byte for byte
+ * when that update names a vendor extension.
+ *
+ * This and the Matter annotations are mutually exclusive: a field is either a Matter
+ * attribute or a vendor parameter. Which branch a PropertyUpdate takes is decided by
+ * whether it names a vendor extension, never by inspecting both.
+ *
+ * Must be unique within the message it appears in — the vendor branch matches one
+ * field of one message, so a repeat would make resolution ambiguous.
+ *
+ * @generated from extension: string vendor_attribute = 50004;
+ */
+export const vendor_attribute = /*@__PURE__*/
+  extDesc(file_kusinta_iot_vendor_v1_vendor_options, 0);
+
+/**
+ * What this vendor parameter supports, as the same bitmask device/v1/matter_options.proto
+ * defines: READ = 1, WRITE = 2, REPORT = 4.
+ *
+ * One mask across both branches on purpose. Bit 4 is Matter's reportable quality and, for
+ * HomeMatic, the parameter's EVENT bit — the same fact under two names, so a consumer
+ * deciding whether to draw a control or a reading asks one question either way.
+ *
+ * Where the value comes from is the difference. The Matter side reads its mask off the
+ * specification; a vendor parameter has no spec to defer to, so this is the upstream
+ * system's own answer about its own parameter — for HomeMatic, the OPERATIONS value the
+ * CCU reports in getParamsetDescription().
+ *
+ * Not permission, and not the implemented set: see matter_attribute_capabilities for both
+ * distinctions. The vendor mirror of the implemented set is
+ * device.v1.Endpoint.vendor_attribute_names.
+ *
+ * @generated from extension: uint32 vendor_attribute_capabilities = 50010;
+ */
+export const vendor_attribute_capabilities = /*@__PURE__*/
+  extDesc(file_kusinta_iot_vendor_v1_vendor_options, 1);
+
+/**
+ * The stable key identifying a vendor extension message, e.g. "homematic.thermostat".
+ * Matches device.v1.PropertyUpdate.vendor_extension byte for byte, and is what selects
+ * the Endpoint.vendor_properties case.
+ *
+ * One key per message carried in Endpoint.vendor_properties, so the vendor branch of the
+ * resolution rule is the same shape as the Matter branch: pick a message by a message
+ * option, then one field by a field option. Nothing nests.
+ *
+ * Form: "<vendor>.<what the message models>", lower_snake_case on both sides —
+ * "homematic.thermostat", and a humidity one would be "homematic.humidity_sensor". The
+ * vendor half alone is NOT a key: a vendor has one message per device type it extends,
+ * and two sharing a key would make the branch non-deterministic. A test asserts they
+ * are distinct, but it cannot tell you which of two is wrong, so keep to the form.
+ *
+ * Not derived from the package or message name — this is the authoritative spelling,
+ * exactly as matter_attribute is on the Matter side.
+ *
+ * @generated from extension: string vendor_extension = 50005;
+ */
+export const vendor_extension = /*@__PURE__*/
+  extDesc(file_kusinta_iot_vendor_v1_vendor_options, 2);
+