-
Notifications
You must be signed in to change notification settings - Fork 496
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 ZigBee Multi-Sensor 4 in 1 Smart PIR Motion Feuchtigkeit Licht Temperatur Sensor / TS0202 #4511
Comments
This device have the tuya cluster, but not sure it use it. @easybeat do you have a real linux machine to test code modification ? |
Yes I run deconz on a ubuntu workstation |
So here you have the procedure to test code https://github.com/dresden-elektronik/deconz-rest-plugin#install-deconz-development-package-optional-linux-only
I have just added the device in white list, it use ikea mac adress range ... |
Good morning, thank you for your immediate support. I will test today at lunch time! |
@Smanar Do I have to install something else before? |
found the problem. Did "sudo apt install build-essential" and then it works |
@Smanar Do I have to check something else? |
If you can see it in phoson (and not only deconz), can you just check if all is working ? It s possible phoscon don't support all device feature, if you can check with third app or directly with the API if needed ? |
No I can't see it in Phoscon but did check inside ioBroker with hueExtended Adapter and there all the datapoints are in. A bit strange as it did create 4 devices but that's maybe more a problem from the Adapter. I also triggered an update on the device and new temperature und humidity etc. came through. So I really think it's fine. Thank you very much. |
Yep it create 1 devices by endpoint, and 1 by cluster, it s the normal working mode for deconz. |
Yes I think so so...everything ready to go. |
Hi Smanar Just updated to 2.11.01 and now finally paired TS0202 succesfully. Unfortunately small problem. Temperature and Humidity values do not update automatically. If I press read on cluster then the values are updated. Is there something you can do about it? Thank you |
Can be reporting issue, but all seem fine in the code, it have worked on your first try ? Just Humidity and Temperature ? Perhaps a step haven't worked during the inclusion, the set reporting part. |
Yes it is only Humidity and Temperature which is not working. I will try to do the inclusion again. |
Will be fine if you can catch logs during inclusion in same time with "info" and "info_l2" (but can be hudge, just need all about the cluster 0x0402 and 0x0405, log about reporting or bind) |
Ok Smanar, I deleted the device and restarted deconz and the joined it again. It looks wierd now as "lightlevel 71" And also no temperature or humidity comes through. here is the log-fiel during paring: Hope this is helping? |
At least bind seem good ... Endpoint 0x02 Value used by deconz are
Edit: Ok, I have found the problem, the device use tuya cluster, so perhaps need to enable something before, need to write some code. |
Can you try this new code
With this code you will have new log starting with "tuya debug", if the code don't work, logs can be usefull. There is too a command to enable reporting, but idk if this setting is usefull yet, what is the utility to disable a reporting .... |
Hi it looks different now but still no luck with temperature and humidity Luminance is working but it should also have presence. Here the log file: I did connect this sensor with zigbee2mqtt and attributes created there were as follows: Does this help? Thanks for help |
You don't need to re-include it, the inclusion is fine. You need to see some logs about a cluster 0xFC00 or better logs starting by
If you realy see nothing I will make the command to enable reporting |
OK started the dev instance again and now it is showing like this: and the log is here when I read temperature: if you search for /sensors/61 then you find the event. Does this help? Thanks |
Ok so still nothing about the tuya cluster ..
|
Hi Do I have to rebuild deconz? As I get this error: [{"error":{"address":"/sensors/62/config/reporting","description":"parameter, reporting, not available","type":6}}] Thanks |
Yep, like for previous tests, but no need to re-include the device (I think the restart will be enought) |
Yeah, using the GUI permit to learn a lot on zigbee working mode, the app is so usefull for me. |
@easybeat I have a question ! If you are sure of that I will need to make a change. for the command was send natively by deconz during the inclusion. |
@Smanar No it doesn't make sense to do "reporting:false". Why do you think I would do this? No need for me. |
it s exactly the manup reaction ^^. But I don't see the utility of this command, it realy disable TOTALY the reporting for temperature and humidity ? |
@easybeat if you still have your dev machine ? I have a new branch to test
On this one I have remove the field "config/reporting" as this setting is probably useless, so now the code send itself the command to enable it To test it, you just need to re-include your device, you will have in log (with "info")
|
Do I have to install latest release to do that? |
e_web_plugin.cpp: In member function ‘virtual bool DeRestPlugin::isHttpTarget(const QHttpRequestHeader&)’: In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qcoreapplication.h:44, got these errors |
OK I have now updated to 2.12.00...could you please assist me how to get your code from there? |
Ha yes, the version is moving a lot ATM.
Then need to clean the project
After that it s classic, if you start from scratch
Else
And to finish
|
bindings.cpp: In member function ‘void DeRestPluginPrivate::checkLightBindingsForAttributeReporting(LightNode*)’: bindings.cpp:2582:93: error: conversion from ‘std::vectordeCONZ::ZclCluster::const_iterator’ {aka ‘__gnu_cxx::__normal_iterator<const deCONZ::ZclCluster*, std::vectordeCONZ::ZclCluster >’} to non-scalar type ‘QListdeCONZ::ZclCluster::const_iterator’ requested bindings.cpp: In member function ‘bool DeRestPluginPrivate::checkSensorBindingsForAttributeReporting(Sensor*)’: doesn't like me anymore!! |
Lol, no, don't worry was my fault, the lib was updated but not the branch
|
Now it did work and after re-include the device works as it should... |
Ha nice ^^.
when including it ? |
@easybeat do you had time to take a look on logs during inclusion ? |
No sorry...not yet...will try tomorrow morning |
@Smanar Hi I haven't found an entry about "reporting status". There are a lot of these entries: Does that help? Thanks |
Yep, thx a lot
So deconz have send the request, but the device haven't answer. Have modified the code again, but not sure will be usefull to test it again, I will make the PR with it, your device is working, so the command is probably not needed. When you include it, you reset setting. |
@Smanar I can confirm the device is working for me. Thanks for help. |
Nope, thx, I m waiting for PR validation, but I have just see I need to upate it first. |
Hi Smanar did this ever go into "production"? Not sure if it's in 2.12.6? Kind regards and Thanks |
I think he is in the stable no ? I don't find PR in waiting list about it. |
Ok let me do some further test...using it on a new system and need to set this up first...
Thanks
Am 10. Oktober 2021 19:20:04 MESZ schrieb Smanar ***@***.***>:
…I think he is in the stable no ? I don't find PR in waiting list about it.
Your device is the "_TZ3210_zmy9hjay" ?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#4511 (comment)
|
Hi Ok sensor is working and reporting correctly all values! Model is "_TZ3210_zmy9hjay". But tried to connect a second sensor to the system. It works but the first sensor disappears in deconz gui. I can still see it in the API. Also it shows as "LightLevel15" all the time. The sensors also do not show up in Phoscon App. Is this something you can fix? Kind regards |
You mean including a second device will delete the first one on the GUI ? The device was correclty included ? have the 2 circle on th node title ? Not possible a node is deleted if it was correclty included, disconnected ok, but deleted ....
This don't depend of the API, Phoscon use white/black list. |
Hur several hours will be better, thoses devices are not called sleeping device for nothing ^^ |
Device
Screenshots
Thank you very much for your help.
The text was updated successfully, but these errors were encountered: