I have a Zooz 4-1 and use it for Lux/motion, seems to do OK for me
My humidity readings seem suspect, we have been in the single digits/teens here over the past 2 weeks and the lowest reading I could find were mid 20's
Rick
Thanks, going to try the Aeon Multisensor 6 and usb power. Now I just gotta find a settings list somewhere so I can go in with the basic zwave tool and get it setup...anyone? List of settings?
It comes with a manual that includes all the advanced settings and their website has a decent FAQ that has recommended settings.
1 Like
Found it all online...didn't realize they had that. Thank you very much. Looks like I just need selective reporting and lower the % humidity change from 10 to 1%. That should do it. I don't think I need to be reporting it every 30 seconds in addition to the % change.
Yes selective reporting is what you want but you may find 1% is a little too sensitive. I find 5% to be perfect but YMMV. I use 5% combined with a 10 minute normal report to work well for me.
What type of Humidity differential are you seeing and how quickly?
I use an Aeotec Multisensor6 driver I found and made cosmetic updates. It exposes most of the valuable parameters.
Quickly looking at that DH it actually turns OFF selective reporting. So is the % change actually working for you with that DH?
//6. disable selective reporting only on thresholds
zwave.configurationV1.configurationSet(parameterNumber: 40, size: 1, scaledConfigurationValue: 0),
And I don't see anywhere else where it's being turned on.
I've set it for an hour, and get hourly reports:
app:8482018-11-19 08:40:51.165 am infoOffice Fan Automation: MultiSensor6C (office) temperature 75.7 app:8482018-11-19 07:40:51.133 am infoOffice Fan Automation: MultiSensor6C (office) temperature 75.4 app:8482018-11-19 06:40:51.208 am infoOffice Fan Automation: MultiSensor6C (office) temperature 73.8 app:8482018-11-19 05:40:51.237 am infoOffice Fan Automation: MultiSensor6C (office) temperature 70.4 app:8482018-11-19 04:40:56.500 am infoOffice Fan Automation: MultiSensor6C (office) temperature 71.2 app:8482018-11-19 03:40:51.264 am infoOffice Fan Automation: MultiSensor6C (office) temperature 72.0 app:8482018-11-19 02:40:57.030 am infoOffice Fan Automation: MultiSensor6C (office) temperature 72.9 app:8482018-11-19 01:40:51.384 am infoOffice Fan Automation: MultiSensor6C (office) temperature 73.9 app:8482018-11-19 12:40:51.422 am infoOffice Fan Automation: MultiSensor6C (office) temperature 75.0 app:8482018-11-18 11:41:01.226 pm infoOffice Fan Automation: MultiSensor6C (office) temperature 76.4 app:8482018-11-18 10:40:51.791 pm infoOffice Fan Automation: MultiSensor6C (office) temperature 77.5 --- Live Log Started, waiting for events ---
understood. I'm looking to turn on:
- Parameter 40 [1 byte]: 1 (enable selective reporting, automatically updates reports when passing a threshold)
Then change Parameter 42 which is % change to report. Default is 10.
This way it will report WHEN the humidity changes by that % amount.
I set the report interval on the multisensor6 physically closest to me to 1 minute. It's USB powered so it should work, and as far as I can tell, it is:
dev:285 2018-11-19 09:25:21.833 am debug raw uv index = -1 dev:285 2018-11-19 09:25:21.832 am debug In multi level report cmd = SensorMultilevelReport(precision:0, scale:0, sensorType:27, sensorValue:[255], size:1, scaledSensorValue:-1) dev:285 2018-11-19 09:25:21.734 am debug raw illuminance = -32768 dev:285 2018-11-19 09:25:21.732 am debug In multi level report cmd = SensorMultilevelReport(precision:0, scale:1, sensorType:3, sensorValue:[128, 0], size:2, scaledSensorValue:-32768) dev:285 2018-11-19 09:25:20.876 am debug raw humidity = 29 dev:285 2018-11-19 09:25:20.875 am debug In multi level report cmd = SensorMultilevelReport(precision:0, scale:0, sensorType:5, sensorValue:[29], size:1, scaledSensorValue:29) dev:285 2018-11-19 09:25:19.078 am debug In BatteryReport dev:285 2018-11-19 09:25:18.082 am debug finalval = 72.5 dev:285 2018-11-19 09:25:18.079 am debug scaled sensor value = 22.5 scale = 0 precision = 1 dev:285 2018-11-19 09:25:18.074 am debug raw temp = 22.5 dev:285 2018-11-19 09:25:18.073 am debug In multi level report cmd = SensorMultilevelReport(precision:1, scale:0, sensorType:1, sensorValue:[0, 225], size:2, scaledSensorValue:22.5) dev:285 2018-11-19 09:25:16.623 am debug raw uv index = -1 dev:285 2018-11-19 09:25:16.621 am debug In multi level report cmd = SensorMultilevelReport(precision:0, scale:0, sensorType:27, sensorValue:[255], size:1, scaledSensorValue:-1) dev:285 2018-11-19 09:25:16.513 am debug motion active dev:285 2018-11-19 09:25:15.407 am debug raw illuminance = -32768 dev:285 2018-11-19 09:25:15.405 am debug In multi level report cmd = SensorMultilevelReport(precision:0, scale:1, sensorType:3, sensorValue:[128, 0], size:2, scaledSensorValue:-32768) dev:285 2018-11-19 09:25:13.262 am debug In BatteryReport dev:285 2018-11-19 09:25:07.439 am debug raw humidity = 29 dev:285 2018-11-19 09:25:07.438 am debug In multi level report cmd = SensorMultilevelReport(precision:0, scale:0, sensorType:5, sensorValue:[29], size:1, scaledSensorValue:29) dev:285 2018-11-19 09:25:03.042 am debug finalval = 72.5 dev:285 2018-11-19 09:25:03.041 am debug scaled sensor value = 72.5 scale = 1 precision = 1 dev:285 2018-11-19 09:25:03.036 am debug raw temp = 72.5 dev:285 2018-11-19 09:25:03.035 am debug In multi level report cmd = SensorMultilevelReport(precision:1, scale:1, sensorType:1, sensorValue:[2, 213], size:2, scaledSensorValue:72.5)
Ignore the illuminance = -32768 -- it's known to be defective on this specific device.
understood.
However I don't need it to report frequently. I really only want it to report when something CHANGES. So this isn't about TIME, it's about change.
Parameter 40 turns on: automatically updates reports when passing a threshold
So when it's set to (1) one. Then the other options 41 through 44. Come into play. Those options define how MUCH change must happen to temp/humidity/etc. Then the sensor should report the change when it changes by the set amount. Hope this makes sense.
What I don't want to do is have an overly chatty sensor sending updates every 30 seconds or a minute when what I'm really looking for is when the humidity jumps (shower on) and then record the % it started it...and likely leave the fan running until we are close to the initial reading.
also in the driver above, the screenshot you show. The 3 options in the middle will never come into play because option 40 is set to 0.
So the "Humidity Change Amount (%)? The percentage the humidity must change to induce an automatic report." Will not work. What should be added to the parameters is a Boolean for "turn on automatic report based on change" setting to true or false. True would turn option 40 on and false would turn it off.
I have 2 small bathrooms and both go up by 3-5 percent humidity in 5 min on the aeon. It is easy to capture when to turn on the fan for me.
1 Like
Do you then just use a set time to leave the fans or or somehow figure out the drop in humidity also to turn it off?
I have an app that I got in my ST days that I have rewrote. It looks for a rise by X% to turn on, then looks for the humidity to come down to X% difference above where it started and the highest humidity it sees to turn off with an optional delay
So, if I Set it to look for a 2% increase and turn off at 25%. If my sensor starts at 40, increases to 45, it will turn on as it is over the 2% increase since the last humidity reading. Let’s say it increases all the way to 52 percent. Then the fan will keep going until the humidity drops below 43%. Then it will either turn off, or turn off with delay.
2 Likes
@Cobra has a similar offering:
And I remember a discussion about using a sensor in another room as a base to compare, but can't jog more of that memory out at this moment 
I'll push a new version of AeotecMultiSensor6 (v1.4) to github in a few minutes, I can't test the reactivity, because this office has no change in humidity, and since lux is defective on this particular device, a flashlight won't work. 
However, I can say, it's sending values, without logging errors. 
ConfigurationSet(configurationValue:[0, 100], defaultValue:false, parameterNumber:42, scaledConfigurationValue:100, reserved11:0, size:2) ConfigurationSet(configurationValue:[5], defaultValue:false, parameterNumber:43, scaledConfigurationValue:5, reserved11:0, size:1) ConfigurationSet(configurationValue:[0, 2, 2, 0], defaultValue:false, parameterNumber:41, scaledConfigurationValue:131584, reserved11:0, size:4) ConfigurationSet(configurationValue:[1], defaultValue:false, parameterNumber:40, scaledConfigurationValue:1, reserved11:0, size:1)
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
