Which version firmware are you using? Mine reports every 5 minutes @ 1 lux setting (of course only if there is a level change - I assume the level change is is only measured as at the end of the period and any fluctuations in the interim are ignored).
Hm, I'm not sure. Is there a way to see on Hubitat? I don't have a Hue bridge.
I did just buy this a couple of weeks ago, so hopefully it's on the latest firmware, but I guess there's no guarantees.
Unfortunately you'll need a hue bridge to pair it to, in order to do that as well as update the firmware. It was released in 2019 but I checked one of my outdoor sensors last week (bought this year) and it was still on the old one. I would imagine yours should be a new version but who knows how long it's been on the shelves.
Yes. I did it. Use the driver "Device", put it through it's paces, and look at the log. It'll give you a 'software firmware' version, or something like that.
I meant, "device.
1 Like
Ah, looks like I am on the older firmware version.
trace Software Build Id:6.1.0.18912
Oh well, at least I know my workaround (of setting log10) seems to work well enough!
I'm doing any intensive lux stuff, but I just shined my flashlight at the Hue on the fireplace mantle, and it changed lux in 5 minutes (maybe a little less?) with motion not active. This is on the old software. I haven't found anything different, but there must be something, I imagine.
edit: I just got 2.5 minutes on the old firmware.
I ended up buying a Hue Hub because there was a sale on a Hue bundle, so I'll be looking to update my motion sensor's firmware.
Did you have to remove the motion sensor from Hubitat first? Or were you just able to pair it with the Hue hub, update the firmware, and then repair with Hubitat?
This.
I wasn't able to re-pair the sensor with my Hubitat after pairing and updating the firmware on the Hue hub.
I ended up having to remove the motion sensor from Hubitat and then it let me re-pair it.
That's strange - have done it a couple of times without issue.
After updating my motion sensor's firmware to 6.1.1.27575, which is the latest, the lux still isn't reported consistently when I have the Lux Reporting set to "On 1 lux change". It would take hours for the lux to update.
Here's report from 11:43 AM.
I noticed the clouds rolled in around 2 and went to go check on the lux value and it hadn't updated. So I refreshed manually:
28 Lux difference. Yet "On 1 lux change" didn't pick up any transition in between the 2.5 hours...weird.
Sun came out again 5 minutes later. I waited for the sensor to update, but nothing. Manually refreshed and saw it increase by 16.
I wonder if this is a Hubitat bug. Is on 1 Lux accidentally actually set to like on 25 Lux change or something? 
I switched back to "log10 precision 3" and reports are back to normal (changes reported every 5 min)! 
1 Like
Now I have to figure out what that means!
It's giving you the same lux result as without the log thing?
Instead of using "On 1 lux change" I'm using "log10 precision 3". It's another option under the lux reporting drop-down. See this post for more details.
When I use "On 1 lux change" the lux value doesn't change every 5 minutes as I'd expect it to. Whereas if I use "log10 precision 3" it does change every 5 minutes.
I'm using precision 3 because the highest lux I've seen inside my house is around 75. I believe the lower log precisions are for situations where you'll have higher lux values).
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
