Aeotec multisensor temperature reporting threshold incorrect

maximosm · December 26, 2019, 5:49pm

Can you please help.I cant change the thershold for the multisensor 6 fot the temperaure and humidity . i have 4 multisensors with the same isue. application version is 1.11

prilly · September 15, 2020, 2:04pm

I think the problem here is the interpretation of the parameter.

The value 1310976 corresponds to 0x140100 = 20 and °C = 2.0°C

To set the value to 0.5°C the hex value must look like 0x50100, but this is not possible because parameter 41 is at least 10 (1.0°C).
If the value is 0xA0100 this would correspond to a Dziamal value of 655616.

prilly · September 15, 2020, 2:05pm

Anyone seen that this sensor is not reporthing at all when threshold is reached.

Also have issues with wake time. Cant set it to other values then default 3600

tom_l · September 15, 2020, 2:21pm

Dude. That was a 2 year old post. I don’t even have zwave devices anymore and it was also fixed 2 years ago:

prilly · September 15, 2020, 4:05pm

This issue is still presented in ha, and the post is old does not matter

tom_l · September 15, 2020, 4:26pm

Then it’s likely a new issue, because that issue was fixed in this PR add ZMHAD1 Qubino support by wackoracoon · Pull Request #664 · OpenZWave/open-zwave · GitHub

Yeah it does. See point 3 here.

thebatfink · October 10, 2020, 2:09pm

I see the exact same issue with parameter 41, showing 1310976. Latest HA, Zwave integration.

Trolan · October 15, 2020, 4:25am

I see the same thing with 1.12 firmware on the Aeotec and the latest HA with zwave (fresh wipe and reinstall).
Weirdly, using 655616 as the value in Parameter 41 leaves that value present, hoping that will reporting 1.0 degree changes in F.

Looking for anyone that can help

thebatfink · October 15, 2020, 5:44am

I raised it on git here, I found other parameters doing this too. No one responded yet and I see a few pending zwave issues going unfixed. I also switched to beta open zwave, behaviour is exactly the same interestingly. Feels like it’s not going to get addressed any time soon so I swallowed the cost and have now switched to a combee ii and aqara / sonoff sensors and have no issues.

Makes you wonder though, I got recommended this sensor quite a bit, don’t understand why people would recommend a sensor they aren’t able to fully configure so I assume for some people its working OK.

If anyone can confirm if this is likely to be more an open zwave issue rather than HA I’ll log it on their git too.