I’m hoping @chris or someone else can chime in on this since there was a similar issue in 2016 (Aeotec Multi-Sensor 6 ZW100-C -Temperature Calibration). I’ve been working with AeoTec for several weeks to confirm that the current MultiSensor 6 (1.12 firmware) is indeed calibrated the same way as the previous 1.07 firmware units.
Quoting on of their engineers…
As per parameter 201, the value is in a scale of x0.1, so a value of 10 = 1.0 degree change. For value -5.0, you will input:
0xCE02
Where value CE = temperature change (0xCE = 206 (calculated from 256-50))
Where value 02 = scale of temperature in F (while 01 would be C)
0xCE02 for -5.0 degree change is 52738
There is also a spreadsheet at: https://aeotec.freshdesk.com/support/solutions/articles/6000120736-calibrating-offsetting-temperature-on-multisensor-6-excel-easy-sheet-included
So, for a -5 offset, you should be able to enter 52738 for parameter 201.
There issues are as follows:
- In PaperUI there are two 201 parameter for this value (the second is at the bottom once you click “more”). In HABmin there is only 1.
- For both PaperUI and HABmin, you cannot input a number larger than +/-127. You can an error during entry in PaperUI while with HABmin, you never see the parameter go to pending.
- For both PaperUI and HABmin it will take -5 (or +5) but I do not see a change in temperature and I’m also not sure if the unit is accepting the change. For example, I was attempted to offset by -7 and after my 900 second wakeup cycle these is what my was in my events.log file
2020-02-17 14:30:14.169 [vent.ItemStateChangedEvent] - office_temp changed from 73.4 to 23
2020-02-17 14:32:44.792 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:c46e91bd:node5’ has been updated.
2020-02-17 14:32:44.812 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=config_201_2_0000FF00, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]
2020-02-17 14:45:07.153 [vent.ItemStateChangedEvent] - office_temp changed from 23 to 73.7
2020-02-17 14:45:13.335 [vent.ItemStateChangedEvent] - office_lum changed from 7 to 10
2020-02-17 14:45:13.784 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:c46e91bd:node5’ has been updated.
2020-02-17 15:00:07.078 [vent.ItemStateChangedEvent] - office_temp changed from 73.7 to 74.2
2020-02-17 15:00:07.555 [vent.ItemStateChangedEvent] - office_rh changed from 24 to 23
2020-02-17 15:00:13.225 [vent.ItemStateChangedEvent] - office_lum changed from 10 to 12
2020-02-17 15:00:13.729 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:c46e91bd:node5’ has been updated.
At 14:45 the node certainly work up and sends a report (because group 1 reporting is also set to 900) but I don’t know if saying the thing has update means what I think it means. You can also see that at 15:00 (just in case a cycle was missed) the temp is still about same. Also, doing it this way only whole numbers and be entered. So attempting to do something like -6.5 would throw an error that says “Input should satisfy expression -?\d+”.
- One last quirk… for both PaperUI and HABmin I have randomly noticed that after I set 201 to an offset. When I go back it might change to a number up to what I am guessing is 255. For instance, I think with either a -5 or -7 offset, I saw 249 in HABmin for parameter 201. I just noticed that happening in the last couple of days and only major environment changes was that I added another sensor and a Kasa bulb. These devices do not interact.
The overarching question is what is the correct way to do the temperature calibration in OpenHAB 2.5.1 now?