TuyaMCU integration for ZY-ZHPS01 mmWave Presence Sensor 5.8GHz

[f-io]

Hi,

got a fairly new mmWave 5.8GHz presence sensor. Tried to integrate it like @blakadder did with the https://templates.blakadder.com/ZY-M100.html. Has anyone here had success with this kind of sensor? MCU+Radar is an all in one solution from AirTouch (AT5820), power consumption ~0,5W.

Here the adjusted blueprint I tried without sucess: https://github.com/f-io/blueprint/blob/development/discovery_zy-zhps01.yaml
I'm new to homeassistant, so there is a good chance that I messed it up.

I repleaced the CB3S with an ESP-C3-12F. Light intensity is working reliable/fast, but the custom dpIDs are only updated once in a while or by manually TuyaSend0.

I used the tuya developer platform to identify the IDs.

The dpIDs

 dpIDs
   11 | light intensity    |  0-950 lux |  tuyaMCU 75,11
  101 | presence           |  0 = true,  1 = false
  104 | presencedelay      |  holdtime: 1-255s
  105 | sensitivity        |  0-x10 
  107 | microsensitivity   |  0-x10
  109 | maxrange           |  0-6m
  110 | minrange           |  0-6m
  111 | micromaxrange      |  0-6m
  112 | microminrange      |  0-6m
  113 | unkown

19:28:38.691 MQT: tele/mmwave/LWT = Online (retained)
19:28:38.693 MQT: cmnd/mmwave/POWER = 
19:28:38.698 MQT: tele/mmwave/INFO1 = {"Info1":{"Module":"ZY-ZHPS01","Version":"14.3.0(release-tasmota32)","FallbackTopic":"cmnd/mmwave_fb/","GroupTopic":"cmnd/tasmotas/"}}
19:28:38.716 MQT: tele/mmwave/INFO2 = {"Info2":{"WebServerMode":"Admin","Hostname":"mmwave","IPAddress":"10.0.0.118","IP6Global":"","IP6Local":"fe80::36b4:72ff:fe07:5a10%st1"}}
19:28:38.734 MQT: tele/mmwave/INFO3 = {"Info3":{"RestartReason":"Vbat power on reset","BootCount":46}}
19:28:38.816 TYA: MCU Product ID: {"p":"3rljcwhv5zazapfv","v":"1.0.3","m":0}
19:28:38.943 RUL: TUYARECEIVED#DPTYPE4ID101 performs 'publish mmwave/presence 0'
19:28:38.947 MQT: mmwave/presence = 0
19:28:38.984 RUL: TUYARECEIVED#DPTYPE2ID109 performs 'publish mmwave/maxrange 200'
19:28:38.986 MQT: mmwave/maxrange = 200
19:28:39.009 RUL: TUYARECEIVED#DPTYPE2ID110 performs 'publish mmwave/minrange 20'
19:28:39.014 MQT: mmwave/minrange = 20
19:28:39.037 RUL: TUYARECEIVED#DPTYPE2ID105 performs 'publish mmwave/sensitivity 5'
19:28:39.040 MQT: mmwave/sensitivity = 5
19:28:39.075 RUL: TUYARECEIVED#DPTYPE2ID111 performs 'publish mmwave/micromaxrange 130'
19:28:39.079 MQT: mmwave/micromaxrange = 130
19:28:39.108 RUL: TUYARECEIVED#DPTYPE2ID112 performs 'publish mmwave/microminrange 30'
19:28:39.112 MQT: mmwave/microminrange = 30
19:28:39.132 RUL: TUYARECEIVED#DPTYPE2ID107 performs 'publish mmwave/microsensitivity 2'
19:28:39.136 MQT: mmwave/microsensitivity = 2
19:28:39.161 RUL: TUYARECEIVED#DPTYPE2ID104 performs 'publish mmwave/holdtime 30'
19:28:39.165 MQT: mmwave/holdtime = 30

[f-io]

Okay, I've now found the messages, whoever stumbles across the same problem:

17:30:59.417 DMP: 55 AA 03 22 00 05 65 04 00 01 00 93
17:30:59.419 {"TuyaReceived":{"Data":"55AA03220005650400010093","Cmnd":34,"CmndData":"6504000100"}}
17:30:59.429 TYA: RX unknown command

= presence

17:31:14.567 DMP: 55 AA 03 22 00 05 65 04 00 01 01 94
17:31:14.569 {"TuyaReceived":{"Data":"55AA03220005650400010194","Cmnd":34,"CmndData":"6504000101"}}
17:31:14.578 TYA: RX unknown command

= !presence

RuleX on tuyareceived#Data=55AA03220005650400010093 do publish %topic%/presence 1 endon 
      on tuyareceived#Data=55AA03220005650400010194 do publish %topic%/presence 0 endon