Just one question, is it possible to use the selective reporting just for one or two variables (temperature and lux), and having a 60 min for the rest?.
My point is when enabling group 1 selective reporting, I don’t care about humidity and UV reporting (trying to minimize battery usage).
For the record, the difference in battery usage is relevant using the 60 min reporting vs 5 min reporting using thresholds.
Rgds
Selective reporting is an all or nothing thing. Unfortunately, it can’t be applied to certain reporting groups, or sensors. You could try setting the second reporting group for humidity and uv to 60 minutes and the first for temp and lux to 5 min. Then enable selective reporting and adjust the thresholds to what you want.
Right now this handler does not support setting up a second reporting group, but you would essentially need to adjust parameter 102 & 112.
Thanks.
Do you have documentation related the params. The one I have (engineer specs) is very limited documented.
Rgds
Aeotec does a pretty good job of posting their documentation and other useful information here:
https://aeotec.freshdesk.com/support/solutions/6000084017
For some reason they haven’t posted an updated engineering document for their Multisensor 6 so I have included it here:
Thanks
If I understand correctly, selective reporting when battery operated is reviewed at interval time. Therefore, if a change of the unit is higher than the threshold, then it would report.
Obviously when USB powered, the threshold reporting makes more sense, because is checked every 10 secs.
Conclusion: Key motion sensors must be powered by USB (the ones used for temp and lux for my case)
I will check this out. On 1.07 in order for the reporting interval to be 300, the wake interval has to be 300 as well. The wake interval should be adjusted automatically with my handler, but I will setup a test scenario to make sure it is getting the right value with the settings you have set.
Is motion detection supposed to work with this handler cuz I get nothing…
@wgmcg Yeah, pretty sure I remembered to include motion detection. 
Not sure why you are having issues.
Yep, you are correct. The documentation says this is to reduce network traffic. I would also think it would improve battery life because the device wakes up but doesn’t send a report if the thresholds are not met. Although, who knows how much it actually saves in that scenario.
@cscheiene I uploaded a new version with several changes. One is that there is a better way of making sure the wake interval is set properly so that parameter 111 takes effect. Tried it several times on 1.07 without any issues. Every setting I set worked “300, 600, 900, etc.” Remember that if selective reporting is enabled you may not get reports on every wake if the thresholds are not met. Also, if you “double tap” the refresh button, the handler will reset the wake interval and parameter 111 from its memory so it will try to set and check them again.
With a few of my sensor that I have upgraded to 1.08, parameter 111 is being really funky. I would recommend against upgrading to it if you have been thinking about it. It looks like Aeotec pulled it from their support site.
Does anyone know how much power this sensor draws from USB?
I’m asking because I’d like to get a handful of these placed throughout my house, but mount them in a permanent state with power back to a USB charging hub which then is connected to an outlet in my attic (so no visible wires). Max length of active USB cables is either 22, or 15 meters (USB 2.0/3.0 respectively), so in theory, I could run them all back to a single hub /outlet.
Hi Eric, I installed your latest handler USB Power reporting is working. Now Tamper is showing active on all sensors and they stay in that state. I did a fresh install after i deleted devices and handler and no change. im on IOS and FW 1.08. Can you help, thank you.
@Mikee It’s probably because with my handler, the device hasn’t sent a “tamper clear” report yet and SmartThings is displaying the first state listed in the code (which is active). If you “bumped” the sensor until the light turned on and waited a few minutes, it would probably clear.
Alternatively, the latest version in github has the “clear” state listed first so SmartThings will probably display that state by default.
I did what you recommended, I tapped the sensors till the green light flashed and left them for couple of hours and they all still show as tamper active. What I have noticed is when I open the sensor output screen in the app tamper clear shows for a millisecond then revert to tamper active and I only noticed that is because of the color. Any other ideas? Thanks again.
Since upgrading to the latest version my sensors are also showing tamper active and won’t clear. It isn’t a big deal to me but just wanted to say you are not alone.
OK, I reinstalled an older version of the device handler, rapped on the side of the motion device until seeing a green light illuminate for about a second, which I assume is the tamper indicator.
Looking at the live log I can see no report of a tamper being received by the hub and the “Tamper Active” remains.
So best I can tell it isn’t caused by the driver.
Firmware of the motion sensor is 1.07
Log attached
Now I loaded the latest version of the device handler and made sure the debug switch is on.
Rapped on the side of the motion sensor until the green light illuminates and here is the log from that
Is the scaledSensorValue the data that indicates tamper? If So the sensor IS reporting, but the tile remains stuck on “Tamper Active”
@Mikee @an39511 I just want to make sure you guys are using the handler that I published just a few hours ago. I’ll start dating them so it is easier to keep track. I feel the handler is just about as good as it will get just got a couple things to work out.
Also, are you both on iOS? I am wondering if this is another platform difference I’ve got to work through. For the record, I am not seeing this behavior at all, but I am running on Android.
The log I just published came from your latest version on Github less than 10 minutes ago.
Hopefully the log values will help you because I am not exactly sure what I am looking at.
I am on Android
I installed the latest because know it says tamper clear but when I tapped the sensors the status does not change it stays on tamper clear. I am on IOS.
To further add to this I went into the device and changed back to the stock device handlers.
Then I went into core and setup a simple piston to send a push notification when acceleration is detected.
I tried Aeon MultiSensor Gen5 and Aeon MultiSensor 6
Neither device handler worked in being able to detect acceleration.
One thing I want to add here is that when I was using your device handler I disabled the motion sensor ability. But when I switched the device handler to the stock version(s) the sensor was still not reporting motion. This tells me that a configuration was loaded into the sensor and remains there regardless of what device handler is being used.
Changing back to your device handler and going into the setting at changing the motion setting back to the default of 5 re-enables motion and low and behold the tamper (acceleration) works again.
So disabling motion by reducing the “PIR motion sensitivity” to 0 will also disable the accelerometer.
