Got my new Zooz 4-1 in today. Paired up right away, getting a reported Lux of 2.95, however I am seeing this error in the log when I turn on another light to increase the lux based on my Simple Lighting Rule and the target light is not being turned off
And why this message? Is being asleep an issue? The only way so far to wake it up that I have found is to use a paper clip and press the reset button (also indicated in the log file)
Rick,
After you paired the device did you hit the 'configure' button?
This sets up all the parameters from the driver so, if you didn't, then you may not have the correct configuration on the device.
I have several of these sensors, you do have to wake up the device using a paperclip in the hole before the configuration will complete. You probably could wait until the device does its automatic wake-up (every 12 hours?), but I didn't. I sometimes had to wake it up several times before everything would take. After getting the configuration done, they have been working great.
I went ahead and excluded the device and re-added it to be sure and to hopefully clear up the error in the log file, selected configure, woke it up and it's reporting all values
So now to test
Illuminance is 3.88
I have a simple lighting rule set to turn off a light when illuminance is >= to 3.9
Turn on said light, nothing happens
Looks like you might be right. I removed the simple lighting rule, created a RM Rule and now it works.
Now my question is, it took nearly 90 seconds for the lux to be registered on the device before the RM Rule would fire. Is there any way to get the device to sense change quicker than 90 seconds?
The way i'm testing is just by placing my hand over the sensor so the lux is going from like 40 to .013
Does it have to do with the Light Change Trigger setting in the device driver? It's currently set to the 10% default setting. Is there a location where I can read up on the different settings that make sense to a non-programmer
The zooz only updates the illum every 3+ minutes, never right away, so you can trigger off of it, but it will only update when it does its next scheduled update, unlike motion which it does automatically.
We should let @bravenel know about the bug in simple lighting.
Hey again, can you further explain what you mean by "trigger" off it? I'm hung up on the definition of trigger when we can trigger off of motion, so what is different with lux?
Motion sends a message to the hub as soon as it happens, lux is on a periodic update message every 3-4 minutes and only if lux changes enough to report it. So motion changes are reported immediately, lux whenever the next update is sent out.
So is this where the light change trigger value comes into play? I'm guessing...
Lux reported at 7:11am as being 11.1, then not again until 7:25 as being 14.45. My trigger value is still at the default 10%. My guess is, during the 15 mins between the 2 reporting, the change in lux was not greater than 10% so therefore it didn't report. Am I on track?
