Aeon Multisensor 6 - Motion Issues?

JHoke · April 30, 2018, 11:37pm

I just moved one of my Aeon Multisensor 6 devices over to Hubitat, paired just fine (granted its about 6" from the HE Hub... )

It was discovered and has the correct driver (Default HE Aeon Multisensor 6 driver)

I had issues with detecting motion - which seem to resolved after 10m for some reason... but I still cant seem to find a way to adjust anything but the sensitivity, not the timing / timeouts etc for motion detections, or other data updates ... is there a way to do this, or another driver/dth that will allow these to be configured as they were under ST?

It looks like when I removed it from ST it reset back to factory settings which are not 'fast/frequent' enough for this usecase

JHoke · April 30, 2018, 11:52pm

The one I have installed to HE is on USB power so I had it reporting much more frequently, but I have one on ST still (Battery powered) that shows the following settings/prefs:

|Name|Type|Value|
| --- | --- | --- |
||paragraph||
|101|enum|241|
|111|number|300|
|201|decimal||
|202|number||
|203|number||
|204|number||
|3|number|60|
|4|number|5|
|40|enum|1|
|41|number|20|
|42|number|5|
|43|number|2|
|44|number|10|
|45|number|2|
|5|enum|1|
|8|number|30|
|81|enum|0|
|enableDebugging|boolean|true|

Based on what I recall of the pref names, I am trying to set 111 & 3 (Reporting time for Group1, PIR motion reset/timeout)

Does the current driver not expose those to be reset?

csteele · May 1, 2018, 12:26am

I have 12 of them with this DH working (mostly) for me.

I modified someone else's to allow for the NULL values on many of the device options.

Maybe it will work for you, but the native one, is, like you found, working poorly.

https://community.hubitat.com/t/another-aeon-multisensor-6-dh/1643

ajayjohnm · May 1, 2018, 12:46am

Another suggestion would be to use erocm123’s handler that Aeon officially recommends too.
The handler doesn’t work as is, in Hubitat but I have tweaked some functions to make it work.
It supports tweaking almost all the parameters that the sensor uses. All credits go to him.

github.com

ajayjohn/SmartThingsPublic/blob/hubitat-patches/devicetypes/erocm123/aeon-multisensor-6-advanced.src/aeon-multisensor-6-advanced.groovy

/**
 *
 *  Aeon Multisensor 6 (Advanced)
 *   
 *	github: Eric Maycock (erocm123)
 *	email: erocmail@gmail.com
 *	Date: 2017-03-08 6:45 PM
 *	Copyright Eric Maycock
 *
 *  Code has elements from other community sources @CyrilPeponnet, @Robert_Vandervoort. Greatly reworked and 
 *  optimized for improved battery life (hopefully) :) and ease of advanced configuration. I tried to get it
 *  as feature rich as possible. 
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License

This file has been truncated. show original

csteele · May 1, 2018, 12:52am

Yep, I started there too and found the other one was able to get me closer. Perhaps they are starting to converge without intent

ajayjohnm · May 1, 2018, 12:54am

Oh cool!
I’m gonna try your handler too now as the NULL aspect seems interesting

JHoke · May 1, 2018, 8:47am

@csteele @ajayjohnm Thank you both! gonna give them a shot tonight when i get home from work

DeveloperDavidB · May 2, 2018, 3:28pm

I put this in the wrong thread a few minutes ago. Copy and pasted this in here and deleting from the other thread. I am currently trying to automate my master bathroom lights and exhaust fans. two of these Multisensor 6’s are installed in the ceiling, one right at the entrance of the bathroom, and the other above the shower. This V1 driver does allow you to set a shorter reporting / active time for the motion, but changes in humidity seem to be taking a very long time to report. Last night I ran the shower for 20 min with no change in humidity detected. Mirrors were foggy. driver humidity reading stayed at 50%. around 30 min after turning the shower off, the humidity reporting jumped to 69% which turned on the fan. By the time the fan turned on, I was already in bed.

Tonight I will try the built in driver again and see if the humidity reporting is quicker, although I already know the motion reporting stays detected for an almost useless length of time. Seems like 10 min or so.

I wonder if @mike.maxwell would be willing to add the ability to adjust the timings to the built in driver that he already built?

csteele · May 2, 2018, 3:42pm

The Sensors Report Interval sets how often changes in values (other than Motion, Tamper) report.

6 sensors, 4 of them report only as often as the Sensors Report Interval tells it to. I have mine set to 1 hour and Live Logs show that's what I'm getting.

2018-05-02 08:35:02.174:debug  raw uv index = 0
2018-05-02 08:35:01.999:debug  raw illuminance = 9
2018-05-02 08:35:01.998:debug   in multi level report cmd = SensorMultilevelReport(precision:0, scale:1, sensorType:3, sensorValue:[0, 9], size:2)
2018-05-02 08:35:00.832:debug  raw humidity = 48
2018-05-02 08:35:00.831:debug   in multi level report cmd = SensorMultilevelReport(precision:0, scale:0, sensorType:5, sensorValue:[48], size:1)
2018-05-02 08:35:00.143:debug  the temp = 67.9
2018-05-02 08:35:00.138:debug  startval = 67.9
2018-05-02 08:35:00.137:debug  offset = null
2018-05-02 08:35:00.135:debug  scaled scaled sensor value = 67.9 scale = 1
2018-05-02 08:35:00.125:debug  raw temp = 67.9

It's a Battery thing for me. I am not using the values for automation, so I don't need those reports to power up the ZWave radio and reduce battery life. I have a dozen of them all running on battery power and it seems like I'm always changing batteries. Each set lasts a while, but "a while" divided by 12 is "too often."

DeveloperDavidB · May 2, 2018, 3:47pm

Thanks for this info CSteeie. Strange thing is this behavior was with a setting of 4 minutes.

csteele · May 2, 2018, 3:49pm

you know how to do live logging? Cuz that’s a 4 min investment to find out if the reports are being sent. If they are then the next step is to alter something (Cover the light hole, add humidity, add some IR, etc.) and see if the values are moving each report.

If not, that would be a call to Aeon, I believe.

DeveloperDavidB · May 2, 2018, 3:50pm

I hear ya. I have 5 so far, but plans for more. I love the flush ceiling mount.

DeveloperDavidB · May 2, 2018, 3:51pm

Yes, will do. Thanks for the suggestion

csteele · May 2, 2018, 3:54pm

I have two Recessors in boxes because I love the IDEA of them… just never gotten around to adding power within one USB wire length. So they are all still battery driven Plus mine are all mounted using 3M’s Command strips so it’s just TOO easy to move around. Same for my Aeon Wallmotes.

I did recently shift my purchasing to the Dome motion/light sensor.

It is battery only and only one battery at that, so it’s a “preview” of Aeon’s next gen Multisensor. It mounts with a MAGNET so it’s super easy to adjust, take down, etc.

csteele · May 2, 2018, 4:00pm

Can I plead for some advice on where you are succesfully mounting them? Ceiling I assume, but how do you avoid stray triggering from hall traffic (outside the room) - does the Recessor really allow enough of an angle away from the door if it’s mounted above (or in close proximity to) the doorway?

Mine are all stuck to walls within a foot or two of a door, facing inwards to the room, canted away from the door. Triggering occurs a foot or two inside the room, not in the approach to the room.

DeveloperDavidB · May 2, 2018, 4:29pm

Yesterday I added 4 of the 5, so they are not in their recessor's yet. for now I am planning on leaving them taped to the ceiling for a week so that I can easily move them to hone in on the best location. Once I am sure where I want them, I will cut the holes. The one I already have in a recessor is in my kitchen.

The new ones went into my laundry room, master closet, and 2 in master bath. I have them mounted really close to the door so the wall above the doors will block motion from walking down the hall in close proximity to the door. All are going to remain battery powered. It is easy to remove the motion from the recessor to change batteries. Its just spring loaded to the ceiling drywall.

DeveloperDavidB · May 2, 2018, 4:37pm

In the last hour, the live log only shows reporting of humidity once. I just resaved the settings and hit the configure button just in case I forgot to do that when setting it up. Will report back when I know more

DeveloperDavidB · May 2, 2018, 4:56pm

Still no reporting from the shower humidity. This V1 driver seems to be a no go for humidity.

DeveloperDavidB · May 2, 2018, 7:02pm

This is what my logs are looking like after I click configure.

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:58:26.479:debugmotion inactive

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:58:26.475:debugparse() &gt;&gt; description: zw device: 59, command: 7105, payload: 00 00 00 FF 07 00 00 00

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:58:26.041:debugmotion inactive

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:58:26.039:debugparse() &gt;&gt; description: zw device: 59, command: 2001, payload: 00

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:54:03.494:debugparse() &gt;&gt; description: zw device: 59, command: 7105, payload: 00 00 00 FF 07 08 00 00

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:54:03.045:debugmotion active

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:54:03.043:debugparse() &gt;&gt; description: zw device: 59, command: 2001, payload: FF

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:53:03.170:debugmotion inactive

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:53:03.166:debugparse() &gt;&gt; description: zw device: 59, command: 7105, payload: 00 00 00 FF 07 00 00 00

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:53:02.727:debugmotion inactive

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:53:02.725:debugparse() &gt;&gt; description: zw device: 59, command: 2001, payload: 00

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:49:02.388:debugparse() &gt;&gt; description: zw device: 59, command: 7105, payload: 00 00 00 FF 07 08 00 00

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:49:01.927:debugmotion active

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:49:01.924:debugparse() &gt;&gt; description: zw device: 59, command: 2001, payload: FF

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:40:48.513:debugmotion inactive

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:40:48.508:debugparse() &gt;&gt; description: zw device: 59, command: 7105, payload: 00 00 00 FF 07 00 00 00

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:40:48.059:debugmotion inactive

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:40:48.056:debugparse() &gt;&gt; description: zw device: 59, command: 2001, payload: 00

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:36:46.282:debugparse() &gt;&gt; description: zw device: 59, command: 7105, payload: 00 00 00 FF 07 08 00 00

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:36:45.845:debugmotion active

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:36:45.841:debugparse() &gt;&gt; description: zw device: 59, command: 2001, payload: FF

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:55.267:infosending commands: [WakeUpIntervalSet(nodeid:1, seconds:180), VersionGet(), FirmwareMdGet(), AssociationSet(groupingIdentifier:1, nodeId:1), AssociationSet(groupingIdentifier:2, nodeId:1), ConfigurationSet(configurationValue:[0, 0, 0, 241], defaultValue:false, parameterNumber:101, scaledConfigurationValue:241, reserved11:0, size:4), ConfigurationSet(configurationValue:[0, 0, 0, 1], defaultValue:false, parameterNumber:102, scaledConfigurationValue:1, reserved11:0, size:4), ConfigurationSet(configurationValue:[0, 120], defaultValue:false, parameterNumber:3, scaledConfigurationValue:120, reserved11:0, size:2), ConfigurationSet(configurationValue:[5], defaultValue:false, parameterNumber:6, scaledConfigurationValue:5, reserved11:0, size:1), ConfigurationSet(configurationValue:[0, 0, 0, 180], defaultValue:false, parameterNumber:111, scaledConfigurationValue:180, reserved11:0, size:4), ConfigurationGet(parameterNumber:111), ConfigurationSet(configurationValue:[0, 0, 28, 32], defaultValue:false, parameterNumber:112, scaledConfigurationValue:7200, reserved11:0, size:4), ConfigurationSet(configurationValue:[1], defaultValue:false, parameterNumber:40, scaledConfigurationValue:1, reserved11:0, size:1), ConfigurationSet(configurationValue:[1], defaultValue:false, parameterNumber:41, scaledConfigurationValue:1, reserved11:0, size:1), ConfigurationSet(configurationValue:[2], defaultValue:false, parameterNumber:5, scaledConfigurationValue:2, reserved11:0, size:1), ConfigurationSet(configurationValue:[1], defaultValue:false, parameterNumber:7, scaledConfigurationValue:1, reserved11:0, size:1), BatteryGet(), SensorBinaryGet(sensorType:null), SensorMultilevelGet(sensorType:1, scale:0), SensorMultilevelGet(sensorType:3, scale:0), SensorMultilevelGet(sensorType:5, scale:0), SensorMultilevelGet(sensorType:27, scale:0)]

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:55.207:debugwake time reset to 180

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:55.189:debugmin temp change for reporting = 1

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:55.186:debugtemp scale = F

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:55.182:debugTz Offset = 2

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:55.179:debugHumidity adjust = 0

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:55.176:debugTemperature adjust = 0

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:55.173:debugMotion Sensitivity = 5

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:55.169:debugMotion Delay Time = 2 minutes

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:55.166:debugIn configure report interval value = 3 minutes

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:55.162:debugMaster Bath Motion Shower is configuring its settings

[dev:540](http://192.168.1.38/logs#dev540)2018-05-02 11:33:47.038:infosending commands: [WakeUpIntervalSet(nodeid:1, seconds:180), VersionGet(), FirmwareMdGet(), AssociationSet(groupingIdentifier:1, nodeId:1), AssociationSet(groupingIdentifier:2, nodeId:1), ConfigurationSet(configurationValue:[0, 0, 0, 241], defaultValue:false, parameterNumber:101, scaledConfigurationValue:241, reserved11:0, size:4), ConfigurationSet(configurationValue:[0, 0, 0, 1], defaultValue:false, parameterNumber:102, scaledConfigurationValue:1, reserved11:0, size:4), ConfigurationSet(configurationValue:[0, 120], defaultValue:false, parameterNumber:3, scaledConfigurationValue:120, reserved11:0, size:2), ConfigurationSet(configurationValue:[5], defaultValue:false, parameterNumber:6, scaledConfigurationValue:5, reserved11:0, size:1), ConfigurationSet(configurationValue:[0, 0, 0, 180], defaultValue:false, parameterNumber:111, scaledConfigurationValue:180, reserved11:0, size:4), ConfigurationGet(parameterNumber:111), ConfigurationSet(configurationValue:[0, 0, 28, 32], defaultValue:false, parameterNumber:112, scaledConfigurationValue:7200, reserved11:0, size:4), ConfigurationSet(configurationValue:[1], defaultValue:false, parameterNumber:40, scaledConfigurationValue:1, reserved11:0, size:1), ConfigurationSet(configurationValue:[1], defaultValue:false, parameterNumber:41, scaledConfigurationValue:1, reserved11:0, size:1), ConfigurationSet(configurationValue:[2], defaultValue:false, parameterNumber:5, scaledConfigurationValue:2, reserved11:0, size:1), ConfigurationSet(configurationValue:[1], defaultValue:false, parameterNumber:7, scaledConfigurationValue:1, reserved11:0, size:1), BatteryGet(), SensorBinaryGet(sensorType:null), SensorMultilevelGet(sensorType:1, scale:0), SensorMultilevelGet(sensorType:3, scale:0), SensorMultilevelGet(sensorType:5, scale:0), SensorMultilevelGet(sensorType:27, scale:0)]

csteele · May 2, 2018, 7:22pm

That looks correct. 3 mins (180 seconds) with the report being sent to node 1 (Hubitat I'd expect)

I'll set mine down to one minute and see if I can duplicate.