Maybe it's a Tuya sensor and a switch that I've used.
The switch is unlikely to have a significant impact on the data section.
Next time I'll take a close look.
Hi @Kaitlyn ,
I don't own this sensor, so I can't say for sure. Typically, these motion sensors report the illuminance only a few hundred milliseconds before the 'motion active' event, as the purpose is the automation rules to decide whether to turn the lights on based on the illuminance value ... This is not a dedicated lux sensor.
But you see that @user3874 in the other thread says that this device reports periodically the illuminance... With Tuya devices everything is possible! : )
He's not at home right now, and it happened on a device at home.
Only some of the devices occurred, and unlike yesterday's me, it only occurred in wall-type products, not ceiling-type products.
What I have in common with my case yesterday is that it only occurred on some devices after the HPM update.
I talked to him.
If possible, please let the developer know the details of the problem.
If there is a problem with the driver, there should be a problem even after re-registration.
But there is no problem after re-registration.
Perhaps, it seems to be an HPM update issue.
Thanks for the information!
I am pretty sure that the problem is not in this HPM version update. Any update, manually or from HPM to any version of this driver will reveal the same problem, if the device manufacturer does r model data is missing. The core of the problem is this mysterious deletion of Data values, that I am trying to find when and why happens sometimes for some devices.
The latest version 1.2.1 supports also the SonOff ms01 ( eWeLink) motion sensor.
This device has a hardcoded 60 seconds motion reporting time, it is not configurable.
Pay attention on the batteries, if the battery goes below 2.95V it starts playing weirdly.
I've got rid of one of the cheap TS0601 sensors (_TZE200_3towulqd) as it kept giving issues, the other one works without any issues.
Also, I've got one sonoff sensor (eWeLink/MS01), which seems to go offline every morning just after 7am, but comes back online once motion is detected, although 3 other sonoff sensors seem to have no issues, weird.
Firstly great job on the driver! I have the Tuya 4 in 1 device. One question, the manual I have says itβs possible to configure the interval for automatic reports to be sent from the device for temp, humidity and luminescence. It says if you set it to zero you get real-time reports which I would like as I power the sensor via micro USB cable rather than battery. Is there any way to set this interval parameter with your driver?
Yeah that's what I ended up doing (copy/paste the driver code). I was just wondering because I've never used the HPM before and it was suggested to do so, but it didn't work. With a manual driver you won't receive any updates though. Thanks anyway.
That is because this driver is still in beta. Once this version will be released through HPMyou can do a match up from HPM and make use of it that way.
The driver has two versions - one stable (production), which is available for installation and automatic updates from HPM. The development version contains the latest device additions or code fixes, but usually, it is needed to be updated manually only for the latest reported issues or when new device support was added in the last weeks.
@concan if you already have the HPM installed, but you had this (or any other driver) installed manually, the best approach is to do a "Match Up" from HPM.
HPM will match the manually installed drivers to the drivers or applications that are in the database and will offer to select which one to be re-installed and maintained by HPM from now on.
After the "Match Up" is done, make a second run choosing HPM "Update". From this point on you will receive notifications when new stable versions are available.