HPM is showing up to date and I do have 3.3.3 best I can tell. The sensor seems to be working great now. Thank you!
1 Like
After the last update (3.3.3) a sensor that was at 77% battery it is now at 100%, but reporting 2.7v like before.
Current States
Battery
100
Battery Voltage
2.7
Health Status
online
Last Battery
Mon Feb 10 17:58:37 CET 2025
Motion
inactive
Power Source
battery
Rtt
timeout
Status
clear
State Variables
Device Profile
TS0202_MOTION_IAS_CONFIGURABLE
Driver Version
3.3.3 2025/01/29 10:06 PM (TS0202 _TZ3000_6ygjfyll) (C-7 2.4.0.151)
Health
{"checkCtr3":0}
Last Rx
{"batteryTime":1739206717167}
Last Tx
{"cmdTime":1739129201312,"pingTime":1739051545692}
Motion Started
2025-02-10 18:14:34.043
Not Present Counter
Packet ID
Rx Counter
44711
States
{"isPing":true,"isTimeoutCheck":false}
Stats
{"bVoltCtr":22,"battCtr":22,"rxCtr":277,"txCtr":25,"pingsFail":1}
Tuya DPs
{}
Tx Counter
12
Does this driver show battery voltage or percentage for an eWelink MS01 motion sensor? All I see now is this:
Pair the Sonoff MS01 sensor again, so that the battery reports are activated.
Sonoff battery-powered sensors are extremely sleepy, the most difficult ones to configure properly.
1 Like
Thanks! Time to get my ladder out...
Make sure you see the battery reported every 2 hours, before you climb the ladder again to mount the MS01 sensor on its final position :
Also, check the batteries - one of my two Sonoff SNZB-02 motion sensors starts to produce false motion detections when the battery percentage remaining drops below 50% ... 
1 Like
Thanks for the tips! I’ll be changing the battery no matter what, since I have to go through the effort of getting to the sensor unit.
All is good with both the old (MS01) and new Sonoff sensors! Thank you again for the great work!
1 Like
1 Like
Manually set the device profile to 'Tuya TS0202 Motion Sensor (IAS)' and click Save.
Then, pair the sensor once again to your HE hub (without deleting it).
Will it work?
1 Like
now is ok, thank you.
Is it possible to change time for restart as I see is 30s.
Hi kkossev,
Thank you for all the work you have done with these Tuya sensors.
I have a Tuya sensor that is logging a lot of messages. Can you tell me why?
Thank you!
Sensor profile:
Device Data
| Application | 93 |
|---|---|
| Manufacturer | _TZE200_kb5noeto |
| Model | TS0601 |
| Tuya Version | 2.1.3 |
Log:
This device (TS0601 _TZE200_kb5noeto) is a combined PIR+mmWave sensor, you must use the Tuya Zigbee mmWave Sensor driver.
2 Likes
Thank you!
Has anyone seen this before? For the past couple days, I have been getting this error message every hour:
For those who cannot see the screenshot--org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method:
user_driver_kkossev_Tuya_Multi_Sensor_4_In_1_1318.sendDelayedBatteryEvent() is applicable for argument types: (groovy.json.internal.LazyMap) values: [[delayed:299, descriptionText:battery is 100 % [delayed 299 seconds], ...]] (method sendDelayedBatteryEvent)
I refreshed, disabled/enabled the device, and HPM reports that it's at the current driver version.
1 Like
What is the device model/manufacturer that generates this error?
Can you correlate the start of this error with any changes made to your HE hub?
Update: I've identified the problem and will prepare a fix ASAP in the driver, thank you for reporting this issue!
1 Like
The bug is fixed in 'Tuya Multi Sensor 4 In 1' version 3.5.2, pushed for update via HPM.
1 Like
Hello, I've purchased this Tuya sensor and it immediately joined my C5 hub. Easy enough. It self assigned a device type of "device" and puked lots of this in the logs: fingerprint profileId:"0104", endpointId:"01", inClusters:"0004,0005,EF00,0000", outClusters:"0019,000A", model:"TS0601", manufacturer:"_TZE204_gkfbdvyx", controllerType: "ZGB"
So I came across this 4-in-1 driver which led me to the Tuya Zigbee mmWave Sensor driver. It took a while but after looking at the driver there was no entry for the "manufacturer":"_TZE204_gkfbdvyx" but it eventually responded to device profile Tuya mmWave Radar ZHPS01. Almost instantly it showed motion=active and I thought OK, it's just sitting here on the couch rolling around so I went and mounted it temporarily in an unoccupied office. When it reconnected to the hub the logs were still incrementing the duration of the motion being active. How could it be? So I forced it inactive in HE UI, and immediately refreshed it, back to active. It's now face-down into the carpet, under a desk, the office is empty, no fans, no windows, no curtains and I've dialed back all the distance settings to 1.0m or 1.1m (min/max), still active.
Thoughts? Any other info I can offer up?
That Manufacturer ID looks very similar to (and the device itself appears physically to be the same as) the device discussed in this post...
I suggest reading the next several posts after that one (the follow-up discussion between Krassimir and Kulfsson)
This thread is for Krassimir's 4-in-1 PIR driver -- that other thread is for Krassimir's mmW sensor driver.
2 Likes
What driver should I be using if my 4 in 1 device has a mmwave sensor in it as the mmwave driver doesn't give temperature and humidity readings.
