I am not able to get illuminance to update at any regular interval (regardless of how granular I set the Lux reporting/change reporting to be) on Fibaro Z-wave motion sensor, Aeotec Multisensor 6, or the Hue (indoor) Motion Sensor. They all work initially, but never over the long term. I'm trying to create rules to set lighting levels, but cannot because the reporting is never consistent (I don't even care if it is accurate, just as long as it is consistent). Does anybody have these sensors working and/or know what might be the issue with reporting of Lux?
There are some that only report when the value changes by a certain amount since the last report (rather than at set intervals) and some don't notice if there is just a quick flash of light, only if the change lasts a while. I don't know if that applies to the ones you mentioned? Are they located in places where you'd not expect much fluctuation?
After further testing, there is just no consistency in any or all of the sensors. The one that "now works" and reports illuminance with consistency is the Fibaro Motion Sensor (Z-Wave). The Aeotec Multisensor 6 is "stuck" at an illuminance of 1 regardless of lighting conditions.
The location I chose is one where there are not large variations or flashes of light (ever). It is in a "protected" hallway where the changes in illuminance really depend on time of day and the light settings themselves. The sensors are not exposed to windows or other light sources where a light source would suddenly or rapidly change the ambient lighting.
This problem goes even deeper in that rules I've installed don't work properly. The logs show an illuminance of X and yet the rules I create to raise the lighting levels to Y don't "engage."
I'm not sure if this is an "upgrade and legacy" thing or what the deal is. But, ever since 2.2.6 or 2.2.8, basic on/off rules (based upon time of day) and a few others don't work consistently.
