@jshimota Any ideas? One of my temp sensors is showing this in logs. It's only on one of 3 that I have using your driver.
I suspect I know what that is @jkudave - as the driver evolved and I kept optimizing it, there was a scheduled task in the driver for the healthcheck. I originally used the HE method of ping/pong - then moved past that. I think your driver had the health check scheduled and a driver update didn't remove it.
Couple of ways to clear that - have you ever done the 'device' driver clear method? changing the driver to 'device'. save. then button mash, then put the driver back. that works every time.
I left 'reset driver' button on the gui, but I just tried it and I can't tell if it removed the scheduled task. You are definitely on 1.1.21 version? I thought I left behind a clearing component just for this issue, it is supposed to clear scheduled tasks when you update the driver. so - check preferences, then save. then push reset driver, then confgure then refresh. Then look at scheduled Jobs and it should look like this:
Yes.
That seems to have worked:
Would your driver address the spamming of the logs for lux value on the nightlight?
My nightlight /motion sensor spams the logs dozens of times a minute with varius lux settings and the lux sensor registers changing light.
it does. very nicely. 
Heres 2 screencaps.
I let the user decide how they want to handle lux logging. thats where the chattiness comes from. By setting a value you like from 5-500 (incrementally), you decide how often the lux change should report. I use my sendIfChanged code that I've standardized all my drivers on to minimize duplication. I looked in on this driver - decided I could go further and put hardware reporting control in the prefs as well. It's working really nicely here in my office!
Last nights 'quick' addition of the hardware reporting has really impacted this driver. I had the settings on defaults (25 for soft threshold and 5 for hardware threshold) and I was barely getting anything back at all. I am now doing more testing on this really cool hardware reporting threshold value - The default values are overly aggressive and its impact has been noticed - I'm running tests this AM in real-world values. The driver is stable and works as designed, but I may need to tweak the defaults - if you load this driver, set both hardware and software thresholds to Maximum initially and tweak it down from there! (Tweak hardware first - just going from 1 to 5 cut out 50 events in 30 mins )
I'm pleased with my driver functionality for the night light. Even setting the driver to it's highest values (1 and 1 for hardware and software) gives a really nice log curve :).
A great test - shine a flashlight at it!