Page 1 of 1

Aeotec Multisensor 6 Hum not working right

Posted: Sunday 26 April 2020 22:14
by wouterlet
Hello,

I have a Aeotec Multisensor 6 that worked fine for about a year. I could really see the humidity go up when I take a shower(to maybe 90%). But for a while now the humidity doesn't respond as I was used to (all other values are fine). I think after a powerfailure or maybe the 2020.1 update (they were right after each other).
Now my graph goes up and down, but it seems it's slower. The graph has a new value every 5 minutes but even when the shower is on for 10 minutes the value didn't go up. Also the trigger in my script doesn't work anymore to switch on the fan at >70% humidity.

I checked the parameters:

42. Humidity Reporting Threshold: set to 3% so it should send a report regugarly when starting the shower.
51. Set the upper limit value of humidity sensor: is its default 60, I don't think this will change anything?
101. Group 1 Reports: set to 241, so all values should trigger a report including humidity

I allready exchanged it with a new one, but this gives the same problem. So it seems to by domoticz or openzwave.

Any ideas?

Best regards,

Wouter Lettinga

Re: Aeotec Multisensor 6 Hum not working right

Posted: Sunday 26 April 2020 22:38
by MartinManders
Hi Wouter,

I experience the same behavior.
There is no report send when humidity rises above the threshold.

I guess it must be a openzwave issue, I use 6 sensors, the all behave the same.

No ideas,

Regards,

Martin

Re: Aeotec Multisensor 6 Hum not working right

Posted: Monday 27 April 2020 22:05
by wouterlet
OK that's at least a shared problem. 😏 I also tried it with a threshold of 100% but it also doesn't help. I mailed aeon about it. Hopefully they can help somehow.

Re: Aeotec Multisensor 6 Hum not working right

Posted: Saturday 02 May 2020 20:43
by wouterlet
Problem solved!,

I discussed it with Aeotec and came to param 48 should be 1 instead of 0. But I couldn't change this value. It's not a param in the openzwave.
I looked up the xml of the zw100 and changed there the value to 1. Now it's changed to 1 in Domoticz also. And the value is now within seconds. But I think it's a bug either in Domoticz or in openzwave.

Hope it helps you to, else don't hecitate to ask!