When interrogating my Aeotec multisensor using the zwave configuration panel I get odd results, as shown below:
Has anyone else experienced this?
My default is set to 20, I think yours might be alittle high. 
Yeah that’s the problem. It displays 1310976 when I set it to anything. I just tried 20 (2°C) , same number (1310976 ) comes back. All the other thresholds return sensible values (humidity, UV etc…).
Could be a dud or is there another config option I’m missing?
I have (5) Command Options set to “Binary Sensor Report”, (40) Report only on thresholds set to “Enabled”, (64) Temperature scale is set to “Celsius”.
Is the multisensor awake when you push?
According to the node information panel, it is awake, it is ready and it is not failed.
Could be a dud? 
Yeah if you can set yours fine that’s what I’m beginning to think. Also I can set any of the other thresholds to any value (within their limits). Just not the temperature threshold.
It actually seems to be changing to the correct value, regardless of what is reported in the panel. Changing it to 2 (0.2°C) I get the silly value back but I see a lot more updates spaced 0.2°C apart.
Have you actually tried changing that parameter recently, and are you using a secure connection?
I haven’t tried changing it ever to be honest
Would you mind trying?
I understand if you are reluctant to.
I’ll have to try when i get home because I can’t wake the device currently.
1 Like
So I purchased another Aeotec Multisensor 6 and it is doing exactly the same thing.
Out of the box the default temperature threshold value (parameter 41) displays as 20, but if something is written to the value (e.g. 10, or 5) after a short delay it displays 1310976 as the set value. I have tried this with both secure and insecure connections. All other parameter values display correctly.
I’m pretty sure this is just a display bug as the device behaves as expected for the value entered.
It would be nice to have this confirmed on another system before I log an issue though.
Anyone?
For anyone wondering it’s a problem with OZW.
1 Like
And does anyone know if this will be fixed in home-assistant?
Assuming it has been fixed upstream like the closure of the issue implies.
This still appears to be a problem. I see the issue opened with HA was closed in reference to it being an OZW issue. That issue was also closed, however I’m still seeing this problem.
Anyone have any clues on how to get this to work?
The issue is still open… if you read the thread it links to the issue that ultimately solve the problem.
Thank you replying @petro, but I must have missed something. I read issue #1332 that @tom_l opened. I see it was closed as this is an OZW issue (#644) but that’s closed as well. I looked at the OZW config file that my 85.0 install has and it references 4 bytes for field #41, yet I still get this error.
What am I missing?
That’s what I’m saying, issue 644 is what I linked and it’s still open, meaning the issue has not been resolved. There is nothing you can do.
@petro I see. I was looking at #664 when I typed #644. I see #644 is old issue that includes several issues like the one we’re seeing. Thanks!
This is what i got from Aeotec support team which i find helpful in understanding what is going on with Parameter 41:
Using Parameter 41 with 4 byte size value
1310976 is the decimal value for 0x00140100 which uses the threshold for 2.0C. As a quick explaination to the hex values:
0x00YYZZ00
YY is the threshold setting for temperature multipied by 0.1 scale for the decimal value. So if this 0x14, this is converted to 20 for hex. This means that is a change in (20*0.1) temperature happens, it will report.
ZZ is the scale where 01 is the scale for C (while 02 is the scale for F), this shouldn’t change for you.
​Unfortunately the minimum setting is 1.0 (while 0.5 cannot be done) which is likely the setting reports back to default. For this example, i will set it to the minimum of 10 degree of change.
So converting 10 to hex, this is 0x0A, this is what will be plugged into YY
Converting 01 scale for C to hex is still 0x01, this will be plugged into ZZ.
0x000A0100 is the final value you want to use. converting this to decimal yields 655616.
So you want to input:
Parameter 41 [4 byte] = 655616
Using 1 byte size for Parameter 41
Alternatively, if you use Parameter 41 [1 byte] = 10, the reported value will report as 655616 (which converts 1 byte into its 4 byte value setting)
ie. So if Parameter 41 [1 byte] = 0x0A or 10, the Multisensor 6 will automatically convert this to 4 byte using the 0x00YYZZ00 value where 0x0A is the YY value.
If the scale is set to 01 (Celcius) or 02 (Fahrenheit) [Lets just say C degree for this example] via Parameter 64. This automatically sets ZZ value as 0x01.
So the output of Parameter 41 will report 0x000A0100 as 655616
6 Likes