Change the lighting (cover the illuminance sensor by hand) at the time when you click on the 'Save Preferences' button so that the sleepy device wakes up and accepts the reporting parameters.
EDIT: Got it in there now. We'll see. Nice fine tuning features. Appreciate your efforts.
Not to burden this thread...but if I set the illumin reporting threshold to 50 should I be seeing this frequency in the Events stack? Something necessary to have it take effect?
50 is not a Lux unit, but some kind of relative number that can not be converted into Lux. Thats why the hint is 'bigger values will result in less frequent reporting'
Hello @kkossev I am sorry if i am bothering you. I bought the light sensor you listed above on Amazon Canada, found this thread and a couple of others that you posted a driver for and i installed it and as @Pradeep suggested to set it to TS0601_AUBESS and he got his working, but min is not. I did match the driver to HPM and it is updated to the August 24 version, but its not sending any lux info to my apps
Ok that seems to have done the trick. it took 5 tries of the 'double tap' method it didn't work from 2 feet away but when i put it within 2 inches it seemed to take right away. Each time it had to select the TS0601_AUBESS to see any change's in the device descriptions. But in the end your magic worked and every seems as it should be. Thank you very much for your help, time and efforts and very fast reply
ok, i have another question. I've seen comments that these are chatty, but i had no idea they were this chatty. it looks like every half second its reporting. is there a way to change this or just switch to another device like the Aqara one that was suggested? I did read something somewhere about changing the sensitivity somewhere but i am not seeing that setting. thanks again
I just edited post#8 to warn about this device's chattiness.
I don't have this device, so I have not experienced its behavior myself.
TS0601_TZE200_khx7nnka fingerprint is actually not included in the Tuya driver, selecting the “TS0601_AUBESS” in the “Model Group” is a workaround / random match of the data points with another device.
Let me check if I can do anything to reduce the frequency of the events rate in the driver.
I will also look for an alternative light sensor.
The only one configurable Light/Illuminance sensor that I know is the Aqara T1 Light Sensor.
Thank you again.. I'll gladly play guinea pig with this device if you want me to try out changes for you.. I did put the aqara T1 in my basket but I haven't ordered yet in case you are able to work some more magic.. 8 also saw a MOES zigbee light sensor but I'm not finding any drivers.. I have several Moes buttons that I like. Back when I got in this rabbit hole a saw the one I got on Amazon and your suggesting it is thought id try that route.. I have a few other light sensors but they are all part of multi devices which I don't need in the kitchen or the price if I can get away with it.. lol
OK, let's not give up that easy... : )
I remembered that I started a new dedicated Tuya Light Sensors driver a year ago but didn't publish it. Next week I will try to find the time to finish it, it has all the neccesery software filters that will undoubtedly reduce the CPU load. Meanwhile, you can collect some statistics on how much chatty this Tuya sensor is. There are at least two ways to check:
Settings -> Zigbee Details -> sort by Msgs column. Here is an example of a very chatty device:
These count statistics are correct and are reset on every reboot of the HE hub.
MOES is just a white-label reseller company. They sell gadgets based on TuyaOS, actually designed and engineered by other unknown manufacturers in China. For me it doesn't matter what label is printed on these products; it doesn't matter whether they are purchased from AliExpress or from Amazon - they have one and the same origin...
Just for the record here Is a screenshot of the activity of the device.. the hub was restarted this morning and I only got the device working properly around 5 hours ago
Maybe I'll order a MOES, they are a little cheaper, just for fun as well.. how would I go about seeing the device information on it.. put in the same driver and see what comes up?
Hello @kkossev, not sure where the time has gone but it feels like summer has vanished. I hope you had a good one.
You at one time mentioned playing with an old driver for the light sensor and I'm wondering if I messed a message or you are still interested in letting me test it for you.. I'll attach a screen shot, the numbers for the sensor is about a week old because of the last hub update. But it still uses a lot of resources
Hi @xbox442, sorry, I haven't had the time to look deeper into this sensor, but typically, Tuya devices reporting intervals are not configurable, so the chances of making it less chatty are close to zero.
It may be better to look for an alternative solution.