Hue sensors setting

[zguy]

Having some issues with the Philips Hue motion sensors and need to better understand the available settings in the JowiHue page, their respective values and how to make sure those settings reach the device.

Lets look at a particular sensor, a Philips SML001 that includes motion, temperature and lumen sensors:



For this type of sensor, I get 2 settings and a LED control for the motion sensor and 1 setting for the temperature sensor:

Motion settings:



Temperature settings:


My understanding of the "Delay nomotion after motion ends" is that the value express the amount of time, in minutes, for the sensor to report no movement back to the plugin after the movement has stopped. I don't remember the initial value. When I initially installed it, I set it to 2, assuming 2 minutes. That value was not enough so I tried to set it to 5, again assuming minutes. The setting doesn't seem to have reached the device, except for the LED setting.

To set this up, I made sure to wake up the device before saving the value in HS. Yet, I'm not seeing the change of behaviour of the sensor although the LED setting seems to have made it thru.. It does flick once in a while when movement starts. but that is not consistent. At this point, the behaviour is after about 1 minute it will report new movement. What am I doing wrong?

For the "Sensitivity motion", the page indicate a value of 0 to 2 is required. I'm assuming 0 is the most sensitive and 2 the least. Is that correct?

For the "Correction temperature value", what is the range, single digit or with a decimal, and can we input a negative value?

And finally, how to make sure these values reach the device?

[w.vuyk]

The motion delay is is seconds, not minutes, so if you want 5 minutes delays, it should be 300 seconds. But I have had issue with false triggering when it was set high, never really could point it out, but this could be some bug in deCONZ there. I have worked around it by putting these timings in the event by adding a condition (cannot be a trigger anymore) "has been Motion/NoMotion for at least" to the events. That did not yet dissapoint me

The sensitivity depends on the type of motion sensor. In the case of Hue 2 is high sensitivity and 0 is low (I know, it is confusing!)
Here is what the deCONZ documentation says:

sensitivity

Number

Device specific sensitivity, with following supported values. Philips Hue motion sensor: 0 = low 1 = medium 2 = high Xiaomi vibration sensor: 21 = low 11 = medium 1 = high

Once you have set the value, you should see the change in the JSON on the same page after a refresh. It could take some time before it reports the change as the device needs to wake up (motion, temperature change, lightlevel change or a report is send). After the wake up, the new value is accepted. deCONZ takes care the correction is saved when the wake up happens. No worries on your side for that

The correction temperature is using the local decimal setting, in your case the dot I believe? And indeed you can give negative numbers.

[zguy]

The motion delay is is seconds, not minutes, so if you want 5 minutes delays, it should be 300 seconds. But I have had issue with false triggering when it was set high, never really could point it out, but this could be some bug in deCONZ there. I have worked around it by putting these timings in the event by adding a condition (cannot be a trigger anymore) "has been Motion/NoMotion for at least" to the events. That did not yet dissapoint me

Seconds, ok, got it. 1 order of magnitude, no wonder it didn't work as expected.

What range of values did you have issues with? If it's way more than 300, I probably won't need extra conditions.

I didn't see that "has been Motion/NoMotion for at least". Options I have are:

[w.vuyk]

You should select the nomotion there. On the bottom you can set the time...


Once you save this, you will see the text I mentioned "has been Motion/NoMotion for at least 9 minutes"