Aeotec MultiSensor6 - Open Z-wave Commander - Updating parameter 201
My sensor returns 24 degrees while it should return 20.
I've found that parameter 201 [1 byte dec] is used to offset the value.
- You need to set a negative offset of -40 to this setting.
- So you will need to set Parameter 201 [1 byte dec]: -40
- If that isn't working, then we will need to do this to set this:
- 255 - (40 - 1) = 214
- So set parameter 201 [1 byte dec]: 214
Setting a correction value through "Open Z-wave Commander" for the temperature parameter (201) isn't successfull, actually the setting is lost after restart of DomotiGa, other than that nothing happens and I am still receiving 24.4 degrees while it is actually 20.
I have build a complete new installation with latest versions pulled as described in the installation manual. When you require additional info, please let me know.
#5 Updated by marmachine about 3 years ago
I'm no expert, but while talking to Aeotec support (they were very helpfull by the way) i have been trying to get this to work.
I think this one in specific could be OZW related indeed, see the attachment (This_is_where_the_configuration_is_wrong.pdf) shows - circled in red - what the problem/cause is.
I've received this from Aeotec.
I have also setup a test with Domoticz, same issue there on the parameters 201-204, however with Domoticz i do receive UV and Vibration! (the other bugs)
Setting any of the correction values (parameters 201-204) will fail i think, so for temperature as well as humidity, luminance or uv that probably won't work unfortunately.
Good to know is that, as i uplugged USB power en went to battery power instead, temperature value dropped with about 4 degrees celsius.
The device appears to be heating up when on USB power.
Apart from the bugs i think the device is awesome and worth it's money, hopefully someone will fix these bugs in time so we get to the full advantage of it.
#6 Updated by wwolkers about 3 years ago
I'm no open-zwave expert but can you try this:
In config/aeotec/multisensor6.xml, you have:
<Value type="short" index="201" genre="config" label="Temperature Calibration" value="0">
<Help>The calibration value = standard value ‐ measure value.
E.g. If measure value =25.3°C and the standard value = 23.2°C, so the calibration value= 23.2°C ‐ 25.3°C= ‐2.1°C (0xFFEB).
If the measure value =30.1°C and the standard value = 33.2°C, so the calibration value= 33.2°C ‐ 30.1°C=3.1°C (0x001F).
The type="short" means that the field is 2 bytes long... try changing that to type="byte" and see if that helps.
remove (or backup) any zwcfg_*.xml file and restart your application.
#7 Updated by johanvandyck about 3 years ago
My sensor arrived as well. Also here some trouble.
I updated till the latest openzwave (589 if i'm not mistaken). Device was recognised without any problem, but Domotiga Z-wave commander can't coop with alle parameters...
The temperature calibration type is "short" and should be short (= 2 bytes). The official device certification indicates it should be. http://products.z-wavealliance.org/products/1403/embedconfigs
Only the UV index should be "byte". This is the case: config/aeotec/multisensor6.xml has "byte" in it for UV.
My temperature is in USB mode about -4.2 wrong (measured: 28.5 °C; real value = 23.3 °C; difference -4.32°C). However z-wave commandor won't accept negative values. I updated directly in the zwcfg_0x0184cf27.xml config file: -42.
<Value type="short" genre="config" instance="1" index="201" label="Temperature Calibration" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-32768" max="32767" value="-42"> <Help>The calibration value = standard value ‐ measure value. E.g. If measure value =25.3°C and the standard value = 23.2°C, so the calibration value= 23.2°C ‐ 25.3°C= ‐2.1°C (0xFFEB). If the measure value =30.1°C and the standard value = 33.2°C, so the calibration value= 33.2°C ‐ 30.1°C=3.1°C (0x001F).</Help>note: to convert values:
- take difference without decimal point. Convert to HEX.
(-42)d = (D6)h. We padd the result. for negative values: padding with F, for positive values, padding with "0". --> FFD6
See also http://math.stackexchange.com/questions/408761/hexadecimal-value-of-a-negative-number but a calculator can help
- However zwcfg_0x0184cf27.xml requires a decimal value (decimal point left out): -42 in my case.
Keep in mind for some reason z-wave commander is not picking all changes immediatly. Not figured out yet when ik updates.
Conclusion: I can change the temperature offset, but not via the z-wave commandor; only via the wrapper directly.