-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tuya - PIR 24G Radar Sensor - ZG-204ZM #7836
Comments
Hi. If you need anybody to test the DDF and device functionality, just tell me as I have 3 of the mmW sensors at home. |
Here also, have several of these sensors available, would likt to test also... |
Can try
|
Hey, the sensor is connecting but the data I get unfortunately make no sense. |
A presence entry and a lightlevel are created by the rest plugin. The ZHAPresence seems to update, but the trigger to presence=true is delayed big time, like a minute or so. The ZHALightlevel part is not updating at all it seems, not even after wating quite some time. The battery level is not present at all in the REST API output. This is a battery device, so it should be there right? I will add the REST API output and also the trace level output that is generated after pressing the button for triggering all the reports on the Tuya branch, I hope this will help you? `ZHALightLevel **************************** Object info ***************************** ZHAPresence **************************** Object info ***************************** Output for triggering all Tuya reports is attached as copy and paste creates a mess.... |
Right, have (tried o) add it on previous DDF
It's not reversed ? I don't see a setting o the device that can delay the detection, so can be the "no detection" after a delay ?
Yeah, defaut value, the code use a common JS file
Perhaps a folder path issue ? where have you put the DDF ? On your file
This is the dpid for detection, need to have this line at detection. and this one if the luminosity |
Battery is still not reported at this moment, do I need to change something for that? I had the file placed on the .local\share\dresden-elektronik\deCONZ\devices area, where DDF's are placed when you edit the DDF for the first time... I will move the DDF to the installed area for the correction? I will try to recheck on the motion. I indeed would expect a delay before nomotion occurs, motion should occur immediately... will monitor this a bit more.
That is the trigger for motion? That will help to check indeed.. that way I can exclude an delay to my plugin. Thanks! |
Just need to replace the DDF. For me it need to work, the code
Your log
Pls try with the file in the "tuya" folder, don't remeber to remove the previous one.
Yes, you need to have it at motion detection, but state/presence" need to become tru in same time and after 90s need to have
(Or the reverse) |
I have added the battery entry, this is now reported correctly. And ZHAPresence after a reset of the device is reprting immediately now as expectd... So I do think it is complete? Below is the DDF I have now. I think it should be good now? { |
Yes and it's tuya cluster, you have no settings on them, all is native, no binds, no report settings.
As you want ^^. |
I never did a PR yet, so if you can do this, it would be helpful for me. Also, looking at the comments in the DDF for lux, it suggests its max value is 2000, but the value from the Tuya device seems to never drop below 2000? Is it possible the javascript being used is returning a wrong value? |
I see the same issue. The lx value makes no sense. |
This depend of phoscon, if I m right the DDF create a ZHALightLevel and a ZHAPresence ? About the convertion, IDK, the device return
So the DDF take the value 1680 and use this value for state/lux (without change) and this script to compute state/lightlevel https://github.com/dresden-elektronik/deconz-rest-plugin/blob/master/devices/generic/illuminance_cluster/lux_to_lightlevel.js 10 .000 lux is outside with sun I can use a convertion if needed, but need to make try to know mini/maxi. Not a problem with mistake beetween lightlevel and lux ? Can you compare the lux value (raw value without convertion) with the light level on the LUMI sensor ? |
I am checking both sensors I mentioned in my earlier post here, they are still laying next to each other. I did a trigger report on the tuya cluster and think I have the line you were posting
This was a minute or two later, so there might be a small difference in the results. But this looks like the value is not converted at all? The DDF is on the production area still so I guess the js file is still executed? Does this help in the search? |
Yes exactly the state/lux for the _TZE200_kb5noeto is a raw value. Can try with a /50 (38 * 50 = 1900), but not sure it will be proportionnal. Try with replacing
and create the file lux_to_lightlevel2.js in the same folder with
|
I did the change and now I get values 26 on the lumi.sen_ill.mgl01 and 34 on the _TZE200_kb5noeto. This is a lot closer than before... I will do a few more checks during daylight to see if the values stay close. I guess we will never make this a 100% match. |
Tried the DDF mentioned in this post but it will not work with it. Saved it as json in share and .local folder and tried to load DDF in deconz directly (failed to load message). What can i do? Used copy&paste to create my json. |
This one > #7836 (comment) ? I don't see typo on my side. |
I have the same issue after upgrading to 2.27.6. because of the upgrade I lost my files on the production devices. I tried to copy the file from my windows system to the raspberry pi. Got the error trying to hot reload. Then I opened a sudo nano command in terminal and pasted the lines and saved it (I am a nitwit on linux, but this at least I know). Then I tried a hot reload with the same result, error. Then I tried to upload the file with the phoscon function to update a DDF, offering the windows file I mentioned earlier.. smae result. Not sure, but I think this might be something with this latest deCONZ version? |
Same issue here. However I am on version 2.27.5. after trying some other custom files, it seems none of the DDFs I try to load are working. Also tried different file encodings and line endings, however I do still get the error |
I copied the data from here #7836 (comment) , created a ddf / json and have the same problem. Working with version 2.27.5. |
I had the same issue, in the "values" section is no escaping which causes troubles. This one should work:
|
Thats it. Its working now! Thank you |
And about the ratio convertion from here #7836 (comment) ? |
It is close enough to the most of my lightsensors 30 lux on the lumi.sen_ill.mgl01 and 26 at the same time on the _TZE200_kb5noeto. During day time they stay close too, so I guess it is ok this way? |
Ah, i don't see before that you have to create an extra script file for this. I will try but i am sure that division by 50 will be ok. Will this be automatic included in further deconz updates? |
As you want. |
I see no issues with that 👍 |
PR done here #7865 |
Thanks |
Hi there, I just ordered a Tuya _TZE200_kb5noeto version and I'm wondering if / and if yes how I can configure this presence detector when using it with deconz. In the Tuya manual, there's a QR-Code to Scan, linking to this page: If I know click on the docs-link for the ZG-204ZM page, I get this document here: https://doc.szalarm.com/zg-205Z/doc/ZG-204ZM.pdf There is also a screenshot of the Zigbee2MQTT UI where you can configure the settings of this presence detector: Is it also possible to configure this via deconz? I am using deconz on my raspberry using the docker image. I already opened the VNC connection but could not find where to configure these settings for my sensor. Best regards Daniel |
Should I maybe rather post in a new thread/is it even possible with deconz to edit such parameters? |
Just look at field presenty in the DDF, you will see wich one are supported ATM. |
Is there already an existing issue for this?
Product name
ZG-204ZM
Manufacturer
_TZE200_kb5noeto
Model identifier
TS0601
Device type to add
Sensor
Node info
Endpoints and clusters
Basic
Further relevant clusters
The text was updated successfully, but these errors were encountered: