That is a possibility. It is strange that my 3 works correctly and yours do not. It is almost like a setting or something in the sensor itself. I attached the log of my family room. You can see someone was in there this evening, light came on, lux went up, light off, lux to zero. Then when I got home I cycled it a couple times in and out. Yes it is really dark in there so when the lights go out zero lux is expected.
Same...normally mine area set to only report lux at 500 lumens change, so I don't get any info logging reports.
Changed it to report on 25 lumen change and I got reports. Only tested on one sensor, and using the Linptech-specific community driver.
1 Like
Linptech specific community driver? Mine is set at 10 which is what the driver was set to.
From here...
Driver is available in HPM. Search Linptech.
GitHub download is here if you prefer.
Oh..., so "Lux Threshold" is lux sensitivity? That is really badly labeled. Mine was defaulted to 65,000 when I changed drivers - I took this to be the Max to report, ie, an actual threshold for max reported value, not a change needed to report. Given it had such a high default value.
So first one I set to "1" started reporting changes.
1 Like
Yes, sets the amount of change in lux required to be considered significant enough to report, and potentially be acted on in automations. Not uncommon use around here.
"1" sounds be pretty low (resulting in lots of log activity etc) -- nothing wrong with letting that ride for a while to get a feel for how it's reporting in your environment, but I'd plan to reassess that setting sooner or later.
As with any device's reporting options, setting the thresholds and intervals to the least spammy/noisy values that still meet your needs helps keep your hub running smooth and happy.
1 Like
I tend to always use HPM for the ease. I looked up the driver. Another Krassimir driver so I know it is excellent. If I start having issues with what I use I will switch over.
Both drivers should work fine, I would expect little difference in device behavior, main differences being available settings/configuration options. I've pretty much only used the Linptech specific driver since it was created. Either is a good choice. 
When you get a chance if you don't mind could you screenshot your preference page for that specific driver?
@danabw -- Are you using gassgs's stripped-down version of the Krassimir mmW 4-1 driver, or Krassimir's mmW 4-1 driver?
@LearningHubitat -- there are 3 Linptech drivers (that I know of 
) - native, Krassimir mmW 4-1, and gassgs. I'm using Krassimir's mmW 4-1.
Edit -- I forgot K's mmW driver is now separate from his 4-1 driver
1 Like
I use the 4 in 1 driver for my motion sensors. The Tuya Zigbee MMWave Driver for my Linptech/Moe's sensors. The one @danabw was talking about as you stated is K's driver that he pulled out to be specific for the Linptech ES1.
I'm using the version of Gassg'sdriver that Kkossev put in HPM. 
Hi guys,
My device (white label 'MOES', TS0225 _TZ3218_awarhusb Tuya Version
1.0.6) seems to be sending the illuminance reports as expected:
I am swamped these days, but hopefully, I will have the chance to research the possible reason(s) that illuminance reporting is not working in other environments.
1 Like
Yes, that was just a test value to make see a change. However, in the rooms that drive lights to a light level, I will need something close to 1 for small changes. Looks like I can get rid of my Fibaro indoor light sensors and just use these now. It won't generate any more activity than the Fibaro has been doing, which is using a 1 lux change.
