@kkossev knows best, but some of these devices are just chatty and can't be made to shut up. I assume you looked through the first post in this topic where he talks about all the devices he has information on and offers recommendations for the ones he feels are good to put in your home?
There may or may not be a way to make the devices you purchased less chatty, but in some cases they are just "bad actors" and can't be used w/out running into issues.
Probably the best approach will be if you pair the 5 chatty mmWave sensors to a second C-7 or C-5 hub and bring the motion active/inactive status to your main automation hub via Hub Mesh.
There is nothing that can be done to reduce the Zigbee radio overload from a driver side. The same chatiness problems are present and reported many times in Home Assistant / Z2M forums as well.
Unfortunately, integration these devices via a Matter Bridge is not available at the moment. This model is not exported by the manufacturer as a bridged device (the Linptech sensor is bridged however!)
I had missed this somehow. Thanks for the reminder.
The top 3 devices are Linptech mmwave devices after 3 days of uptime. The busiest area is the kitchen. The difference is that I covered the lux sensor on the kitchen Linptech.
Thanks for the reply. Yes I did, so I intentionally ordered the ones that are recommended.
As you have 8 of these radars, you may want to consider purchasing a dedicated Tuya Matter Hub/bridge for these?
I have the USB-C version, model: ZG-205Z and it works with the Tuya Zemismart Matter Bridge.
So the Tuya Hub can be bridged with Hubitat? I haven't searched the forum to read about that!
I appreciate you jumping in. Thanks for all your work on these device drivers. You put out some great work! I have my old C7 hub to do your suggestion.
I am really new to bridging so just to help me understand a little better, using the second hub will just isolate the chatty devices on their own to not bring down primary Zigbee network on the C8 Hub. But I will still have the problem of the C7 hub crashing from having 8 of these running?
Also what exactly does it mean when you say the Linptech sensor is bridged device? If I change out to Linptech there is a better advantage? And how would a Matter Bridge do it better than using the C7?
ok got the linptech (obviously not an english speaker who named the co)
anyway much better than the previous in terms of zigbee traffic about 3 messages per minute when not in the room (instead of 2 per 5 sec)
off the 3
1 is the I am alive message
1 is a bogus no motion report.. not sure why they need that every minute.. i am alive shoudl be enough.
the third i am not sure what it is maybe @kkossev can chime in. nothing comes out with debugging on and i would have to modify the driver to get to the bottom of it..
also how do i update the fw on this.. Do i need the toyu hub? is this the latest firmware?
Good to know. It seems your is similar to mine but you haven't had any Zigbee radio OFFLINE incidents yet with only 3 of the devices.
Firmware update available, but just enables LED control. Update requires a Tuya hub or whatever equivalent Chinese hub these things "normally" pair too.
only one first i am testing.
will probably get another as i am happy with performance..will give it a week or two to see if things change or it drops offline. maybe ill get it now and send it back before installing if the other starts acting up (the 10% off for a total on amazon 27 bucks seems to be a good deal) i dont trust alli much anymore as my account is locked now anyway as i had to file a chargeback with paypal. when an item said it was shipped, but link went nowhere and they denied my complaint.
added it to my zigbee externder offline rule..
ie
Just another data point for capacity ...
On one C-8 Pro, I'm running 8 Linptechs and 6 Tuya 2AAELWXK with another 100+ Zigbee devices (and 30+ ZWave devices). I'm not having any issues with the Zigbee network or CPU. That's with full illuminance reporting, as I have not yet taped over the light sensors and my attempts to "zdo unbind" the 0x400 illuminance communication have failed.
On a different C-8 Pro, I'm running 3 Tuya "flat" 24G and 1 Tuya "flat" spammy 5.8G. No issues now. However, when I earlier tried 4 of the spammy 5.8G, the Zigbee network became unusable.
Mine was after 36 hours since the last reboot. How many hours was your hub running when you posted the details?
I don't remember exactly but it was only a few days max if even that. Today I am down again and requiring another reboot. I need to move up the priority of moving these spammy devices over to another spare C7 hub
Is the distance report accurate at the time when a motion is detected?
Do you mean the distance report that follows immediately after the motion is changed from inactive to active?
No.i have dist reports disabled as i dont want them every sec. But woukd like limited dist report only when motion detected.
@kkossev,
Are you able to add the device below to this driver please?
Currently using Linptech profile for motion, all other settings were configured in the Tuya app first.
Device pairing info
Manufacturer: _TZE204_muvkrjr5
Endpoint 01 application: 4A
Endpoint 01 endpointId: 01
Endpoint 01 idAsInt: 1
Endpoint 01 inClusters: 0004,0005,EF00,0000
Endpoint 01 initialized: true
Endpoint 01 manufacturer: _TZE204_muvkrjr5
Endpoint 01 model: TS0601
Endpoint 01 outClusters: 0019,000A
Endpoint 01 profileId: 0104
Endpoint 01 stage: 4
Thanks again
@iEnam I have a better idea - instead of adding just another new mmWave sensor to this driver myself, it will be better to put my efforts in documenting the driver and providing examples how to add support for new Tuya sensors yourself.
No Groovy coding knowledge is needed—just copy an existing template ('device profile''), test and analyze the results, and modify the template inside the driver code.
When I am ready, I will create a new thread where we can try together to make this new mmWave sensor working, using a new device profile in this driver,
There are some complications - it is not possible to add more new 'Device Profiles' in the driver, as now there are too many device profiles and the attempt to add new profiles results in an error that this driver has exceeded the maximum size of a static object allowed in HE ... 
I will need to do some more complex refactoring, or to re-think whether it is not a better idea to make a new driver for the mmWave sensors only, and leave the 4-in-1 driver for PIR sensors only.
As I will be rather busy at work in the next 10 days, I expect a new version to be available no sooner than two weeks from now.
Download the Hubitat app
