Motion detection is irrespective of the selective reporting, it will fire when motion is detected. Regarding lux measurements, then you will need to select 5 minutes reporting frequency, and with no threshold. Please bear in mind, you could select a threshold for the others (temp, UV, RH) so they don’t report that frequent. However, 5 minutes reporting will decrease battery life for sure.
It would be great that lux threshold to be defined by a change %. To be honest, I dont care whether the lux value change from 500 to 556, but I do care when it changes from 100 to 76. I know default is lux, but is it possible to do it? or we would require some change from the firmware…
Thank you for the explanation, perhaps I get it now
But can you help confirm or correct me on these cases.
Case1: Room just using the motion sensor to turn on/off lights. So here I could increase the Reporting Interval from 3600 seconds to several hours to save more battery right? And leave Selective Reporting Off right?
Case 2: Room using both motion and Lux to turn on lights AND adjust level. So here I need lux reading every 5 minutes, BUT only if goes from e.g. 199 to 200.
So here I would enabled Selective Reporting right? and leave the luminance Threshold to 100 (so I will get lux reporting when lux reaches steps of 100, meaning 100, 200, 300, 400 and so on), is that correct understood?
Should I leave Reporting Interval at 1 hour?
My two cents
Case 1: reporting interval 3600, selective reporting YES, thresholds high
Case 2: reporting interval 5 min, selective reporting YES, lux threshold 100 (but suggest playing with this value)
When selective reporting is positive IT WILL REPORT only at that frequency AND threshold is met. For instance, lux will not be informed once it exceed threshold, but when reporting time is met AND threshold is exceed.
So for settings tresholds high for the values that I dont use, would that be like for example
Could I increase them more, or is any of them unwise to increase?
Why not increase the reporting interval from 3600 to even more, when motion is the only feature needed?
Anyone have tried that battery reported jumps around?
Yesterday it jumped between 33% and 35% and a couple of times down to 0% or 1%. And then today it jumpts between reporting 1 and 0% battery. So I dont know what to trust.
I also have a problem with this too. Brand new. Not sure if it is a hardware issue or a software issue. Not able to anything on the motion side. It is not reporting any movement in the samsung smartthings app. However the green light does come on when I step in front of it. Also the configured triggers (lights on) not working.
I wonder how to diagnose the problem.
You have probably already checked, but I’ve got to make sure. Change the motion sensitivity to 5 in the preferences and make sure they update. If the sensitivity is 0 then motion detection is off. Also, you can enable debug logging and watch the logs when the light flashes from motion to see if any reports come in.
It is set to 5. Everything else is being reported under “recently” - illuminance, humidty, temperature.
The motion sensor worked like 2 times. Then it doesn’t work anymore.
I am not sure what I need to do to reset the whole thing.
Hi, I have a problem that my sensors just stopped updating illuminance, the motion part works perfect, but a few days ago it started that it wont update illuminance / lux sensor.
Any idea what todo? Tried taking the batteries out then in. But Im not sure If I need to wait a while before adding the batteries again, a little worried it should reset the entire sensor si I need to readd and setup all my rules again.
Thanks, this device handler is amazing for battery usage compared to other device handlers ive tried, Thanks…
You can reset the sensor by holding down the button on it for 20+ seconds. You might want to try that and then re-include it.
@Fredrik I haven’t seen this on my sensors. If you want to reset the sensor without having to set up all of your rules you can either 1) reset the MultiSensor 6 out of range of the hub. If you do it within range of the hub, it will actually send a report to the hub telling it that it has been reset and the device will be removed from your account (messing up your rules). 2) use another Z-Wave controller and just do a general device exclusion on it.
Then, go to the device in the SmartThings app and do a “Replace”. Before the replace, you may want to hit refresh and configure a few times and wait a few minutes. This can help the Z-Wave controller inside of the SmartThings hub see that the device is failed. During the “Replace” process you just include the sensor like it is new. It will pair with the hub with the same Z-Wave node number and all of your automations will stay in place.
Actually i think the sensor is constantly seeing that there is motion. As I looked at your screen at the top of this thread. So essentially the blue icon is always on. So it triggers the rule one time.
I tried to set the sensitivity to 1 and also 0. But it has no effect.
Might consider returning this.
I was experiencing similar symptoms to Fredrik and cedrictang while setting up two new sensors. Mine are running firmware 1.07, usb powered, PIR set to 10 and sensitivity to 5 to try and rule out conflicts. Specifically my motion detector stays in the state it was in upon first adding it to the system.
Hey @erocm1231, I believe I was able to capture a potentially related error to setting up one of the sensors as a secure device.
error groovy.lang.MissingMethodException: No signature of method: static physicalgraph.zwave.ZwaveUtils.uint24FromBytes() is applicable for argument types: (java.util.ArrayList$SubList, java.lang.Integer) values: [[0, 0, 240, 1, 2], 0]
Possible solutions: uint24FromBytes(java.util.ArrayList, int) @ line 191
I wasn’t able to duplicate the error while setting up normally however it still didn’t update the motion state. I have tried resetting the device and adding in secure and non-secure ways.
Let me know if you have other ideas or things to try.
Additional error when editing settings
error java.lang.IndexOutOfBoundsException: toIndex = 6 @ line 191
I have had a strange experience the past couple of weeks.
I have these sensors in several rooms in my house, and have me working fine 99% of the time.
But the last couple of weeks I have tried walking in a room, and the light didn’t turn on as normal.
Then I would go into the next room and watch the sensor to see if the LED turns green = it senses motion. And no, nothing.
1 week ago I had a sensor not doing anything for 50 minutes. I tried coming back to the room watching the sensor for the green LED, and nothing. And then after 50 minutes after first incident, then it just works normal again.
So this behaviour I have seen several times now over the past 2-3 weeks on almost all sensors.
I feel the sensors take turns on “napping”.
I’m getting a bit paranoid because now I watch for the sensor every time I walk into a room, just to see if the LED turns green or not.
For humidity use the same method I use for my cigars-get an adjustable digital hygrometer-they’re cheap. Take a small cap from a prescription vial or similar and fill it with salt. Moisten the salt until damp, but not watery. Place the hygrometer and cap in an airtight baggy for 8 hours. This will achieve humidity of 75%. Adjust the hygrometer as needed and your set.
Thanks for this great code.
Right now I am using this excellent device to measure the illuminance level.
Is there a way to change the default viewed attribute from temperature to illuminance?
Is this something that could be configurable moving forward?
Do you mean on the main tile? You can probably accomplish this by editing the code, but there isn’t a way to have it be an option. Right now device handler layouts are not dynamic. SmartThings used to let you choose which measurement was displayed in the main device list, but that was in their version 1 app.