Tuya Zigbee Smoke Detector #6515
Comments
|
Hello can you try this DDf |
|
thanks for the hint. How can I test this? |
|
Depend of OS.
Then re-include the device |
|
Thanks. What's the problem now?
Here I want to include the new file...
...then the error message follows
|
|
:(, was my bad 2 typo in the same DDF, sorry have made it with copy/paste without test. I have updated it on the previous post. |
|
No problem. Now it looks like this... What is the next step?
It is now also recognized in the Phoscon app but not listed yet
API looks like this:
|
|
Fire sensor are not visible in phoscon. But there is "last updated" to "none" so the device have probably never send a notification. I have just found that Koenkk/zigbee2mqtt#11119 (comment) Perhaps this device don't use same DP than the one I m using. To be sure there is only way. |
|
Oh, thank you. Have triggered an alarm with a button and get this information:
In the APP / API /Events: { |
|
It's perfect, it's exactly what we need. So the device is using :
On the Z2M link he have 0x65 = 0 and you = 1 (because you have trigger a detection), all other values are same for him, so I think it's the value to use for fire detection. So you edit edit the DDF to use the value 101 here Now for the battery is another problem, you haven't an used battery to make the same thing ? |
|
Now: { |
You don't have notification with state / fire when making the same thing that you have done before ? Need to make "hot relaod" in the ddf editor menu after editing the DDF, or relaod deconz. |
|
17:27:06:715 TY_DATA_RESPONSE: seq 1, dpid: 0x65, type: 0x01, length: 1, val: 1 |
|
BTW you have a setting issue too
You haven't an old backup somewhere ? Else can set the value using the deconz setting window (with pressing F9), need to have something like here https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Network-lost-and-configuration-restore-does-not-help#in-case-the-network-does-still-not-come-up And BTW the DDF is not working, try this one pls. And have new dpid
So the device is using :
Some device are using the 0x0E for battery state, ATM the value = 2 for full charged, but you can have 1 = medium and 0 for low. |
|
Thank you very much for being so patient with me... (I don’t speak English or almost no English and I have to translate it first) I followed the instructions... Debug Info: 12:37:09:748 Skip automatic channel change, TODO warn user In the Phoscon App: (Rest API) { Events: { |
No, for the moment, you can just restart deconz, I don't change the device configuration, all changes are on deconz side.
You have a lastupdated values, So I think the state/fire is working no ? You haven't an old battery to try to find the "low battery" or the "battery level" dpid ? BTW you have a problem in your setup (and don't worry I have an awful english too ^^)
In purple, the red stuff is not for you |
|
I connect 2 sensors from Aqara with the adapter “DeConz” in the iobroker. The screenshots from above I have always started directly from the DeConz-Gui, top right. Now that I have e. g. stopped deconz-gui and started deconz. . . . and triggered a test alarm, I see the following in the Phoscon app under Events: |
|
In iobroker I see the following under objects:
|
|
Alarm triggered and now stands ....
|
|
I have old batteries in it now, it beeps at regular intervals... How can we test this? |
No automatic return to false ? It can happen on some device that make a new notification at every detection but never return back, but from your log this device need to return to false itself.
Like usual, looking for tuya return ^^. By deduction I think it will be this one
And you will have a lower value than 2, 1 or 0 |
Yes, it does. With old batteries 21:18:44:574 TY_DATA_RESPONSE: seq 30, dpid: 0x01, type: 0x04, length: 1, val: 0 |
And it's the only one that have changed, so I m almost sure it's this one, not the first time I see this dpid So I think the final DDF, for state/fire and state/battery You don't need to re-include the device. I m using the value in the 0x0E request and * 50 so you will have as battery level 100/50/0 for values (2/1/0) |
|
Great, looks good. . . I don’t have any batteries, which are about 50%, but it shows 100 and 0 With good batteries: 22:34:07:116 Websocket 192.168.0.60:39184 send message: {"attr":{"id":"11","lastannounced":"2022-11-14T21:27:24Z","lastseen":"2022-11-14T21:34Z","manufacturername":"_TZE200_dq1mfjug","modelid":"TS0601","name":"Fire 11","swversion":null,"type":"ZHAFire","uniqueid":"a4:c1:38:1a:40:d3:3a:75-01-ef00"},"e":"changed","id":"11","r":"sensors","t":"event","uniqueid":"a4:c1:38:1a:40:d3:3a:75-01-ef00"} (ret = -1092779880) and "others" 22:41:01:847 TY_DATA_RESPONSE: seq 11, dpid: 0x0E, type: 0x04, length: 1, val: 0 |
|
What’s the next step? The sensor should then be displayed under DeCONZ or in the Phoscon APP. From there I can also integrate it into the iobroker. Unfortunately, it no longer works in iobroker today. There was still Fire 17. So I deleted it in the iobroker. But I can not integrate the Fire 11, which is displayed in the deCONZ Gui. How this was with the Fire 17 I can’t explain myself either. |
Yeah it's with the value 1, probably with medium charger battery ...
Lol, me too, It was not working or are not visible ? a synchronisation issue ? For information, you can see raw value in phoscon/help/API Information /sensors
On third app. Deconz don't use the API and display the reality, and phoscon don't display all devices in the API, iobroker need to be better than it |
|
In deCONZ the sensor is visible and when I press the Phoscon app in the upper right corner and connect it to, then the information is available in the API. Then I enter the commands in the console: stop deconz-gui and start deconz. Then I open the Phoscon app and there is no information in the API and the sensor is not listed. In addition, the sensor does not appear in the iobroker and I do not know how I could integrate it there....? |
|
Ha ? But it was still in deconz ? What is your OS ? docker ? Some OS have not persistent config. |
|
Best from the start: In order to get deCONZ-gui and the connection to the ConBee II, the following commands are entered in the console: Then I connect via Remotdesctop to the Pi and the connection is established. There I see the sensor e.g.Fire 12. If I start the Phoscon APP from there with the button in the upper right, then I see the data from this sensor in the API. Then I close the deCONZ-gui, disconnect the connection and enter the following commands: Then I start the Phoscon app directly in the browser and there is no data in the API and the sensor is not present. Here’s the thing. I had to create a separate user on the Pi for access via Desctop. With this data I log in via Remotdesctop. I use a Pi4 with Linux. Yes, I have integrated 2 Aqara temperature and humidity sensors and they work perfectly. I also see this in the deCONZ-gui. Pictures of these are shown above.
I haven’t applied this tip yet. Do I need to make this “adjustment” to APS Use Ext PAN ID? If it doesn’t work, can I just go back to the old value? |
|
The GUI mode use the same database than the headless mode, so you are fine.
Hu :(, It remember me the issue. You need to be PI as user for correct working mode. Have you try to include the device on the headless mode ? without the GUI , one time the DDf is on a folder "devices" it need to work for both mode.
It's not just a tip ^^, you realy need to correct that. It happen sometime if you use the conbee with other software. It's possible the value can be set only if you are offline, so you can use the (1) to disconnect |
Sorry, can I ask how to do this? If I see correctly, the Sonsor is in here:
I’ve done that now, thank you. |
|
I just want the following: |
Yeah but I don't understand why the inclusion is not memorised in the data base, probably a "user issue". But for me it's fine, if you put the file like on the capture, it need to be used for the user "nano" for all type of running deconz (headless and desktop), so just try including the device with this user (on headless mode if its the mode used with iobroker) But I hope iobroker is running for the "nano" user too ? By defaut its "pi" for deconz. To use deconz with other user than "pi" there is some change to done, I hope you have correclty set your OS ? If you type "groups" you need to see "dialout" You can too try to put your DDF in the deconz folder |
|
@Smanar, you to the best and my hero! Thank you very much. It was actually due to the user’s settings. After I checked that both users are present in the dialout, the Pi restarted the sensor appears now in the iobroker! Wow. Although I don’t see it in the Phoscon app, but I think that’s normal, since now deconz have to record this sensor, right? I was also able to integrate a second sensor successfully. Question: |
the problem is only from Phoscon, it's a third app, but less powerfull than Iobroker.
Not possible with the GUI, you need to use direclty the API, and as phoscon don't support them, you haven't the possibility using iobroker ? else I can explain you how to do with the API ? For information:
So probably need a restart too. If the DDF is working wana make a PR to submit it, or I can make it if needed ? |
yes please
I don’t quite understand your question, sorry |
|
You have the long sory here https://dresden-elektronik.github.io/deconz-rest-doc/getting_started/ Else can use command line (from your old capture), the device id (11) can be different now
To submit the DDF, to have it officially in the code https://github.com/dresden-elektronik/deconz-rest-plugin/pulls if you make it, it will be under your name. |
|
All right, Smanar. Please do this for me. |
Yes, in iobroker it works. I can rename the sensors there! |
|
Pr submitted #6567
And easier than with the API ^^ |
That’s right, I think so. I would like to thank you very sincerely for all your efforts. Without your help, I wouldn’t have been able to integrate my sensors into my system. Do you think DeConz will integrate them now? |
|
I think yes, it's a small DDF and alone, will be faster than the PR with a package of 10/20 DDF ^^ Easy to know, this issue will be closed when the PR will be added. |
|
As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs. |
|
As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again. |
Device
bought at: https://de.aliexpress.com/item/1005003564649452.html
Screenshots
Basic
Node Info
Working Device Temperature and Humidity from Aqara
Basic
Node Info
The text was updated successfully, but these errors were encountered: