I have a couple of the Hue Motion Sensors and the Hubitat driver is generally solid as a rock, especially appreciate the log10x precision sensitivity levels (thank you @MikeMaxwell) but it will only ever report lux once every 10 minutes with no option to change that.
Where I live is really awkward for light, a passing cloud and some of the rooms darken to the point of needing to turn on the lights! The 10-minute reporting is really difficult for that.
Is it possible to include an option for more frequent reports? Or a change in light level that would force a report?
Or does anyone know of a custom driver with that option?
I just tried this, and it seems to work:
Temperature reporting interval on the driver goes down to 5 minutes.
I changed it to 5 minutes, and lux reporting interval also goes to 5 minutes.
Interesting on the temp reporting affecting the lux reporting time. I'll have to try that
You can think of the log precision as lux "changes by % of current value" - the more precision, the smaller the %. If you used 1 lux in a generally bright room, the sensor will always report a change (ie. 2073 becomes 2081) - if you think, only tell me if it changes 10%. Then it wouldn't. But would still capture lux changing from 10 to 9.
I like that, much more relevant. But it's still limited to reporting the change no more often than by that hidden time value.
Last night, when I experimented with 5 minutes setting on temp change causing the lux to report at 5 minute intervals, I couldn't get it back to reporting lux at 10 minute intervals, lol. It sorted itself out overnight. Sometimes I think most Zigbee devices have a mind of their own.
I can at least confirm that setting the temp setting to 5 minutes brought the lux update back to 5 minutes. Something is not right. I started looking at it myself as I use it for lux readings. For some reason it is not updating lux while it was active.
5 minutes is probably as quick as it will report lux and temp changes since it is designed for the Hue bridge and Hue not wanting to overwhelm the bridge with lux readings. The Tuya mmwave sensor comes to mind as I duct taped the lux sensor on mine and stopped hundreds of lux reports per hour from being sent. As Iām typing this I realize that the Tuya sensor may be just the thing for your situation
For some reason now it's pretty much working as I want it too - with a caveat or two.
But having changed it to the Temp Report every 5 minutes, and then back to a more useful (for me) Report on 0.5C change, I get reports every 5 mins from both the illuminance and temperature sensors if there's been a change - which is perfect for me..
The caveat is it wasn't enough for me where it was originally - the landing between the stairs, bathroom, and bedrooms. For that, I gave up - 5 mins is just not useful enough.
So I got an Aqara P1 - which solves that particular problem because it takes a lux reading when it detects motion and reports the lux before reporting motion active. Only when it detects motion, which is useless where I need a more passive lux reading, but perfect for that particular use-case of turning the light on if someone enters and if it's dark!
I also had to rejoin the Hue Motion Sensor to the hub - as it seemed to lose connectivity in the move, so that might have helped sort out the 5 minute readings but can't say for certain with that one. Just saying for those that are reading this with a similar query.
I have a similar 2nd floor landing situation, but there's a light in the window that's on to 11:30, so I can get by with a combo of time and sunrise. My problem involves a cat. I'll try decreasing the sensitivity on the Hue tonight.
So, as a final update on my little thread diversion, the cat did not set off the motion detector this morning. Hue motion, mounted on 8' ceiling, sensitivity on low, small cat.
