@zwave-js/config 11.10.0 → 11.10.1
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.
|
@@ -332,10 +332,40 @@
|
|
|
332
332
|
}
|
|
333
333
|
],
|
|
334
334
|
"compat": {
|
|
335
|
-
//
|
|
336
|
-
|
|
337
|
-
//
|
|
338
|
-
//
|
|
339
|
-
|
|
335
|
+
// https://github.com/zwave-js/node-zwave-js/issues/6017#issuecomment-1648532422
|
|
336
|
+
|
|
337
|
+
// The device has a weird endpoint setup. Most thermostat functionality is on endpoint 0, but the two additional
|
|
338
|
+
// endpoints have a thermostat device class:
|
|
339
|
+
// General Thermostat V2
|
|
340
|
+
// - "Manufacturer Specific"
|
|
341
|
+
// - "Thermostat Mode"
|
|
342
|
+
// - "Thermostat Setpoint"
|
|
343
|
+
// - "Version"
|
|
344
|
+
// plus the non-mandatory CCs
|
|
345
|
+
// - "Multilevel Sensor"
|
|
346
|
+
// - "Association"
|
|
347
|
+
|
|
348
|
+
// The additional endpoints simply mirror the root endpoint though, except the humidity sensor on endpoint 2.
|
|
349
|
+
|
|
350
|
+
// expose the application CCs on the root endpoint
|
|
351
|
+
"preserveRootApplicationCCValueIDs": true,
|
|
352
|
+
|
|
353
|
+
// Remove all Thermostat CCs from endpoints 1 and 2, as well as the sensor on endpoint 1
|
|
354
|
+
"commandClasses": {
|
|
355
|
+
"remove": {
|
|
356
|
+
"Basic": {
|
|
357
|
+
"endpoints": [1, 2]
|
|
358
|
+
},
|
|
359
|
+
"Thermostat Mode": {
|
|
360
|
+
"endpoints": [1, 2]
|
|
361
|
+
},
|
|
362
|
+
"Thermostat Setpoint": {
|
|
363
|
+
"endpoints": [1, 2]
|
|
364
|
+
},
|
|
365
|
+
"Multilevel Sensor": {
|
|
366
|
+
"endpoints": [1]
|
|
367
|
+
}
|
|
368
|
+
}
|
|
369
|
+
}
|
|
340
370
|
}
|
|
341
371
|
}
|