matterbridge 3.0.7-dev-20250620-076b34c → 3.0.7

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.
Files changed (188) hide show
  1. package/CHANGELOG.md +3 -2
  2. package/README-DEV.md +4 -4
  3. package/dist/cli.d.ts +29 -0
  4. package/dist/cli.d.ts.map +1 -0
  5. package/dist/cli.js +62 -2
  6. package/dist/cli.js.map +1 -0
  7. package/dist/clusters/export.d.ts +2 -0
  8. package/dist/clusters/export.d.ts.map +1 -0
  9. package/dist/clusters/export.js +2 -0
  10. package/dist/clusters/export.js.map +1 -0
  11. package/dist/defaultConfigSchema.d.ts +27 -0
  12. package/dist/defaultConfigSchema.d.ts.map +1 -0
  13. package/dist/defaultConfigSchema.js +23 -0
  14. package/dist/defaultConfigSchema.js.map +1 -0
  15. package/dist/deviceManager.d.ts +114 -0
  16. package/dist/deviceManager.d.ts.map +1 -0
  17. package/dist/deviceManager.js +94 -1
  18. package/dist/deviceManager.js.map +1 -0
  19. package/dist/devices/export.d.ts +5 -0
  20. package/dist/devices/export.d.ts.map +1 -0
  21. package/dist/devices/export.js +2 -0
  22. package/dist/devices/export.js.map +1 -0
  23. package/dist/evse.d.ts +67 -0
  24. package/dist/evse.d.ts.map +1 -0
  25. package/dist/evse.js +65 -9
  26. package/dist/evse.js.map +1 -0
  27. package/dist/frontend.d.ts +256 -0
  28. package/dist/frontend.d.ts.map +1 -0
  29. package/dist/frontend.js +374 -16
  30. package/dist/frontend.js.map +1 -0
  31. package/dist/globalMatterbridge.d.ts +32 -0
  32. package/dist/globalMatterbridge.d.ts.map +1 -0
  33. package/dist/globalMatterbridge.js +20 -0
  34. package/dist/globalMatterbridge.js.map +1 -0
  35. package/dist/helpers.d.ts +47 -0
  36. package/dist/helpers.d.ts.map +1 -0
  37. package/dist/helpers.js +51 -0
  38. package/dist/helpers.js.map +1 -0
  39. package/dist/index.d.ts +37 -0
  40. package/dist/index.d.ts.map +1 -0
  41. package/dist/index.js +28 -1
  42. package/dist/index.js.map +1 -0
  43. package/dist/laundryWasher.d.ts +243 -0
  44. package/dist/laundryWasher.d.ts.map +1 -0
  45. package/dist/laundryWasher.js +92 -7
  46. package/dist/laundryWasher.js.map +1 -0
  47. package/dist/logger/export.d.ts +2 -0
  48. package/dist/logger/export.d.ts.map +1 -0
  49. package/dist/logger/export.js +1 -0
  50. package/dist/logger/export.js.map +1 -0
  51. package/dist/matter/behaviors.d.ts +2 -0
  52. package/dist/matter/behaviors.d.ts.map +1 -0
  53. package/dist/matter/behaviors.js +2 -0
  54. package/dist/matter/behaviors.js.map +1 -0
  55. package/dist/matter/clusters.d.ts +2 -0
  56. package/dist/matter/clusters.d.ts.map +1 -0
  57. package/dist/matter/clusters.js +2 -0
  58. package/dist/matter/clusters.js.map +1 -0
  59. package/dist/matter/devices.d.ts +2 -0
  60. package/dist/matter/devices.d.ts.map +1 -0
  61. package/dist/matter/devices.js +2 -0
  62. package/dist/matter/devices.js.map +1 -0
  63. package/dist/matter/endpoints.d.ts +2 -0
  64. package/dist/matter/endpoints.d.ts.map +1 -0
  65. package/dist/matter/endpoints.js +2 -0
  66. package/dist/matter/endpoints.js.map +1 -0
  67. package/dist/matter/export.d.ts +5 -0
  68. package/dist/matter/export.d.ts.map +1 -0
  69. package/dist/matter/export.js +2 -0
  70. package/dist/matter/export.js.map +1 -0
  71. package/dist/matter/types.d.ts +3 -0
  72. package/dist/matter/types.d.ts.map +1 -0
  73. package/dist/matter/types.js +2 -0
  74. package/dist/matter/types.js.map +1 -0
  75. package/dist/matterbridge.d.ts +445 -0
  76. package/dist/matterbridge.d.ts.map +1 -0
  77. package/dist/matterbridge.js +748 -46
  78. package/dist/matterbridge.js.map +1 -0
  79. package/dist/matterbridgeAccessoryPlatform.d.ts +40 -0
  80. package/dist/matterbridgeAccessoryPlatform.d.ts.map +1 -0
  81. package/dist/matterbridgeAccessoryPlatform.js +34 -0
  82. package/dist/matterbridgeAccessoryPlatform.js.map +1 -0
  83. package/dist/matterbridgeBehaviors.d.ts +1333 -0
  84. package/dist/matterbridgeBehaviors.d.ts.map +1 -0
  85. package/dist/matterbridgeBehaviors.js +54 -1
  86. package/dist/matterbridgeBehaviors.js.map +1 -0
  87. package/dist/matterbridgeDeviceTypes.d.ts +644 -0
  88. package/dist/matterbridgeDeviceTypes.d.ts.map +1 -0
  89. package/dist/matterbridgeDeviceTypes.js +578 -15
  90. package/dist/matterbridgeDeviceTypes.js.map +1 -0
  91. package/dist/matterbridgeDynamicPlatform.d.ts +40 -0
  92. package/dist/matterbridgeDynamicPlatform.d.ts.map +1 -0
  93. package/dist/matterbridgeDynamicPlatform.js +34 -0
  94. package/dist/matterbridgeDynamicPlatform.js.map +1 -0
  95. package/dist/matterbridgeEndpoint.d.ts +1145 -0
  96. package/dist/matterbridgeEndpoint.d.ts.map +1 -0
  97. package/dist/matterbridgeEndpoint.js +995 -40
  98. package/dist/matterbridgeEndpoint.js.map +1 -0
  99. package/dist/matterbridgeEndpointHelpers.d.ts +3083 -0
  100. package/dist/matterbridgeEndpointHelpers.d.ts.map +1 -0
  101. package/dist/matterbridgeEndpointHelpers.js +204 -10
  102. package/dist/matterbridgeEndpointHelpers.js.map +1 -0
  103. package/dist/matterbridgePlatform.d.ts +290 -0
  104. package/dist/matterbridgePlatform.d.ts.map +1 -0
  105. package/dist/matterbridgePlatform.js +221 -6
  106. package/dist/matterbridgePlatform.js.map +1 -0
  107. package/dist/matterbridgeTypes.d.ts +196 -0
  108. package/dist/matterbridgeTypes.d.ts.map +1 -0
  109. package/dist/matterbridgeTypes.js +24 -0
  110. package/dist/matterbridgeTypes.js.map +1 -0
  111. package/dist/pluginManager.d.ts +273 -0
  112. package/dist/pluginManager.d.ts.map +1 -0
  113. package/dist/pluginManager.js +269 -3
  114. package/dist/pluginManager.js.map +1 -0
  115. package/dist/roboticVacuumCleaner.d.ts +102 -0
  116. package/dist/roboticVacuumCleaner.d.ts.map +1 -0
  117. package/dist/roboticVacuumCleaner.js +81 -6
  118. package/dist/roboticVacuumCleaner.js.map +1 -0
  119. package/dist/shelly.d.ts +161 -0
  120. package/dist/shelly.d.ts.map +1 -0
  121. package/dist/shelly.js +155 -7
  122. package/dist/shelly.js.map +1 -0
  123. package/dist/storage/export.d.ts +2 -0
  124. package/dist/storage/export.d.ts.map +1 -0
  125. package/dist/storage/export.js +1 -0
  126. package/dist/storage/export.js.map +1 -0
  127. package/dist/update.d.ts +58 -0
  128. package/dist/update.d.ts.map +1 -0
  129. package/dist/update.js +53 -0
  130. package/dist/update.js.map +1 -0
  131. package/dist/utils/colorUtils.d.ts +61 -0
  132. package/dist/utils/colorUtils.d.ts.map +1 -0
  133. package/dist/utils/colorUtils.js +205 -2
  134. package/dist/utils/colorUtils.js.map +1 -0
  135. package/dist/utils/commandLine.d.ts +58 -0
  136. package/dist/utils/commandLine.d.ts.map +1 -0
  137. package/dist/utils/commandLine.js +53 -0
  138. package/dist/utils/commandLine.js.map +1 -0
  139. package/dist/utils/copyDirectory.d.ts +32 -0
  140. package/dist/utils/copyDirectory.d.ts.map +1 -0
  141. package/dist/utils/copyDirectory.js +37 -1
  142. package/dist/utils/copyDirectory.js.map +1 -0
  143. package/dist/utils/createDirectory.d.ts +32 -0
  144. package/dist/utils/createDirectory.d.ts.map +1 -0
  145. package/dist/utils/createDirectory.js +31 -0
  146. package/dist/utils/createDirectory.js.map +1 -0
  147. package/dist/utils/createZip.d.ts +38 -0
  148. package/dist/utils/createZip.d.ts.map +1 -0
  149. package/dist/utils/createZip.js +42 -2
  150. package/dist/utils/createZip.js.map +1 -0
  151. package/dist/utils/deepCopy.d.ts +31 -0
  152. package/dist/utils/deepCopy.d.ts.map +1 -0
  153. package/dist/utils/deepCopy.js +38 -0
  154. package/dist/utils/deepCopy.js.map +1 -0
  155. package/dist/utils/deepEqual.d.ts +53 -0
  156. package/dist/utils/deepEqual.d.ts.map +1 -0
  157. package/dist/utils/deepEqual.js +71 -1
  158. package/dist/utils/deepEqual.js.map +1 -0
  159. package/dist/utils/export.d.ts +12 -0
  160. package/dist/utils/export.d.ts.map +1 -0
  161. package/dist/utils/export.js +1 -0
  162. package/dist/utils/export.js.map +1 -0
  163. package/dist/utils/hex.d.ts +48 -0
  164. package/dist/utils/hex.d.ts.map +1 -0
  165. package/dist/utils/hex.js +57 -0
  166. package/dist/utils/hex.js.map +1 -0
  167. package/dist/utils/isvalid.d.ts +102 -0
  168. package/dist/utils/isvalid.d.ts.map +1 -0
  169. package/dist/utils/isvalid.js +100 -0
  170. package/dist/utils/isvalid.js.map +1 -0
  171. package/dist/utils/network.d.ts +69 -0
  172. package/dist/utils/network.d.ts.map +1 -0
  173. package/dist/utils/network.js +76 -5
  174. package/dist/utils/network.js.map +1 -0
  175. package/dist/utils/spawn.d.ts +12 -0
  176. package/dist/utils/spawn.d.ts.map +1 -0
  177. package/dist/utils/spawn.js +16 -0
  178. package/dist/utils/spawn.js.map +1 -0
  179. package/dist/utils/wait.d.ts +52 -0
  180. package/dist/utils/wait.d.ts.map +1 -0
  181. package/dist/utils/wait.js +58 -9
  182. package/dist/utils/wait.js.map +1 -0
  183. package/dist/waterHeater.d.ts +90 -0
  184. package/dist/waterHeater.d.ts.map +1 -0
  185. package/dist/waterHeater.js +62 -2
  186. package/dist/waterHeater.js.map +1 -0
  187. package/npm-shrinkwrap.json +2 -2
  188. package/package.json +2 -1
@@ -0,0 +1,644 @@
1
+ /**
2
+ * This file contains the class MatterbridgeDevice.
3
+ *
4
+ * @file matterbridgeDeviceTypes.ts
5
+ * @author Luca Liguori
6
+ * @date 2024-11-08
7
+ * @version 1.0.0
8
+ *
9
+ * Copyright 2024, 2025, 2026 Luca Liguori.
10
+ *
11
+ * Licensed under the Apache License, Version 2.0 (the "License");
12
+ * you may not use this file except in compliance with the License.
13
+ * You may obtain a copy of the License at
14
+ *
15
+ * http://www.apache.org/licenses/LICENSE-2.0
16
+ *
17
+ * Unless required by applicable law or agreed to in writing, software
18
+ * distributed under the License is distributed on an "AS IS" BASIS,
19
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
20
+ * See the License for the specific language governing permissions and
21
+ * limitations under the License. *
22
+ */
23
+ import { ClusterId, DeviceTypeId, EndpointNumber } from '@matter/main';
24
+ import { Semtag } from '@matter/main/types';
25
+ export declare enum DeviceClasses {
26
+ /** Node device type. */
27
+ Node = "Node",
28
+ /**
29
+ * Application device type.
30
+ * Application devices types are typically the most datatype endpoints on a node and in the network.
31
+ */
32
+ App = "App",
33
+ /**
34
+ * Utility device type.
35
+ * A Utility device type supports configuration and settings.
36
+ */
37
+ Utility = "Utility",
38
+ /**
39
+ * Simple device type.
40
+ * A Simple device type supports local control that is persistent, independent, and unsupervised.
41
+ */
42
+ Simple = "Simple",
43
+ /**
44
+ * Dynamic device type.
45
+ * A Dynamic device type supports intelligent and supervisory services, such as commissioning,
46
+ * monitoring, trend analysis, scheduling and central management. A dynamic device type is an
47
+ * application device type.
48
+ */
49
+ Dynamic = "Dynamic",
50
+ /** There exists a client application cluster on the endpoint. */
51
+ Client = "Client",
52
+ /** There exists a server application cluster on the endpoint. */
53
+ Server = "Server",
54
+ /** The device type is composed of 2 or more device types. */
55
+ Composed = "Composed",
56
+ /** The endpoint and at least one of its sibling endpoints have an overlap in application device type(s). */
57
+ Duplicate = "Duplicate",
58
+ /**
59
+ * The endpoint represents a Bridged Device, for which information about the state of
60
+ * its power source is available to the Bridge
61
+ */
62
+ BridgedPowerSourceInfo = "BridgedPowerSourceInfo"
63
+ }
64
+ export interface DeviceTypeDefinition {
65
+ name: string;
66
+ code: DeviceTypeId;
67
+ deviceClass: DeviceClasses;
68
+ revision: number;
69
+ requiredServerClusters: ClusterId[];
70
+ optionalServerClusters: ClusterId[];
71
+ requiredClientClusters: ClusterId[];
72
+ optionalClientClusters: ClusterId[];
73
+ }
74
+ export declare const DeviceTypeDefinition: ({ name, code, deviceClass, revision, requiredServerClusters, optionalServerClusters, requiredClientClusters, optionalClientClusters, }: {
75
+ name: string;
76
+ code: number;
77
+ deviceClass: DeviceClasses;
78
+ revision: number;
79
+ requiredServerClusters?: ClusterId[];
80
+ optionalServerClusters?: ClusterId[];
81
+ requiredClientClusters?: ClusterId[];
82
+ optionalClientClusters?: ClusterId[];
83
+ }) => DeviceTypeDefinition;
84
+ export interface MatterbridgeEndpointOptions extends EndpointOptions {
85
+ tagList?: Semtag[];
86
+ }
87
+ export interface EndpointOptions {
88
+ endpointId?: EndpointNumber;
89
+ uniqueStorageKey?: string;
90
+ }
91
+ export declare const powerSource: DeviceTypeDefinition;
92
+ export declare const OTARequestor: DeviceTypeDefinition;
93
+ export declare const OTAProvider: DeviceTypeDefinition;
94
+ /**
95
+ 2.5.3. Conditions
96
+ Please see the Base Device Type definition for conformance tags.
97
+ This device type SHALL only be used for Nodes which have a device type of Bridge.
98
+
99
+ 2.5.5. Cluster Requirements
100
+ Each endpoint supporting this device type SHALL include these clusters based on the conformance
101
+ defined below.
102
+ - 0x0039 Bridged Device Basic Information Server
103
+
104
+ 2.5.6. Endpoint Composition
105
+ • A Bridged Node endpoint SHALL support one of the following composition patterns:
106
+ ◦ Separate Endpoints: All application device types are supported on separate endpoints, and
107
+ not on the Bridged Node endpoint. The Bridged Node endpoint’s Descriptor cluster PartsList
108
+ attribute SHALL indicate a list of all endpoints representing the functionality of the bridged
109
+ device, including the endpoints supporting the application device types, i.e. the full-family
110
+ pattern defined in the System Model specification.
111
+ ◦ One Endpoint: Both the Bridged Node and one or more application device types are sup
112
+ ported on the same endpoint (following application device type rules). Endpoint composi
113
+ tion SHALL conform to the application device type(s) definition
114
+ */
115
+ export declare const bridgedNode: DeviceTypeDefinition;
116
+ /**
117
+ * An Electrical Sensor device measures the electrical power and/or energy being imported and/or
118
+ * exported.
119
+ * It is a utility device type that provides information about the electrical power and/or energy
120
+ * consumption and generation.
121
+ *
122
+ * 2.6.3. Device Type Requirements
123
+ * Electrical measurements made by either the Electrical Power Measurement cluster, the Electrical
124
+ * Energy Measurement cluster, or both SHALL apply to the endpoints indicated by the Power Topology
125
+ * cluster.
126
+ */
127
+ export declare const electricalSensor: DeviceTypeDefinition;
128
+ /**
129
+ * A Device Energy Management device provides reporting and optionally adjustment of the electrical
130
+ * power planned on being consumed or produced by the device.
131
+ */
132
+ export declare const deviceEnergyManagement: DeviceTypeDefinition;
133
+ /**
134
+ * Element Requirements:
135
+ * - Identify Command TriggerEffect
136
+ * - Scenes Management Command CopyScene
137
+ * - On/Off Feature Lighting
138
+ * - Level Control Feature OnOff
139
+ * - Level Control Feature Lighting
140
+ * - Level Control Attribute CurrentLevel 1 to 254
141
+ * - Level Control Attribute MinLevel 1
142
+ * - Level Control Attribute MaxLevel 254
143
+ */
144
+ export declare const onOffLight: DeviceTypeDefinition;
145
+ /**
146
+ * Element Requirements:
147
+ * - Identify Command TriggerEffect
148
+ * - Scenes Management Command CopyScene
149
+ * - On/Off Feature Lighting
150
+ * - Level Control Feature OnOff
151
+ * - Level Control Feature Lighting
152
+ * - Level Control Attribute CurrentLevel 1 to 254
153
+ * - Level Control Attribute MinLevel 1
154
+ * - Level Control Attribute MaxLevel 254
155
+ */
156
+ export declare const dimmableLight: DeviceTypeDefinition;
157
+ /**
158
+ * Element Requirements:
159
+ * - Identify Command TriggerEffect
160
+ * - Scenes Management Command CopyScene
161
+ * - On/Off Feature Lighting
162
+ * - Level Control Feature OnOff
163
+ * - Level Control Feature Lighting
164
+ * - Level Control Attribute CurrentLevel 1 to 254
165
+ * - Level Control Attribute MinLevel 1
166
+ * - Level Control Attribute MaxLevel 254
167
+ * - Color Control Feature ColorTemperature
168
+ * - Color Control Attribute RemainingTime
169
+ */
170
+ export declare const colorTemperatureLight: DeviceTypeDefinition;
171
+ /**
172
+ * Element Requirements:
173
+ * - Identify Command TriggerEffect
174
+ * - Scenes Management Command CopyScene
175
+ * - On/Off Feature Lighting
176
+ * - Level Control Feature OnOff
177
+ * - Level Control Feature Lighting
178
+ * - Level Control Attribute CurrentLevel 1 to 254
179
+ * - Level Control Attribute MinLevel 1
180
+ * - Level Control Attribute MaxLevel 254
181
+ * - Color Control Feature XY
182
+ * - Color Control Feature ColorTemperature
183
+ * - Color Control Attribute RemainingTime
184
+ */
185
+ export declare const extendedColorLight: DeviceTypeDefinition;
186
+ /**
187
+ * Element Requirements:
188
+ * - Identify Command TriggerEffect
189
+ * - Scenes Management Command CopyScene
190
+ * - On/Off Feature Lighting
191
+ * - Level Control Feature OnOff
192
+ * - Level Control Feature Lighting
193
+ * - Level Control Attribute CurrentLevel 1 to 254
194
+ * - Level Control Attribute MinLevel 1
195
+ * - Level Control Attribute MaxLevel 254
196
+ */
197
+ export declare const onOffOutlet: DeviceTypeDefinition;
198
+ /**
199
+ * Element Requirements:
200
+ * - Identify Command TriggerEffect
201
+ * - Scenes Management Command CopyScene
202
+ * - On/Off Feature Lighting
203
+ * - Level Control Feature OnOff
204
+ * - Level Control Feature Lighting
205
+ * - Level Control Attribute CurrentLevel 1 to 254
206
+ * - Level Control Attribute MinLevel 1
207
+ * - Level Control Attribute MaxLevel 254
208
+ */
209
+ export declare const dimmableOutlet: DeviceTypeDefinition;
210
+ /**
211
+ * A Mounted On/Off Control is a fixed device that provides power to another device that is plugged
212
+ * into it, and is capable of switching that provided power on or off.
213
+ * It is a simple device type that does not require any client clusters.
214
+ * Element Requirements:
215
+ * - Identify Command TriggerEffect
216
+ * - Scenes Management Command CopyScene
217
+ * - On/Off Feature Lighting
218
+ * - Level Control Feature OnOff
219
+ * - Level Control Feature Lighting
220
+ * - Level Control Attribute CurrentLevel 1 to 254
221
+ * - Level Control Attribute MinLevel 1
222
+ * - Level Control Attribute MaxLevel 254
223
+ */
224
+ export declare const onOffMountedSwitch: DeviceTypeDefinition;
225
+ /**
226
+ * A Mounted Dimmable Load Control is a fixed device that provides power to another device that is
227
+ * plugged into it, and is capable of being switched on or off and have its level adjusted. The Mounted
228
+ * Dimmable Load Control is typically used to control a conventional non-communicating light
229
+ * through its mains connection using phase cutting.
230
+ * It is a simple device type that does not require any client clusters.
231
+ * Element Requirements:
232
+ * - Identify Command TriggerEffect
233
+ * - Scenes Management Command CopyScene
234
+ * - On/Off Feature Lighting
235
+ * - Level Control Feature OnOff
236
+ * - Level Control Feature Lighting
237
+ * - Level Control Attribute CurrentLevel 1 to 254
238
+ * - Level Control Attribute MinLevel 1
239
+ * - Level Control Attribute MaxLevel 254
240
+ */
241
+ export declare const dimmableMountedSwitch: DeviceTypeDefinition;
242
+ /**
243
+ * Remark:
244
+ * On/Off Cluster:
245
+ * - Off If the pump is powered on, store the current level then immediately power it off.
246
+ * - On If the pump is powered off, power it on and move immediately to the level stored by a previous Off command. If no such level has been stored,
247
+ * move immediately to the maximum level allowed for the pump.
248
+ * - Toggle If the pump is powered on, proceed as for the Off command. If the device is powered off, proceed as for the On command.
249
+ *
250
+ * LevelControl cluster:
251
+ * Level Setpoint Meaning
252
+ * 0 N/A Pump is stopped,
253
+ * 1–200 Level / 2 (0.5–100.0%) Pump setpoint in percent
254
+ * 201–255 100.0% Pump setpoint is 100.0%
255
+ */
256
+ export declare const pumpDevice: DeviceTypeDefinition;
257
+ export declare const waterValve: DeviceTypeDefinition;
258
+ export declare const onOffSwitch: DeviceTypeDefinition;
259
+ export declare const dimmableSwitch: DeviceTypeDefinition;
260
+ export declare const colorTemperatureSwitch: DeviceTypeDefinition;
261
+ export declare const genericSwitch: DeviceTypeDefinition;
262
+ /**
263
+ * Closed or contact: state true
264
+ * Open or no contact: state false
265
+ */
266
+ export declare const contactSensor: DeviceTypeDefinition;
267
+ export declare const lightSensor: DeviceTypeDefinition;
268
+ export declare const occupancySensor: DeviceTypeDefinition;
269
+ export declare const temperatureSensor: DeviceTypeDefinition;
270
+ export declare const pressureSensor: DeviceTypeDefinition;
271
+ export declare const flowSensor: DeviceTypeDefinition;
272
+ export declare const humiditySensor: DeviceTypeDefinition;
273
+ export declare const smokeCoAlarm: DeviceTypeDefinition;
274
+ export declare const airQualitySensor: DeviceTypeDefinition;
275
+ export declare const waterFreezeDetector: DeviceTypeDefinition;
276
+ export declare const waterLeakDetector: DeviceTypeDefinition;
277
+ export declare const rainSensor: DeviceTypeDefinition;
278
+ /**
279
+ * A Door Lock is a device used to secure a door. It is possible to actuate a door lock either by means of a manual or a remote method.
280
+ * Element Requirements:
281
+ *
282
+ * - AccessControl Attribute Extension
283
+ * - DoorLock Feature User
284
+ * - DoorLock Attribute AlarmMask
285
+ */
286
+ export declare const doorLockDevice: DeviceTypeDefinition;
287
+ export declare const coverDevice: DeviceTypeDefinition;
288
+ /**
289
+ * A Thermostat device is capable of having either built-in or separate sensors for temperature,
290
+ * humidity or occupancy. It allows the desired temperature to be set either remotely or locally. The
291
+ * thermostat is capable of sending heating and/or cooling requirement notifications to a heating/cooling
292
+ * unit (for example, an indoor air handler) or is capable of including a mechanism to control a
293
+ * heating or cooling unit directly.
294
+ *
295
+ */
296
+ export declare const thermostatDevice: DeviceTypeDefinition;
297
+ /**
298
+ * A Fan device is typically standalone or mounted on a ceiling or wall and is used to circulate air in a room.
299
+ * Remark: it may have a thermostat device type.
300
+ * Additional device types MAY also be included in device compositions.
301
+ * Element Requirements:
302
+ * The FanControl cluster must have the FanModeSequence attribute.
303
+ *
304
+ * The On/Off cluster is independent from the Fan Control Cluster’s FanMode attribute, which also
305
+ * includes an Off setting.
306
+ * If the FanMode attribute of the Fan Control cluster is set to a value other than Off when the OnOff
307
+ * attribute of the On/Off cluster transitions from TRUE to FALSE, it may be desirable to restore the
308
+ * FanMode, SpeedSetting and PercentSetting attribute values of the Fan Control cluster when the OnOff
309
+ * attribute of the On/Off cluster later transitions from FALSE to TRUE. If the FanMode is set to Off when
310
+ * the device is turned off, this information is lost, as the SpeedSetting and PercentSetting will be set to
311
+ * zero. Using the On/Off cluster alongside the Fan Control cluster allows the FanMode, SpeedSetting and
312
+ * PercentSetting to remain unchanged when the device is turned off. In this case, the On/Off cluster
313
+ * would be set to Off, and the SpeedCurrent and PercentCurrent set to zero, without changing FanMode,
314
+ * SpeedSetting and PercentSetting.
315
+ */
316
+ export declare const fanDevice: DeviceTypeDefinition;
317
+ /**
318
+ * An Air Purifier is a standalone device that is designed to clean the air in a room.
319
+ * It is a device that has a fan to control the air speed while it is operating. Optionally, it can report on
320
+ * the condition of its filters.
321
+ *
322
+ * Remark:
323
+ * An Air Purifier MAY expose elements of its functionality through one or more additional device
324
+ * types on different endpoints. All devices used in compositions SHALL adhere to the disambiguation
325
+ * requirements of the System Model. Other device types, not explicitly listed in the table, MAY also be
326
+ * included in device compositions but are not considered part of the core functionality of the device.
327
+ * 0x0301 Thermostat O
328
+ * 0x0302 Temperature Sensor O
329
+ * 0x0307 Humidity Sensor O
330
+ * 0x002C Air Quality Sensor O
331
+ *
332
+ * Cluster Restrictions:
333
+ * The On/Off cluster is independent from the Fan Control Cluster’s FanMode attribute, which also
334
+ * includes an Off setting.
335
+ * If the FanMode attribute of the Fan Control cluster is set to a value other than Off when the OnOff
336
+ * attribute of the On/Off cluster transitions from TRUE to FALSE, it may be desirable to restore the
337
+ * FanMode, SpeedSetting and PercentSetting attribute values of the Fan Control cluster when the OnOff
338
+ * attribute of the On/Off cluster later transitions from FALSE to TRUE. If the FanMode is set to Off when
339
+ * the device is turned off, this information is lost, as the SpeedSetting and PercentSetting will be set to
340
+ * zero. Using the On/Off cluster alongside the Fan Control cluster allows the FanMode, SpeedSetting and
341
+ * PercentSetting to remain unchanged when the device is turned off. In this case, the On/Off cluster
342
+ * would be set to Off, and the SpeedCurrent and PercentCurrent set to zero, without changing FanMode,
343
+ * SpeedSetting and PercentSetting.
344
+ *
345
+ */
346
+ export declare const airPurifier: DeviceTypeDefinition;
347
+ export declare const modeSelect: DeviceTypeDefinition;
348
+ /**
349
+ * This device type aggregates endpoints as a collection. Clusters on the endpoint indicating this
350
+ * device type provide functionality for the collection of descendant endpoints present in the PartsList
351
+ * of the endpoint’s descriptor, for example the Actions cluster.
352
+ *
353
+ * Endpoint Composition:
354
+ * An Aggregator endpoint’s Descriptor cluster PartsList attribute SHALL list the collection of all endpoints
355
+ * aggregated by the Aggregator device type, i.e. the full-family pattern defined in the System Model specification.
356
+ *
357
+ * Disambiguation:
358
+ * If the Duplicate condition applies to child endpoints of an Aggregator endpoint that represent multiple
359
+ * independent bridged devices, the endpoints SHOULD make available metadata to allow a
360
+ * client to disambiguate distinct bridged devices with an overlap in application device types.
361
+ *
362
+ * Typically this is done using the NodeLabel attribute of the Bridged Device Basic Information cluster
363
+ * - thus reusing the naming information which the bridge already has to allow disambiguation to the
364
+ * user when using a direct user interface to the bridge.
365
+ *
366
+ * Actions cluster (9.14 Matter specification):
367
+ * If a Bridge has (such) information on topology or logical grouping, it SHOULD expose such information
368
+ * in the EndpointLists attribute of an Actions cluster (the ActionLists of which MAY be empty if
369
+ * no actions are exposed). 9.12 Matter specification
370
+ *
371
+ * 9.12.5. New features for Bridged Devices
372
+ * Bridged Devices can have their software updated independently of the Bridge, through Bridge Manufacturer-
373
+ * specific means. These updates MAY result in one or more changes to their capabilities,
374
+ * such as supported clusters and/or attributes, for an endpoint. Like every Matter Node, every endpoint
375
+ * on the Bridge’s Node contains a Descriptor cluster that contains attributes for the device types
376
+ * (DeviceTypeList), endpoints (PartsList) and supported clusters (ServerList and ClientList). Nodes
377
+ * that wish to be notified of such changes SHOULD monitor changes of these attributes.
378
+ */
379
+ export declare const aggregator: DeviceTypeDefinition;
380
+ export declare const bridge: DeviceTypeDefinition;
381
+ /**
382
+ * A Robotic Vacuum Cleaner is a device that is capable of cleaning floors and other surfaces
383
+ * in a home or office environment. It is typically a mobile device that can navigate around
384
+ * obstacles and can be controlled remotely.
385
+ *
386
+ * Cluster Usage:
387
+ * The RVC Operational State cluster’s OperationalState attribute SHALL be updated according to the
388
+ * state of the device, and therefore it SHOULD be used for monitoring purposes.
389
+ *
390
+ * To attempt starting a cleaning operation, the RVC Run Mode cluster can be sent a ChangeToMode
391
+ * command with the NewMode field set to a mode that has the Cleaning mode tag associated with it.
392
+ *
393
+ * To attempt stopping a cleaning operation, the RVC Run Mode cluster can be sent a ChangeToMode
394
+ * command with the NewMode field set to a mode that has the Idle mode tag associated with it.
395
+ *
396
+ * To attempt pausing a cleaning operation, the RVC Operational State cluster can be sent a Pause command.
397
+ *
398
+ * To attempt resuming a cleaning operation, the RVC Operational State cluster can be sent a Resume
399
+ * command.
400
+ *
401
+ *
402
+ */
403
+ export declare const roboticVacuumCleaner: DeviceTypeDefinition;
404
+ /**
405
+ * Cluster Restrictions:
406
+ * On/Off Cluster: the DF (Dead Front) feature is required
407
+ */
408
+ export declare const laundryWasher: DeviceTypeDefinition;
409
+ /**
410
+ * A refrigerator represents a device that contains one or more cabinets that are capable of chilling or freezing food.
411
+ * A Refrigerator SHALL be composed of at least one endpoint with the Temperature Controlled Cabinet device type.
412
+ *
413
+ * Device Type Requirements:
414
+ * 0x0071 Temperature Controlled Cabinet
415
+ */
416
+ export declare const refrigerator: DeviceTypeDefinition;
417
+ /**
418
+ * A Room Air Conditioner is a device with the primary function of controlling the air temperature in a single room.
419
+ *
420
+ * A Room Air Conditioner MAY have zero or more of each device type listed in this table subject to
421
+ * the conformance column of the table. All devices used in compositions SHALL adhere to the disambiguation
422
+ * requirements of the System Model. Additional device types not listed in this table MAY also be included in device compositions.
423
+ * 0x0302 Temperature Sensor O
424
+ * 0x0307 Humidity Sensor O
425
+ *
426
+ * Remark:
427
+ * The DF (Dead Front) feature is required for the On/Off cluster in this device type:
428
+ * - Thermostat LocalTemperature null
429
+ * - Temperature Measurement MeasuredValue null
430
+ * - Relative Humidity Measurement MeasuredValue null
431
+ * - Fan Control SpeedSetting null
432
+ * - Fan Control PercentSetting null
433
+ */
434
+ export declare const airConditioner: DeviceTypeDefinition;
435
+ /**
436
+ * A Temperature Controlled Cabinet only exists composed as part of another device type. It represents
437
+ * a single cabinet that is capable of having its temperature controlled. Such a cabinet may be
438
+ * chilling or freezing food, for example as part of a refrigerator, freezer, wine chiller, or other similar
439
+ * device. Equally, such a cabinet may be warming or heating food, for example as part of an oven,
440
+ * range, or similar device.
441
+ * Conditions:
442
+ * Cooler The device has cooling functionality.
443
+ */
444
+ export declare const temperatureControlledCabinetCooler: DeviceTypeDefinition;
445
+ /**
446
+ * A Temperature Controlled Cabinet only exists composed as part of another device type. It represents
447
+ * a single cabinet that is capable of having its temperature controlled. Such a cabinet may be
448
+ * chilling or freezing food, for example as part of a refrigerator, freezer, wine chiller, or other similar
449
+ * device. Equally, such a cabinet may be warming or heating food, for example as part of an oven,
450
+ * range, or similar device.
451
+ * Conditions:
452
+ * Heater The device has heating functionality.
453
+ */
454
+ export declare const temperatureControlledCabinetHeater: DeviceTypeDefinition;
455
+ /**
456
+ * Cluster Restrictions:
457
+ * On/Off Cluster: the DF (Dead Front) feature is required
458
+ */
459
+ export declare const dishwasher: DeviceTypeDefinition;
460
+ /**
461
+ * Cluster Restrictions:
462
+ * On/Off Cluster: the DF (Dead Front) feature is required
463
+ */
464
+ export declare const laundryDryer: DeviceTypeDefinition;
465
+ /**
466
+ * A Cook Surface device type represents a heating object on a cooktop or other similar device. It
467
+ * SHALL only be used when composed as part of another device type (cooktop).
468
+ *
469
+ * Cluster Restrictions:
470
+ * The OffOnly feature is required for the On/Off cluster in this device type due to safety requirements.
471
+ */
472
+ export declare const cookSurface: DeviceTypeDefinition;
473
+ /**
474
+ * A cooktop is a cooking surface that heats food either by transferring currents from an electromagnetic
475
+ * field located below the glass surface directly to the magnetic induction cookware placed
476
+ * above or through traditional gas or electric burners.
477
+ *
478
+ * Device Type Requirements:
479
+ * A Cooktop SHALL be composed of zero or more endpoints with the Cook Surface device type as defined by the conformance below.
480
+ * 0x0077 Cook Surface min 1 O
481
+ *
482
+ * Cluster Restrictions:
483
+ * The OffOnly feature is required for the On/Off cluster in this device type due to safety requirements.
484
+ */
485
+ export declare const cooktop: DeviceTypeDefinition;
486
+ /**
487
+ * An oven represents a device that contains one or more cabinets, and optionally a single cooktop, that are all capable of heating food.
488
+ * An oven is always defined via endpoint composition.
489
+ * Conditions:
490
+ * An Oven SHALL have the Heater condition applied to at least one endpoint containing the Temperature Control Cluster.
491
+ * Device Type Requirements:
492
+ * 0x0071 Temperature Controlled Cabinet min 1
493
+ * 0x0078 Cooktop
494
+ */
495
+ export declare const oven: DeviceTypeDefinition;
496
+ /**
497
+ * An Extractor Hood is a device that is generally installed above a cooking surface in residential kitchens.
498
+ * Additional device types not listed in this table MAY also be included in device compositions.
499
+ * Device Type Requirements:
500
+ * 0x0100+ On/Off Light+ O
501
+ *
502
+ *
503
+ * Element Requirements:
504
+ * 0x0202 Fan Control Feature Rocking X
505
+ * 0x0202 Fan Control Feature Wind X
506
+ * 0x0202 Fan Control Feature AirflowDirection X
507
+ */
508
+ export declare const extractorHood: DeviceTypeDefinition;
509
+ /**
510
+ * A Microwave Oven is a device with the primary function of heating foods and beverages using a magnetron.
511
+ * A Microwave Oven is a device which at a minimum is capable of being started and stopped and of setting a power level.
512
+ * A Microwave Oven MAY also support additional capabilities via endpoint composition.
513
+ *
514
+ */
515
+ export declare const microwaveOven: DeviceTypeDefinition;
516
+ /**
517
+ * An EVSE (Electric Vehicle Supply Equipment) is a device that allows an EV (Electric Vehicle) to be
518
+ * connected to the mains electricity supply to allow it to be charged (or discharged in case of Vehicle
519
+ * to Grid / Vehicle to Home applications).
520
+ *
521
+ * 14.1.5. Device Type Requirements
522
+ * An EVSE SHALL be composed of at least one endpoint with device types as defined by the conformance
523
+ * below. There MAY be more endpoints with other device types existing in the EVSE.
524
+ * ID Name Constraint Conformance
525
+ * 0x0011 Power Source min 1 M
526
+ * 0x0510 Electrical Sensor min 1 M
527
+ * 0x050D Device Energy Management min 1 M
528
+ *
529
+ * The Electrical Sensor device SHALL include both the Electrical Energy Measurement and Electrical
530
+ * Power Measurement clusters, measuring the total energy and power of the EVSE.
531
+ *
532
+ * The Device Energy Management cluster included in the Device Energy Management device SHALL
533
+ * support the Power Forecast Reporting (PFR) feature.
534
+ */
535
+ export declare const evse: DeviceTypeDefinition;
536
+ /**
537
+ * A water heater is a device that is generally installed in properties to heat water for showers, baths etc.
538
+ * A Water Heater is always defined via endpoint composition.
539
+ *
540
+ * 14.2.5. Device Type Requirements
541
+ * A Water Heater SHALL be composed of at least one endpoint with device types as defined by the
542
+ * conformance below. There MAY be more endpoints with other device types existing in the Water Heater.
543
+ * ID Name Constraint Conformance
544
+ * 0x0011 Power Source O
545
+ * 0x0302 Temperature Sensor O
546
+ * 0x0510 Electrical Sensor desc
547
+ * 0x050D Device Energy Management O
548
+ *
549
+ * 14.2.7. Element Requirements
550
+ * 0x0201 Thermostat Feature Heating M
551
+ *
552
+ * The Energy Management feature of the Water Heater cluster SHALL be supported if the Device
553
+ * Energy Management device type is included.
554
+ * If Off is a supported SystemMode in the Thermostat cluster, setting the SystemMode of the Thermostat
555
+ * cluster to Off SHALL set the CurrentMode attribute of the Water Heater Mode cluster to a mode
556
+ * having the Off mode tag value and vice versa.
557
+ * At least one entry in the SupportedModes attribute of the Water Heater Mode cluster SHALL
558
+ * include the Timed mode tag in the ModeTags field list.
559
+ *
560
+ * WaterHeaterMode Cluster
561
+ * 9.6.6.1. SupportedModes Attribute
562
+ * At least one entry in the SupportedModes attribute SHALL include the Manual mode tag in the
563
+ * ModeTags field list.
564
+ * At least one entry in the SupportedModes attribute SHALL include the Off mode tag in the ModeTags
565
+ * field list.
566
+ * An entry in the SupportedModes attribute that includes one of an Off, Manual, or Timed tag SHALL
567
+ * NOT also include an additional instance of any one of these tag types.
568
+ */
569
+ export declare const waterHeater: DeviceTypeDefinition;
570
+ /**
571
+ * A Solar Power device is a device that allows a solar panel array, which can optionally be comprised
572
+ * of a set parallel strings of solar panels, and its associated controller and, if appropriate, inverter, to
573
+ * be monitored and controlled by an Energy Management System.
574
+ *
575
+ * 14.3.5. Device Type Requirements
576
+ * A Solar Power device SHALL be composed of at least one endpoint with device types as defined by
577
+ * the conformance below. There MAY be more endpoints with additional instances of these device
578
+ * types or additional device types existing in the Solar Power device.
579
+ *
580
+ * ID Name Constraint Conformance
581
+ * 0x0011 Power Source min 1 M
582
+ * 0x0510 Electrical Sensor min 1 M
583
+ * 0x050D Device Energy Management O
584
+ * 0x0302 Temperature Sensor O
585
+ *
586
+ * 14.3.5.1. Cluster Requirements on Composing Device Types
587
+ *
588
+ * 0x0011 Power Source 0x002F Power Source Feature Wired M
589
+ * 0x0011 Power Source 0x001D Descriptor Feature TagList M
590
+ * 0x0510 Electrical Sensor 0x0090 Electrical Power Measurement M
591
+ * 0x0510 Electrical Sensor 0x0090 Electrical Power Measurement Attribute Voltage M
592
+ * 0x0510 Electrical Sensor 0x0090 Electrical Power Measurement Attribute ActiveCurrent M
593
+ * 0x0510 Electrical Sensor 0x0091 Electrical Energy Measurement M
594
+ * 0x0510 Electrical Sensor 0x0091 Electrical Energy Measurement Feature ExportedEnergy M
595
+ * 0x050D Device Energy Management 0x0098 Device Energy Management Feature PowerAdjustment M
596
+ * 0x0302 Temperature Sensor 0x001D Descriptor Feature TagList M
597
+ */
598
+ export declare const solarPower: DeviceTypeDefinition;
599
+ /**
600
+ * A Battery Storage device is a device that allows a DC battery, which can optionally be comprised of
601
+ * a set parallel strings of battery packs and associated controller, and an AC inverter, to be monitored
602
+ * and controlled by an Energy Management System in order to manage the peaks and troughs of supply
603
+ * and demand, and/or to optimize cost of the energy consumed in premises. It is not intended to
604
+ * be used for a UPS directly supplying a set of appliances, nor for portable battery storage devices.
605
+ *
606
+ * 14.4.5. Device Type Requirements
607
+ * A Battery Storage device SHALL be composed of at least one endpoint with device types as defined by
608
+ * the conformance below. There MAY be more endpoints with additional instances of these device
609
+ * types or additional device types existing in the Battery Storage device.
610
+ * ID Name Constraint Conformance
611
+ * 0x0011 Power Source min 1 M
612
+ * 0x0510 Electrical Sensor min 1 M
613
+ * 0x050D Device Energy Management M
614
+ * 0x0302 Temperature Sensor O
615
+ * 0x0017 Solar Power O
616
+ *
617
+ * See 14.4.5.1. Cluster Requirements on Composing Device Types
618
+ */
619
+ export declare const batteryStorage: DeviceTypeDefinition;
620
+ /**
621
+ * A Heat Pump device is a device that uses electrical energy to heat either spaces or water tanks using
622
+ * ground, water or air as the heat source. These typically can heat the air or can pump water via central
623
+ * heating radiators or underfloor heating systems. It is typical to also heat hot water and store
624
+ * the heat in a hot water tank.
625
+ *
626
+ * 14.5.1. Heat Pump Architecture
627
+ * A Heat Pump device is always defined via endpoint composition.
628
+ *
629
+ * 14.5.5. Device Type Requirements
630
+ * A Heat Pump device SHALL be composed of at least one endpoint with device types as defined by
631
+ * the conformance below. There MAY be more endpoints with additional instances of these device
632
+ * types or additional device types existing in the Heat Pump device.
633
+ * ID Name Constraint Conformance
634
+ * 0x0011 Power Source M
635
+ * 0x0510 Electrical Sensor min 1 M
636
+ * 0x050D Device Energy Management M
637
+ * 0x0301 Thermostat O
638
+ * 0x050f Water Heater O
639
+ * 0x0302 Temperature Sensor O
640
+ *
641
+ * See 14.5.5.1. Cluster Requirements on Composing Device Types
642
+ */
643
+ export declare const heatPump: DeviceTypeDefinition;
644
+ //# sourceMappingURL=matterbridgeDeviceTypes.d.ts.map
@@ -0,0 +1 @@
1
+ {"version":3,"file":"matterbridgeDeviceTypes.d.ts","sourceRoot":"","sources":["../src/matterbridgeDeviceTypes.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;GAqBG;AAGH,OAAO,EAAE,SAAS,EAAE,YAAY,EAAE,cAAc,EAAE,MAAM,cAAc,CAAC;AACvE,OAAO,EAAE,MAAM,EAAE,MAAM,oBAAoB,CAAC;AAuE5C,oBAAY,aAAa;IACvB,wBAAwB;IACxB,IAAI,SAAS;IAEb;;;OAGG;IACH,GAAG,QAAQ;IAEX;;;OAGG;IACH,OAAO,YAAY;IAEnB;;;OAGG;IACH,MAAM,WAAW;IAEjB;;;;;OAKG;IACH,OAAO,YAAY;IAEnB,iEAAiE;IACjE,MAAM,WAAW;IAEjB,iEAAiE;IACjE,MAAM,WAAW;IAEjB,6DAA6D;IAC7D,QAAQ,aAAa;IAErB,4GAA4G;IAC5G,SAAS,cAAc;IAEvB;;;OAGG;IACH,sBAAsB,2BAA2B;CAClD;AAED,MAAM,WAAW,oBAAoB;IACnC,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,YAAY,CAAC;IACnB,WAAW,EAAE,aAAa,CAAC;IAC3B,QAAQ,EAAE,MAAM,CAAC;IACjB,sBAAsB,EAAE,SAAS,EAAE,CAAC;IACpC,sBAAsB,EAAE,SAAS,EAAE,CAAC;IACpC,sBAAsB,EAAE,SAAS,EAAE,CAAC;IACpC,sBAAsB,EAAE,SAAS,EAAE,CAAC;CACrC;AAED,eAAO,MAAM,oBAAoB,GAAI,wIASlC;IACD,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,aAAa,CAAC;IAC3B,QAAQ,EAAE,MAAM,CAAC;IACjB,sBAAsB,CAAC,EAAE,SAAS,EAAE,CAAC;IACrC,sBAAsB,CAAC,EAAE,SAAS,EAAE,CAAC;IACrC,sBAAsB,CAAC,EAAE,SAAS,EAAE,CAAC;IACrC,sBAAsB,CAAC,EAAE,SAAS,EAAE,CAAC;CACtC,KAAG,oBASF,CAAC;AAEH,MAAM,WAAW,2BAA4B,SAAQ,eAAe;IAClE,OAAO,CAAC,EAAE,MAAM,EAAE,CAAC;CACpB;AAED,MAAM,WAAW,eAAe;IAC9B,UAAU,CAAC,EAAE,cAAc,CAAC;IAC5B,gBAAgB,CAAC,EAAE,MAAM,CAAC;CAC3B;AAID,eAAO,MAAM,WAAW,sBAOtB,CAAC;AAEH,eAAO,MAAM,YAAY,sBASvB,CAAC;AAEH,eAAO,MAAM,WAAW,sBAStB,CAAC;AAEH;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,eAAO,MAAM,WAAW,sBAOtB,CAAC;AAEH;;;;;;;;;;GAUG;AACH,eAAO,MAAM,gBAAgB,sBAO3B,CAAC;AAEH;;;GAGG;AACH,eAAO,MAAM,sBAAsB,sBAOjC,CAAC;AAIH;;;;;;;;;;GAUG;AACH,eAAO,MAAM,UAAU,sBAOrB,CAAC;AAEH;;;;;;;;;;GAUG;AACH,eAAO,MAAM,aAAa,sBAOxB,CAAC;AAEH;;;;;;;;;;;;GAYG;AACH,eAAO,MAAM,qBAAqB,sBAOhC,CAAC;AAEH;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,kBAAkB,sBAO7B,CAAC;AAIH;;;;;;;;;;GAUG;AACH,eAAO,MAAM,WAAW,sBAOtB,CAAC;AAEH;;;;;;;;;;GAUG;AACH,eAAO,MAAM,cAAc,sBAOzB,CAAC;AAEH;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,kBAAkB,sBAO7B,CAAC;AAEH;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,qBAAqB,sBAOhC,CAAC;AAEH;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,UAAU,sBAOrB,CAAC;AAEH,eAAO,MAAM,UAAU,sBAOrB,CAAC;AAKH,eAAO,MAAM,WAAW,sBAOtB,CAAC;AAGH,eAAO,MAAM,cAAc,sBAOzB,CAAC;AAGH,eAAO,MAAM,sBAAsB,sBAOjC,CAAC;AAEH,eAAO,MAAM,aAAa,sBAOxB,CAAC;AAIH;;;GAGG;AACH,eAAO,MAAM,aAAa,sBAOxB,CAAC;AAEH,eAAO,MAAM,WAAW,sBAMtB,CAAC;AAEH,eAAO,MAAM,eAAe,sBAO1B,CAAC;AAEH,eAAO,MAAM,iBAAiB,sBAM5B,CAAC;AAEH,eAAO,MAAM,cAAc,sBAMzB,CAAC;AAEH,eAAO,MAAM,UAAU,sBAMrB,CAAC;AAEH,eAAO,MAAM,cAAc,sBAMzB,CAAC;AAGH,eAAO,MAAM,YAAY,sBAOvB,CAAC;AAEH,eAAO,MAAM,gBAAgB,sBAoB3B,CAAC;AAEH,eAAO,MAAM,mBAAmB,sBAO9B,CAAC;AAEH,eAAO,MAAM,iBAAiB,sBAO5B,CAAC;AAEH,eAAO,MAAM,UAAU,sBAOrB,CAAC;AAGH;;;;;;;GAOG;AACH,eAAO,MAAM,cAAc,sBAOzB,CAAC;AAEH,eAAO,MAAM,WAAW,sBAOtB,CAAC;AAIH;;;;;;;GAOG;AACH,eAAO,MAAM,gBAAgB,sBAO3B,CAAC;AAEH;;;;;;;;;;;;;;;;;;GAkBG;AACH,eAAO,MAAM,SAAS,sBAOpB,CAAC;AAEH;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACH,eAAO,MAAM,WAAW,sBAOtB,CAAC;AAIH,eAAO,MAAM,UAAU,sBAMrB,CAAC;AAEH;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8BG;AACH,eAAO,MAAM,UAAU,sBAOrB,CAAC;AAEH,eAAO,MAAM,MAAM,sBAAa,CAAC;AAIjC;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,eAAO,MAAM,oBAAoB,sBAO/B,CAAC;AAIH;;;GAGG;AACH,eAAO,MAAM,aAAa,sBAOxB,CAAC;AAEH;;;;;;GAMG;AACH,eAAO,MAAM,YAAY,sBAOvB,CAAC;AAEH;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,cAAc,sBAczB,CAAC;AAEH;;;;;;;;GAQG;AACH,eAAO,MAAM,kCAAkC,sBAO7C,CAAC;AAEH;;;;;;;;GAQG;AACH,eAAO,MAAM,kCAAkC,sBAO7C,CAAC;AAEH;;;GAGG;AACH,eAAO,MAAM,UAAU,sBAOrB,CAAC;AAEH;;;GAGG;AACH,eAAO,MAAM,YAAY,sBAOvB,CAAC;AAEH;;;;;;GAMG;AACH,eAAO,MAAM,WAAW,sBAOtB,CAAC;AAEH;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,OAAO,sBAOlB,CAAC;AAEH;;;;;;;;GAQG;AACH,eAAO,MAAM,IAAI,sBAOf,CAAC;AAEH;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,aAAa,sBAOxB,CAAC;AAEH;;;;;GAKG;AACH,eAAO,MAAM,aAAa,sBAOxB,CAAC;AAIH;;;;;;;;;;;;;;;;;;GAkBG;AACH,eAAO,MAAM,IAAI,sBAOf,CAAC;AAEH;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAgCG;AACH,eAAO,MAAM,WAAW,sBAOtB,CAAC;AAEH;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,eAAO,MAAM,UAAU,sBAOrB,CAAC;AAEH;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,cAAc,sBAOzB,CAAC;AAEH;;;;;;;;;;;;;;;;;;;;;;GAsBG;AACH,eAAO,MAAM,QAAQ,sBAOnB,CAAC"}