mclimate:16a-dry-switch:1 | updated | back to the 4.0.0 driver; the manufacturer driver moves to mclimate:16a-dry-switch:2 — index.js is the driver-catalog-4.0.0 one again, so devices provisioned on mclimate:16a-dry-switch:1 keep the payload and downlink bytes they had in 4.0.0; the 5.0.0 changes (the uplink relayState is a boolean (true/false) instead of "ON"/"OFF", and the relay state change reason (0x54) and relay timer (0x56) responses are decoded) are only in mclimate:16a-dry-switch:2. The examples are the 4.0.0 behaviour (examples the 4.0.0 code cannot run are dropped) and the BACnet mapping moves to mclimate:16a-dry-switch:2, the BACnet owner of the model. Package 1.1.2. |
mclimate:16a-dry-switch:2 | added | MClimate manufacturer driver as a v2: 16a-dry-switch changes its payload — The manufacturer's driver shipped as mclimate:16a-dry-switch:1 in 5.0.0 is not backward compatible with 4.0.0: the uplink relayState is a boolean (true/false) instead of "ON"/"OFF", and the relay state change reason (0x54) and relay timer (0x56) responses are decoded. It becomes mclimate:16a-dry-switch:2 (package 2.0.0), with the private extractPoints and the BACnet mapping, and is the default driver of new 16a-dry-switch devices. Devices provisioned on mclimate:16a-dry-switch:1 keep the 4.0.0 behaviour. |
mclimate:co2-display-lite:1 | updated | back to the 4.0.0 driver; the manufacturer driver moves to mclimate:co2-display-lite:2 — index.js is the driver-catalog-4.0.0 one again, so devices provisioned on mclimate:co2-display-lite:1 keep the payload and downlink bytes they had in 4.0.0; the 5.0.0 changes (the watchdog parameters response reports wdpC 3 instead of 22, the images visibility (0x83) and uplink on button press (0x2f) responses are decoded, and downlink encoding is added) are only in mclimate:co2-display-lite:2. The examples are the 4.0.0 behaviour (examples the 4.0.0 code cannot run are dropped) and the BACnet mapping moves to mclimate:co2-display-lite:2, the BACnet owner of the model. Package 1.2.2. |
mclimate:co2-display-lite:2 | added | MClimate manufacturer driver as a v2: co2-display-lite changes its payload — The manufacturer's driver shipped as mclimate:co2-display-lite:1 in 5.0.0 is not backward compatible with 4.0.0: the watchdog parameters response reports wdpC 3 instead of 22, the images visibility (0x83) and uplink on button press (0x2f) responses are decoded, and downlink encoding is added. It becomes mclimate:co2-display-lite:2 (package 2.0.0), with the private extractPoints and the BACnet mapping, and is the default driver of new co2-display-lite devices. Devices provisioned on mclimate:co2-display-lite:1 keep the 4.0.0 behaviour. |
mclimate:co2-pir-lite:1 | updated | back to the 4.0.0 driver; the manufacturer driver moves to mclimate:co2-pir-lite:2 — index.js is the driver-catalog-4.0.0 one again, so devices provisioned on mclimate:co2-pir-lite:1 keep the payload and downlink bytes they had in 4.0.0; the 5.0.0 changes (setPIRBlindPeriod no longer encodes (4C0014 -> nothing), and enable PIR, occupancy timeout and restart downlinks are added) are only in mclimate:co2-pir-lite:2. The examples are the 4.0.0 behaviour (examples the 4.0.0 code cannot run are dropped) and the BACnet mapping moves to mclimate:co2-pir-lite:2, the BACnet owner of the model. Package 1.2.2. |
mclimate:co2-pir-lite:2 | added | MClimate manufacturer driver as a v2: co2-pir-lite changes its payload — The manufacturer's driver shipped as mclimate:co2-pir-lite:1 in 5.0.0 is not backward compatible with 4.0.0: setPIRBlindPeriod no longer encodes (4C0014 -> nothing), and enable PIR, occupancy timeout and restart downlinks are added. It becomes mclimate:co2-pir-lite:2 (package 2.0.0), with the private extractPoints and the BACnet mapping, and is the default driver of new co2-pir-lite devices. Devices provisioned on mclimate:co2-pir-lite:1 keep the 4.0.0 behaviour. |
mclimate:fan-coil:1 | updated | back to the 4.0.0 driver; the manufacturer driver moves to mclimate:fan-coil:2 — index.js is the driver-catalog-4.0.0 one again, so devices provisioned on mclimate:fan-coil:1 keep the payload and downlink bytes they had in 4.0.0; the 5.0.0 changes (temperatures and deltas are scaled (external sensor temperature, temperature sensor compensation, delta temperatures 2 and 3: 250 -> 25, 300 -> 3), manualTargetTemperatureUpdate is decoded on two bytes, the FCT operational mode (0x53) and region (0xa4) responses are decoded, and the downlink commands carry the manufacturer's command bytes and scale (frost protection 4F01 -> 4E01, read frost protection 4D -> 4F, target temperature step 0300 -> 0305, delta temperature 1 6A03 -> 6A1E, watchdog parameters encodable)) are only in mclimate:fan-coil:2. The examples are the 4.0.0 behaviour (examples the 4.0.0 code cannot run are dropped) and the BACnet mapping moves to mclimate:fan-coil:2, the BACnet owner of the model. Package 1.1.2. |
mclimate:fan-coil:2 | added | MClimate manufacturer driver as a v2: fan-coil changes its payload — The manufacturer's driver shipped as mclimate:fan-coil:1 in 5.0.0 is not backward compatible with 4.0.0: temperatures and deltas are scaled (external sensor temperature, temperature sensor compensation, delta temperatures 2 and 3: 250 -> 25, 300 -> 3), manualTargetTemperatureUpdate is decoded on two bytes, the FCT operational mode (0x53) and region (0xa4) responses are decoded, and the downlink commands carry the manufacturer's command bytes and scale (frost protection 4F01 -> 4E01, read frost protection 4D -> 4F, target temperature step 0300 -> 0305, delta temperature 1 6A03 -> 6A1E, watchdog parameters encodable). It becomes mclimate:fan-coil:2 (package 2.0.0), with the private extractPoints and the BACnet mapping, and is the default driver of new fan-coil devices. Devices provisioned on mclimate:fan-coil:1 keep the 4.0.0 behaviour. |
mclimate:flood-sensor:1 | updated | back to the 4.0.0 driver; the manufacturer driver moves to mclimate:flood-sensor:2 — index.js is the driver-catalog-4.0.0 one again, so devices provisioned on mclimate:flood-sensor:1 keep the payload and downlink bytes they had in 4.0.0; the 5.0.0 changes (the command responses (keepAliveTime 0x12, flood alarm duration 0x06) are decoded and their keepalive trailer no longer read as flood/tamper/battery/temperature values, the fraud reason is decoded, a too short payload returns an error, and downlink encoding is added) are only in mclimate:flood-sensor:2. The examples are the 4.0.0 behaviour (examples the 4.0.0 code cannot run are dropped) and the BACnet mapping moves to mclimate:flood-sensor:2, the BACnet owner of the model. Package 1.2.3. |
mclimate:flood-sensor:2 | added | MClimate manufacturer driver as a v2: flood-sensor changes its payload — The manufacturer's driver shipped as mclimate:flood-sensor:1 in 5.0.0 is not backward compatible with 4.0.0: the command responses (keepAliveTime 0x12, flood alarm duration 0x06) are decoded and their keepalive trailer no longer read as flood/tamper/battery/temperature values, the fraud reason is decoded, a too short payload returns an error, and downlink encoding is added. It becomes mclimate:flood-sensor:2 (package 2.0.0), with the private extractPoints and the BACnet mapping, and is the default driver of new flood-sensor devices. Devices provisioned on mclimate:flood-sensor:1 keep the 4.0.0 behaviour. |
mclimate:ht-pir-lite:1 | updated | back to the 4.0.0 driver; the manufacturer driver moves to mclimate:ht-pir-lite:2 — index.js is the driver-catalog-4.0.0 one again, so devices provisioned on mclimate:ht-pir-lite:1 keep the payload and downlink bytes they had in 4.0.0; the 5.0.0 changes (setPIRBlindPeriod no longer encodes (4C0014 -> nothing), the keepAliveTime response (0x12) is decoded, and enable PIR, occupancy timeout and restart downlinks are added) are only in mclimate:ht-pir-lite:2. The examples are the 4.0.0 behaviour (examples the 4.0.0 code cannot run are dropped) and the BACnet mapping moves to mclimate:ht-pir-lite:2, the BACnet owner of the model. Package 1.2.2. |
mclimate:ht-pir-lite:2 | added | MClimate manufacturer driver as a v2: ht-pir-lite changes its payload — The manufacturer's driver shipped as mclimate:ht-pir-lite:1 in 5.0.0 is not backward compatible with 4.0.0: setPIRBlindPeriod no longer encodes (4C0014 -> nothing), the keepAliveTime response (0x12) is decoded, and enable PIR, occupancy timeout and restart downlinks are added. It becomes mclimate:ht-pir-lite:2 (package 2.0.0), with the private extractPoints and the BACnet mapping, and is the default driver of new ht-pir-lite devices. Devices provisioned on mclimate:ht-pir-lite:1 keep the 4.0.0 behaviour. |
mclimate:w-thermostat:1 | updated | back to the 4.0.0 driver; the manufacturer driver moves to mclimate:w-thermostat:2 — index.js is the driver-catalog-4.0.0 one again, so devices provisioned on mclimate:w-thermostat:1 keep the payload and downlink bytes they had in 4.0.0; the 5.0.0 changes (the PIR check period response (0x4b) is decoded on two bytes (0 -> 60), the region response (0xa4) is decoded, and the downlinks carry the manufacturer's command bytes (setTargetTemperature 2E00D7 -> 5000D7 for 21.5C, 2E00C8 -> 2E14 for 20C, setWatchDogParams 1C1D -> 1C0205)) are only in mclimate:w-thermostat:2. The examples are the 4.0.0 behaviour (examples the 4.0.0 code cannot run are dropped) and the BACnet mapping moves to mclimate:w-thermostat:2, the BACnet owner of the model. Package 1.1.2. |
mclimate:w-thermostat:2 | added | MClimate manufacturer driver as a v2: wireless-thermostat changes its payload — The manufacturer's driver shipped as mclimate:w-thermostat:1 in 5.0.0 is not backward compatible with 4.0.0: the PIR check period response (0x4b) is decoded on two bytes (0 -> 60), the region response (0xa4) is decoded, and the downlinks carry the manufacturer's command bytes (setTargetTemperature 2E00D7 -> 5000D7 for 21.5C, 2E00C8 -> 2E14 for 20C, setWatchDogParams 1C1D -> 1C0205). It becomes mclimate:w-thermostat:2 (package 2.0.0), with the private extractPoints and the BACnet mapping, and is the default driver of new wireless-thermostat devices. Devices provisioned on mclimate:w-thermostat:1 keep the 4.0.0 behaviour. |