[BETA] Tuya Zigbee mmWave Sensors (code moved from the Tuya 4 In 1 driver)

Is it possible to add support for PIR + mmWave sensor, battery powered? This sensor activates mmWave only after motion is detected by PIR to save battery. I tried "Tuya Multi-Sensor 4 In 1", but looks like it sees only PIR part (plus battery and illuminance), but not mmWave part.
mmWave driver does not work at all.

  • manufacturer: _TZE200_kb5noeto
  • model: TS0601
  • softwareBuild: 0122052017
  • tuyaVersion: 2.1.1

https://www.aliexpress.us/item/3256806664768243.html

Make sure you selected "Mmwave PIR" version above, not just PIR.

4 Likes

Anybody else seeing trace entries in logs even though trace logging is disabled?

1 Like

Yes. I reported 3 hours ago (a couple messages above) and just identified what is the issue. Probably something left in by mistake.

3 Likes

Thank you for the report - yes, I forgot to remove/comment out this debug trace line in the previous version.

This is now fixed in driver version 3.1.3, pushed for updates via HPM.

2 Likes

Please update the driver manually to the development branch version 3.1.3 (link)

I had a similar device sitting in my drawer for quite a long, it is made by another manufacturer, but yours seems to be of the same type :

  • endpointId: 01
  • application: 90
  • inClusters: 0000,0003,0500,0001,0400
  • manufacturer: _TZE200_2aaelwxk
  • model: TS0601
  • softwareBuild: 0122052017
  • tuyaVersion: 2.1.0

AliExpress : (link)

I have added just another 'Device Profile' group:
image

After updating the driver, select 'LOAD ALL DEFAULTS' and click the Configure button above.

I didn't have much time to test everything, but the first tests were OK, and this battery-powered mmWave sensor seems to be working fine with my setup!

image

I will add the battery level reporting in the next update.

@iEnam If I am not wrong, you had a similar battery-powered mmWave device?

1 Like

@kkossev Thank you, it seems to be working and reporting both sensors! Yes, my device looks absolutely the same as yours.

1 Like

@kkossev,
Yes, I have this battery-powered mmWave device which I was using on the Zemismart hub.
Thanks for the new driver.

Summary

image


Unfortunately, due to poor results for "static motion" this device seems to be a good PIR sensor only which is a shame.

I have now decided to install a spare Moes radar instead where I was using this device and "occupiedTime" has been solid for the last 35 mins.

@dv1
how is your experience with static motion?

@iEnam I am playing with sensitivity and distance.. It works to some extent.. It stopped to clear (static motion -> none) at some point, I haven't figured out why yet. Overall, it seems to be that Sonoff performs better in the same room, but it is USB powered..

1 Like

Hello. I recently bought a new mmWAVE sensor as below.

The sensor I newly bought looks like old one which is working well using your Tuya Multi sensor 4 in 1.

However what I bought recently is using AC 220V even though old one is using DC 12V power.

So I tried to use your new Tuya Zigbee mmWave Sensors driver, but it was shown as unknown device in hubitat even after trying to do ' Select 'LOAD ALL DEFAULTS' from the Configure command drop-down menu and click on the configure button'.

My device info is as below.

  • endpointId: 01
  • application: 4A
  • manufacturer: _TZE204_fwondbzy
  • model: TS0601
  • tuyaVersion: 1.0.10

Please kindly checek my device information in the hubitat.

Below is the product page I purchased.
https://a.aliexpress.com/_oE0eMOQ

1 Like

This is a new manufacturer code - no any info for it in GitHub.. : (

Manually assign the first Device Profile from the list (ZY-M100) :
image

Most of the 'Data Points' are matching, so I suppose the new device will work with this profile.
Let me know the result, if OK - I will add the new manufacturer ID in the next update.

1 Like

Dear Kkossev.
Thanks for your quick feedback.

It works well after following your advice and really appreciate it.

  • endpointId: 01
  • application: 4A
  • manufacturer: _TZE204_fwondbzy
  • model: TS0601
  • tuyaVersion: 1.0.10

1 Like

Changing to this driver with the Tuya radar sensor, how do I stop the settings values appearing in the Events history every few seconds?

Please post a screenshot of what you see in the logs. And what is your radar model/manufacturer - is it the Sonoff ?

1 Like

TS0601_TUYA_RADAR

Summary
detectionDelay 0.1 seconds detectionDelay is 0.1 seconds physical Boat Motion 5/17/2024 3:00:56.674 pm
minimumDistance 0.2 meters minimumDistance is 0.2 meters physical Boat Motion 5/17/2024 3:00:56.628 pm
radarSensitivity 6 radarSensitivity is 6 physical Boat Motion 5/17/2024 3:00:56.583 pm
maximumDistance 5.0 meters maximumDistance is 5.0 meters physical Boat Motion 5/17/2024 3:00:56.532 pm
fadingTime 5.0 seconds fadingTime is 5.0 seconds physical Boat Motion 5/17/2024 2:50:57.331 pm
detectionDelay 0.1 seconds detectionDelay is 0.1 seconds physical Boat Motion 5/17/2024 2:50:57.280 pm
minimumDistance 0.2 meters minimumDistance is 0.2 meters physical Boat Motion 5/17/2024 2:50:57.228 pm
radarSensitivity 6 radarSensitivity is 6 physical Boat Motion 5/17/2024 2:50:57.178 pm
maximumDistance 5.0 meters maximumDistance is 5.0 meters physical Boat Motion 5/17/2024 2:50:57.141 pm
fadingTime 5.0 seconds fadingTime is 5.0 seconds physical Boat Motion 5/17/2024 2:50:47.351 pm
detectionDelay 0.1 seconds detectionDelay is 0.1 seconds physical Boat Motion 5/17/2024 2:50:47.301 pm
minimumDistance 0.2 meters minimumDistance is 0.2 meters physical Boat Motion 5/17/2024 2:50:47.252 pm
radarSensitivity 6 radarSensitivity is 6 physical Boat Motion 5/17/2024 2:50:47.220 pm
maximumDistance 5.0 meters maximumDistance is 5.0 meters physical Boat Motion 5/17/2024 2:50:47.197 pm
fadingTime 5.0 seconds fadingTime is 5.0 seconds physical Boat Motion 5/17/2024 2:50:37.350 pm
detectionDelay 0.1 seconds detectionDelay is 0.1 seconds physical Boat Motion 5/17/2024 2:50:37.301 pm
minimumDistance 0.2 meters minimumDistance is 0.2 meters physical Boat Motion 5/17/2024 2:50:37.251 pm
radarSensitivity 6 radarSensitivity is 6 physical Boat Motion 5/17/2024 2:50:37.199 pm
maximumDistance 5.0 meters maximumDistance is 5.0 meters physical Boat Motion 5/17/2024 2:50:37.167 pm
fadingTime 5.0 seconds fadingTime is 5.0 seconds physical Boat Motion 5/17/2024 2:50:27.377 pm
detectionDelay 0.1 seconds detectionDelay is 0.1 seconds physical Boat Motion 5/17/2024 2:50:27.330 pm
minimumDistance 0.2 meters minimumDistance is 0.2 meters physical Boat Motion 5/17/2024 2:50:27.292 pm
radarSensitivity 6 radarSensitivity is 6 physical Boat Motion 5/17/2024 2:50:27.257 pm
maximumDistance 5.0 meters maximumDistance is 5.0 meters physical Boat Motion 5/17/2024 2:50:27.227 pm
fadingTime 5.0 seconds fadingTime is 5.0 seconds physical Boat Motion 5/17/2024 2:50:17.371 pm
detectionDelay 0.1 seconds detectionDelay is 0.1 seconds physical Boat Motion 5/17/2024 2:50:17.320 pm
minimumDistance 0.2 meters minimumDistance is 0.2 meters physical Boat Motion 5/17/2024 2:50:17.272 pm
radarSensitivity 6 radarSensitivity is 6 physical Boat Motion 5/17/2024 2:50:17.236 pm
maximumDistance 5.0

I don't see this with my radars... What is the driver version that you are using?

Make a screenshot of the State Variables section.

Here you go Sir...

Summary

Latest version that was pushed for updates via HPM is 3.1.3, dated 2024-05-11. You have an earlier version, honestly I don't remember whether this bug was fixed in the next version.

I can recommend to use the HPM (Hubitat Package Manager) for receiving update notifications..
Do a 'MatchUp' in HPM, and you will receive the latest versions with bug fixes, if not done yet,

1 Like

Running ver. 3.1.4 2024-05-11 I have an unusual situation of a device not preserving parameters.

I wanted a fade of 30 seconds and a power level of 3, but it stubbornly decides that 60 seconds and "2" is what it will allow.

dev:6802024-05-19 10:05:27.598 AMinfoFront Porch SNZB-06P detectionDelay is 0.0 seconds [refresh]
dev:6802024-05-19 10:05:27.486 AMinfoFront Porch SNZB-06P fadingTime is 60 seconds [refresh]
dev:6802024-05-19 10:05:27.387 AMinfoFront Porch SNZB-06P radarSensitivity is 2 [refresh]
dev:6802024-05-18 03:50:13.463 PMinfoFront Porch SNZB-06P detectionDelay is 0.0 seconds [refresh]
dev:6802024-05-18 03:50:13.367 PMinfoFront Porch SNZB-06P fadingTime is 30 seconds [refresh]
dev:6802024-05-18 03:50:13.262 PMinfoFront Porch SNZB-06P radarSensitivity is 3 [refresh]
dev:6802024-05-18 03:50:11.054 PMinfoFront Porch SNZB-06P updated
dev:6802024-05-18 03:50:10.986 PMinfoFront Porch SNZB-06P setPar: (3) successfluly executed setPar customSetDetectionDelay(0)
dev:6802024-05-18 03:50:10.973 PMinfoFront Porch SNZB-06P setPar: (3) successfluly executed setPar customSetRadarSensitivity(3)
dev:6802024-05-18 03:50:10.964 PMinfoFront Porch SNZB-06P setPar: (3) successfluly executed setPar customSetFadingTime(30)
dev:6802024-05-18 03:50:10.897 PMinfoscheduling health check every 240 minutes by Activity check method
dev:6802024-05-18 03:50:10.879 PMinfoFront Porch SNZB-06P driver version 3.1.3 2024/05/11 9:46 AM (SNZB-06P SONOFF) (C-7 2.3.8.140)
dev:6802024-05-18 03:50:10.876 PMinfoFront Porch SNZB-06P updated()...

1 Like

From the logs I see that your preferences of 30 seconds / sensitivity 2 were confirmed to be accepted by the sensor at 03:50:13

However, at 10:05:27 the settings were reported as being changed somehow... There are 6 hours between these events, is it possible that the device was reset to the factory defaults in this period?

Note, that this driver (also all of my other drivers) will update the Preferences parameters to the real values as reported by the device itself. As an example, if you try to set a fading time of 3 seconds, but the device does not accept it and report back 10 seconds instead - next time you refresh the web page you will see 10 seconds fadingTime - this is the actual setting, not the 3 seconds that was not confirmed by the device.

All the previous versions of this and the 4-in-1 driver should have the same behavor in regards to the preferences handling (the automatic update of the real values).

Yes, I did a refresh to see if the device was still communicating. Nothing happened to the device in the interim, so the setting of the parameters seems to be successful at first, but later silently fall back again...

Here's the longs showing that a setting of parameters works, at least initially. These are the complete logs, nothing left out, just annotated:

Here is the "refresh" showing that the parameters change back to "factory defaults" of 60 secs and power level 2 within minutes of being set:

dev:6802024-05-19 06:40:19.822 PMinfoFront Porch SNZB-06P detectionDelay is 0.0 seconds [refresh]
dev:6802024-05-19 06:40:19.729 PMinfoFront Porch SNZB-06P fadingTime is 60 seconds [refresh]
dev:6802024-05-19 06:40:19.625 PMinfoFront Porch SNZB-06P radarSensitivity is 2 [refresh]

Below is the initial refresh after setting, which seems to verify that the device took the settings:

dev:6802024-05-19 06:32:45.599 PMinfoFront Porch SNZB-06P detectionDelay is 0.0 seconds [refresh]
dev:6802024-05-19 06:32:45.504 PMinfoFront Porch SNZB-06P fadingTime is 30 seconds [refresh]
dev:6802024-05-19 06:32:45.415 PMinfoFront Porch SNZB-06P radarSensitivity is 3 [refresh]
dev:6802024-05-19 06:32:35.516 PMinfoFront Porch SNZB-06P detectionDelay is 0.0 seconds [refresh]
dev:6802024-05-19 06:32:35.496 PMinfoFront Porch SNZB-06P detectionDelay is 0.0 seconds [refresh]
dev:6802024-05-19 06:32:35.420 PMinfoFront Porch SNZB-06P radarSensitivity is 3 [refresh]
dev:6802024-05-19 06:32:35.387 PMinfoFront Porch SNZB-06P fadingTime is 30 seconds [refresh]
dev:6802024-05-19 06:32:35.366 PMinfoFront Porch SNZB-06P fadingTime is 30 seconds [refresh]
dev:6802024-05-19 06:32:35.336 PMinfoFront Porch SNZB-06P radarSensitivity is 3 [refresh]
dev:6802024-05-19 06:32:31.326 PMinfoFront Porch SNZB-06P updated
dev:6802024-05-19 06:32:31.240 PMinfoFront Porch SNZB-06P setPar: (3) successfluly executed setPar customSetDetectionDelay(0)
dev:6802024-05-19 06:32:31.227 PMinfoFront Porch SNZB-06P setPar: (3) successfluly executed setPar customSetRadarSensitivity(3)
dev:6802024-05-19 06:32:31.218 PMinfoFront Porch SNZB-06P setPar: (3) successfluly executed setPar customSetFadingTime(30)
dev:6802024-05-19 06:32:31.179 PMinfoscheduling health check every 240 minutes by Activity check method
dev:6802024-05-19 06:32:31.165 PMinfoFront Porch SNZB-06P driver version 3.1.3 2024/05/11 9:46 AM (SNZB-06P SONOFF) (C-7 2.3.8.140)
dev:6802024-05-19 06:32:31.162 PMinfoFront Porch SNZB-06P updated()...

Here is where we saw it revert to "60 seconds fade" and "power level 2:

dev:6802024-05-19 06:31:02.008 PMinfoFront Porch SNZB-06P detectionDelay is 0.0 seconds [refresh]
dev:6802024-05-19 06:31:01.912 PMinfoFront Porch SNZB-06P fadingTime is 60 seconds [refresh]
dev:6802024-05-19 06:31:01.813 PMinfoFront Porch SNZB-06P radarSensitivity is 2 [refresh]


Here is where it functioned, detecting motion (but note that it reset after 65 seconds, not 30):

dev:6802024-05-19 11:10:19.628 AMinfoFront Porch SNZB-06P Motion reset to inactive after 65s
dev:6802024-05-19 11:09:14.277 AMinfoFront Porch SNZB-06P Detected motion

Below is the same logs as before, where a "refresh" the next morning showed a silent change from 30 secs and power level 3 back to 60 secs and power level 2:

dev:6802024-05-19 10:05:27.598 AMinfoFront Porch SNZB-06P detectionDelay is 0.0 seconds [refresh]
dev:6802024-05-19 10:05:27.486 AMinfoFront Porch SNZB-06P fadingTime is 60 seconds [refresh]
dev:6802024-05-19 10:05:27.387 AMinfoFront Porch SNZB-06P radarSensitivity is 2 [refresh]
dev:6802024-05-18 03:50:13.463 PMinfoFront Porch SNZB-06P detectionDelay is 0.0 seconds [refresh]
dev:6802024-05-18 03:50:13.367 PMinfoFront Porch SNZB-06P fadingTime is 30 seconds [refresh]
dev:6802024-05-18 03:50:13.262 PMinfoFront Porch SNZB-06P radarSensitivity is 3 [refresh]
dev:6802024-05-18 03:50:11.054 PMinfoFront Porch SNZB-06P updated
dev:6802024-05-18 03:50:10.986 PMinfoFront Porch SNZB-06P setPar: (3) successfluly executed setPar customSetDetectionDelay(0)
dev:6802024-05-18 03:50:10.973 PMinfoFront Porch SNZB-06P setPar: (3) successfluly executed setPar customSetRadarSensitivity(3)
dev:6802024-05-18 03:50:10.964 PMinfoFront Porch SNZB-06P setPar: (3) successfluly executed setPar customSetFadingTime(30)