IndigoSam wrote:I wouldn't poll the multi sensor for current lux, it should raise a lux change event when it does change and you can build a trigger on this event. You may also want to stop trying to raise the light percentage once you are at 100%, purely to reduce network traffic.
I think I'd go with polling myself...then you determine how many times an hour it talks. I don't know how "talkative" that sensor can be with updates, but if you go on a change in the lux value, then you could potentially make a very noisy network if a fast moving cloud bank comes in. I see it possibly happening like this-
- Code: Select all
Sensor: Hey its darker
Indigo: I fixed it
Sensor: It's lighter
Indigo: I fixed it
Sensor: I'm darker again
Indigo: I fixed it
Sensor: I'm lighter again
Indigo: I fixed it.
And so on...unless you have some ideas for smoothing out the logic. I'm always open to new ideas and things folks have learned.
I know some of my rooms can vary brightness multiple times per minute based on cloud coverage alternating with sunlight, time of day and shadows from the trees outside the windows swaying in the wind, etc.
With polling you could say every 5 minutes to check and then you know there's only 12 events per hour or so...