Problem with Presence in 24G tuya radar

[beliy82]

Hi, just added Tuya RT_ZCZ03Z Presence sensor,
and the illuminance work great, target distance is working, but the presence stays always on false... any idea?

[beliy82]

same here.... hoped the new update will fix it, but no

[oritor91]

I also have the same issue. Help needed if anyone figured it out.

[beliy82]

any news?

[S12Link]

Same here. All parameters work correctly except presence, always false.
Is it a zigbee2MQTT bug?

[beliy82]

i am with homekit and homebridge, i cannot make automation based on distance, but with zemismart it works fine, in smartlife app

[S12Link]

Then it must be a zigbee2Mqtt problem. Do the developers read this thread? It would be interesting if they reviewed it because perhaps the solution could come with an update.

[6PATyCb]

While we wait for the fix, you can try this converter
RT_ZCZ03Z.zip

[beliy82]

how to use it?

[S12Link]

Hello, thank you very much, I didn't know that this type of external files existed.

I have been reading about the issue in several Github threads, seeing that there are more people with this problem on similar devices.
The converter you attached makes presence detection work, but sometimes it goes crazy and gives false positives.
The two states that appear to me are: 0.- Unknown, 1.- Present.

The presence option does not appear in the automations in home assistant either, only when you configure it as an entity, and the options are unknown, any state and not available.
I use it with the value "Not available" to do the automation.

To prevent the light from turning on when giving a false positive, I have added the target distance as a condition.
We are still testing, let's see when they solve the problem, but thank you very much for the contribution friend.

To use these external files (converters), I pass the link:
#17483 (comment)

[S12Link]

Hello, thank you very much, I didn't know that this type of external files existed.

I have been reading about the issue in several Github threads, seeing that there are more people with this problem on similar devices.
The converter you attached makes presence detection work, but sometimes it goes crazy and gives false positives.
The two states that appear to me are: 0.- Unknown, 1.- Present.

The presence option does not appear in the automations in home assistant either, only when you configure it as an entity, and the options are unknown, any state and not available.
I use it with the value "Not available" to do the automation.

To prevent the light from turning on when giving a false positive, I have added the target distance as a condition.
We are still testing, let's see when they solve the problem, but thank you very much for the contribution friend.

To use these external files (converters), I pass the link:
#17483 (comment)

[6PATyCb]

This is not my script. I found it in one of the forums and fixed it so that it works on the latest version of z2m. The script is not perfect, some things in it still do not work. It also seems to me that you and I can have different devices that have a common chip and are recognized the same way, but they can have different firmware and different behavioral bugs. My device looks like this:

[S12Link]

In appearance, it is the same. It also has green wall plugs 😂.
I think the false positives were due to a curtain moving with the air, so that's not a problem.
The rest works, except the indicator, which gives an error in the zigbee2Mqtt log.
But it works much better than before, and the errors it has are negligible.
Thank you very much, now at least it works as it should.

[6PATyCb]

RT_ZCZ03Z_v2.zip

I corrected the script so that the LED would work and so that the presence would be true/false. For the script to work properly, you need to forcefully remove the device and add it again (after connecting the script file):

[6PATyCb]

And now version 3, which looks better in HA.
RT_ZCZ03Z_v3.zip

[6PATyCb]

And version 4, with worked reset button
RT_ZCZ03Z_v4.zip

[S12Link]

Thanks man, you're great.
I have used the V4 script and it works perfectly, just as you said, both the presence and the indicator.
Thank you very much man.

[oritor91]

I also use homebridge with zigbee2mqtt plugin (running on raspberry pi 4) - how can I use the RT_ZCZ03Z_v4 script? would love for a short explanation.

…

On Mon, Oct 21, 2024 at 7:35 PM S12Link ***@***.***> wrote: Thanks man, you're great. I have used the V4 script and it works perfectly, just as you said, both the presence and the indicator. Thank you very much man. — Reply to this email directly, view it on GitHub <#23484 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKEUMND4E6JBSNMWS72A55DZ4UUL3AVCNFSM6AAAAABL4XFHFKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBQG43TAOA> . You are receiving this because you commented.Message ID: ***@***.***>

[6PATyCb]

I think it must work for you.
You need:

1. upload script file to z2m data folder:
   

2. include file to z2m (you can do this over web):
   

3. restart z2m(If all good take a look at z2m start log):
   

4. profit! Now your device must work fine:
   
   device sensor real time changes will be visible at 'State' tab:
   

[oritor91]

It worked! Thank you so much

…

On Mon, 21 Oct 2024 at 20:53 Alexander ***@***.***> wrote: I think it must work for you. You need: 1. upload script file to z2m data folder: default.png (view on web) <https://github.com/user-attachments/assets/4ce65b30-323c-4964-990c-452ae915d447> 2. include file to z2m (you can do this over web): default.png (view on web) <https://github.com/user-attachments/assets/38e83393-aa3b-46dd-a9bc-354546f2459f> 3. restart z2m(If all good take a look at z2m start log): default.png (view on web) <https://github.com/user-attachments/assets/8139871a-c551-4d7d-ae31-c6241475d3e0> 4. profit! Now your device must work fine: default.png (view on web) <https://github.com/user-attachments/assets/702a0d6a-fff6-4f56-b9b8-a903d20a595e> device sensor real time changes will be visible at 'State' tab: default.png (view on web) <https://github.com/user-attachments/assets/d9b4a30f-2f05-4720-a413-a5281da4ecc9> — Reply to this email directly, view it on GitHub <#23484 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKEUMNFPNCPHS7AG7L6BVP3Z4U5TNAVCNFSM6AAAAABL4XFHFKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBQHAZTSMY> . You are receiving this because you commented.Message ID: ***@***.***>

[S12Link]

Hello again. After working fine all this time, now I'm having problems again.
The detector remains "present" all the time, as if it were blocked.
I tried resetting it, without success.
I tried leaving it without voltage for a while and then resetting it, without success.
I tried removing it from zigbee2mqtt and rebinding it. This seemed to work, but it only lasted two days, then the same thing happened again, always "presence".
Does it happen to anyone else?
Are there new versions of the external converter?

On the zigbee2MQTT page (devices) there is no problem with this detector and no link to github with the discussion, but here we are, with operating problems.

[6PATyCb]

What version of z2m are you using? I haven't used this device for a long time because I bought another one. I didn't make a new version of the converter.

[S12Link]

Hello, sorry for the delay in responding.
I'll give you an image with the z2m data.