Yes window glass will greatly reduce, if not block, the UV.
Very hard too get sunburned when behind glass.
expected this, but didn't expect it to 100% block.
Edit: tested earlier by putting on window sill and got 32oc and value of 4 on ultraviolet 
so yes windows block it all!
love the driver thanks @csteele, just a couple of questions sorry.
How do we stop the double logging of activity?
dev:3572019-08-09 10:41:17.579 pm infoAeon multi 6 a motion inactive
dev:3572019-08-09 10:41:17.366 pm infoAeon multi 6 a motion inactive
motion sensor delay time, thats the delay between active and inactive correct ? I have a bunch of the iris MS here but im not sure what their threshold is to match it.
If I extend out the report interval, that slows down the update if any of the values change? (lux, temp etc)
Enable selective reporting will bring down the huge reports its spitting out now ?
Yes, for inactive... But active will report right away. So it's the delay for it to turn active to inactive if no motion has been detected, every time it registers activity it resets the timer.
Yes, this is important to watch out for if the device is battery operated... Mine are on wired, so I can set it as fast as I want.
@csteele, can you answer the last question? I'm curious also. The "lastUpdate" items are filling the event log up in a horizontal way so that is doesn't make it very handy for normal use. Thanks.
1 Like
All 6 of the sensors will report anytime they exceed their threshold. Clearly for the Motion and Tamper sensor, the threshold is pretty much binary, although, Motion's sensitivity can be set between 1-5. But any motion causes a report. Any Tamper, causes a report. Any Temp that is different from the previous report by x tenths of a degree causes a report. Similar for Humidity, Illuminance and UV. They will each report when there's enough of a change. But there's also a report periodically so that when there's no significant change, all the sensors report. You can set the %'s individually and you can set the period of the 'all report'
You can define that UV reports on 10% change while RH reports on 2% change, etc. by setting the "Change Amounts" fields. Selective Reports enables these:
Enable/disable the selective reporting only when measurements reach a certain threshold or percentage, but is disabled if battery powered.
Enable/disable the selective reporting only when measurements reach a certain threshold or percentage. This is used to reduce network traffic. Note: If USB power, the Sensor will check the threshold every 10 seconds. If battery power, the Sensor will check the threshold when it is waken up.
Not sure it will help, but here's a nicely formatted version of the Manual:
http://manuals-backend.z-wave.info/make.php?lang=en&sku=AEOEZW100&cert=ZC10-16065113
I think it was @ericm identified this problem quite some time ago, not specifically for this device, but most ZWave devices.... They send two reports.
Notice there's no option for "Both".. yet that's what they do. I commented out line 394 in my copy of the Driver to ignore the SensorBinaryReport and indeed, only one shows in the log. Note that the traffic is still on the mesh, the driver just ignores it. For that reason, I don't think I'll leave it that way.. I'd rather have logs that inform.
1 Like
I have mine on USB too - I can only imagine the cost of replacing all these batteries after all the initial testing iver had to do lol.
so a dual reports not a error, the log just sees both. No probs if thats the case.
@csteele is there any way I can stop these messages from getting in my logs? Besides editing the driver code myself?
Figured I'd post this here...just in case... Anyone else see something like this?
I've never seen the humidity fluxuate this much this quick. Bad device? Something that changed in the new HE version? Anyone else?
maybe.. this is from an event log:
humidity 51% 2019-10-01 11:42:26.859 AM PDT humidity 50% 2019-10-01 12:27:26.814 PM PDT humidity 60% 2019-10-01 12:47:26.797 PM PDT humidity 67% 2019-10-01 12:52:26.792 PM PDT humidity 73% 2019-10-01 12:57:26.784 PM PDT humidity 69% 2019-10-01 01:02:26.781 PM PDT humidity 67% 2019-10-01 01:07:26.773 PM PDT humidity 64% 2019-10-01 01:32:26.757 PM PDT humidity 63% 2019-10-01 01:37:26.754 PM PDT
Is anyone else also also having issues with the ultravioletindex?
Yes, my ultra-violet always measures 0.
Good point! Thanks.
I've used these for some time and the sunlight must strike the face of the sensor for UV to be detected. Naturally, any UV filtering in the way will negate that function. I first had one under an eave, for weather protection, near the front door and it never indicated any UV level simply aimed at the yard. If you place it in direct sunlight it will absolutely work but then you have it exposed to the sky and it is not weather proof. I have no use for the UV data so it's never been an issue for me.
1 Like
I installed the latest driver code some of my sensors report 10 degrees higher in temp then if I use the hubitat built in driver.?? If i switch back to built in driver they go back to reporting normal temps
I have quite a few and haven't seen that...
I opened a Live Logging tab then turned on debugging on one of the Multisensors. After clicking Save Preferences, there's a LOT of debugs... which is the Hub sending (simultaneously) about 20 commands to the Multisensor.. and then there's the wait for the Multisensor to respond.. But when it does respond, one of the results is:
dev:845 2020-06-05 02:15:13.947 pm info Temperature is 80.1°F dev:845 2020-06-05 02:15:13.944 pm debug finalval = 80.1 dev:845 2020-06-05 02:15:13.936 pm debug raw temp = 26.7 dev:845 2020-06-05 02:15:13.934 pm debug In multi level report cmd = SensorMultilevelReport(precision:1, scale:0, sensorType:1, sensorValue:[1, 11], size:2, scaledSensorValue:26.7)
26.7c is 80.06f -- which looks to me like a correct result.
I'll inspect the code, because the most recent change was dealing with the tempOffset per @christie999 However, a brief glance at the command that was affected by that change shows it to be correct/as expected too:
dev:845 2020-06-05 02:25:19.181 pm debug Sending Z-wave command: ConfigurationSet(configurationValue:[6, 2], defaultValue:false, parameterNumber:201, reserved11:0, size:2)
(configurationValue:[6, 2], <-- the 6 in that line is what would have been affected.. and 6 is what I put in for that field. But like I said, I'll recheck.
dev:14412020-06-05 02:42:13.034 pm debugfinalval = 74.3
dev:14412020-06-05 02:42:13.030 pm debugraw temp = 23.5
dev:14412020-06-05 02:42:13.027 pm debugIn multi level report cmd = SensorMultilevelReport(precision:1, scale:0, sensorType:1, sensorValue:[0, 235], size:2, scaledSensorValue:23.5)
Thanks for that info, Looks correct in my logs I'll give it some time because the temps are dropping towards normal but very slowly.
actually I'll switch one of the sensors back to built in driver and see if the temps go back to normal something weird is going on.
As promised, I looked at the code and although I didn't find anything related to temp, I did find two other questionable areas and I've attempted to fix them... along with what seems like a never ending need to 'beautify' the code with consistent indenting, etc. 
-
Clicking Save Preferences seems to have always been sending the set of parameters twice. That can't be right... it's pretty rare, unless like me, you're developing.
So I've reduced it to once per. -
Motion Detection (meaning a report arrived from the MS6 indicating Motion active or inactive) occurs twice. Once using what Aeon calls Notification: Home Security:
...and again via basicSet or via sensorBinary.
dev:845 2020-06-07 11:31:58.981 am info Motion is active by SensorBinaryReport dev:845 2020-06-07 11:31:56.062 am info Motion is active by NotificationReport
...don't need duplicates. I decided to 'clip' the NotificationReport and have it just deal with Acceleration and Tamper, allowing the SensorBinaryReport to facilitate Motion detection.
These changes don't do anything to/for the Device, they simply make the Logs look better 
I have 12 of these MultiSensor 6's and I'm going to test overnight to verify all the motion events I care about continue to occur.
If successful, I'll release the code as v1.7 tomorrow.
3 Likes
