Yes, the main issue has been solved. There is still an issue with keeping settings persistent. But motion detection works fine with 3.4.0 version
1 Like
Would you mind just sending me a link to where I can get there working version so far? I only found 3.3.3
Hubitat Package Manager is easiest - see first post for more information.
1 Like
Hey @kkossev ,
I noticed on the GitHub forum you shared with me a while back that they’ve been discussing the possibility of applying custom firmware to address the spamming issue with these devices. I believe this is the chattiness you were referring to. Would this firmware fix that issue for the devices mentioned above?
If so, as Hubitat users, how can we find and apply the custom firmware? This isn’t something I’m familiar with, so I’d appreciate any instructions or links to help guide me through the process.
Thanks in advance for your help!
thanks for your help I got it working now using (Tuya Motion Sensor and Scene Switch) it works well but doesn't report any lux levels, I have tried all the other profiles with no luck, am I missing somthing?
Unfortunately, I don't use that device - I have a Linptech mmW sensor that I use this driver for, so my experience is limited to the Linptech.
There are instructions on how to change the firmware of the spammy Tuya mmWave sensors in the link below, however, this is not an OTA (over-the-air) update. The process involves opening the devices, soldering connectors , using a JTAG programmers, etc... 
2 Likes
Well, I guess I have my work cut out for me then. Thanks for the link
1 Like
@kkossev
I'm not sure if I'm just realizing this now, but does anyone else notice that it takes a really long time before the sensor goes back to Inactive? It seems to be stuck to the "small" human motion forever. I have Presence keep time set to 20 seconds. Debug logging doesn’t seem to point anything.
Device Profile: TS0601_24GHZ_PIR_RADAR
Driver Version: 3.5.1 2025/04/25 10:29 PM (TS0601 _TZE200_kb5noeto) (C-8 2.4.1.157)
P.S. No one has been in or near the room since that last “small” motion. Not sure why it’s taking forever to become “Inactive” again. The sensor isn’t facing towards where we are and we are at least 2 rooms over.
Does Linptech have battery operated mmWave sensors? I think my Tuya is a dud It keeps getting stuck in “small motion” so my lights won’t turn off. I used to have a plug in one but the wires looked ugly so I wanted a wireless one.
Not to my knowledge. I'm very admittedly not keeping up on mmW developments, but I'm not aware of any battery mmW-only (i.e. no PIR component) devices.
It appears as though they do exist.
But my guess is a battery powered version of a mmWave sensor has to make some kind of trade-off(s) to balance features/functionality with acceptable battery life.
1 Like
Oh… how is mmWave only vs mmWave with PIR different? Do they not do the same thing? I really just need it to make sure it doesn’t shut the lights on me when I’m taking a bubble bath 
There are some combo PIR/mmW units that can run off battery only -- then the mmW can sleep until PIR wakes it up, so that's apparently enough of a power savings that battery-only can work.
I have no clue how well that setup works (performance-wise or in terms of battery life), but such devices are out there.
The fact that no battery-only mmW-only devices exist seems to imply that standalone mmW's too power hungry. If you were to find such a device, I'd expect its battery life to be pretty terrible.
Edit -- oops, I guess 3R has one these days... They normally do a nice job with battery life, so maybe they cracked that nut.
I'm confused why there is even a need for an mmW-only battery device though. I feel as though PIR + mmWave (in theory) should be good enough. Unless you teleported in and out of a room, you would probably always trigger a big motion. Then, the mmWave can kick in check for small motion.
But, of course, I don't know anything because I can't get my battery-operated PIR+mmWave to work properly so maybe I should try an mmWave-only one and see how that works lol. It just stays active in small motion indefinitely it seems...
Hi!
Is this device already supported? When I added to Hubitat it was added as "Device". Motion detection doesn't seem to work. Any help would be appreciated 
Zigbee parsed:[raw:D64901000030DFFF42140D000000650E00000012CF00000065D000000012, dni:D649, endpoint:01, cluster:0000, size:30, attrId:FFDF, encoding:42, command:0A, value: eÏeÐ, clusterInt:0, attrInt:65503]
fingerprint profileId:"0104", endpointId:"01", inClusters:"0004,0005,EF00,0000,ED00", outClusters:"0019,000A", model:"TS0601", manufacturer:"_TZE284_iadro9bf", controllerType: "ZGB"
This is a new device, not in the driver internal list.
Have you tried to manually select some of the existing device profiles from the Preferences tab?
I tried some of them (not all) but the detection seems to be inversed. Is there any other thing I could try?
I checked the posts about this device on GitHub, and they confirm that the 'presence' reporting is inverted. At this time, I couldn't find a final Z2M well-working converter.
... While searching, I came across this post from an AliExpress seller....
If your device works partially with the first Device Profile, you could still try to use it. Create a virtual motion sensor device, and invert the motion attribute using RM5 rules. (when the real Tuya device reports motion active -> set the virtual motion device inactive, etc,,,,).
Unfortunately, this driver can not be expanded further with new mmWave Device Profiles, as the driver has reached the maximum allowed single structure static data size.
2 Likes
Thanks, I will do that then. Are you planning to add support somehow to new devices in the future? I just found out some more information about the device. It seems to need more tweaking to have it working completly: Missing support for Human presence sensor _TZE284_iadro9bf · Issue #8939 · Koenkk/zigbee-herdsman-converters · GitHub
