Tuya Fingerbot Plus #7094
Comments
|
It's normal, device not supported, but need more information. https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Request-Device-Support |
|
Please add all screenshots. |
|
its a battery device |
|
We need screenshots of all clusters. Also, please add them in the first post. |
|
edited |
|
added new pic |
|
Hello, can try this DDF Support for on/off and battery |
hi, thanks for yr advice, now it shows on HA and phoscon, but i cannot control it in home assistant, when i press it, it just no response and turn back to the previous state, also it shows at lights category while its a switch. At deconz app it has a name now |
|
Ha, my bad the request use enum type and not bool. by |
um....i tried this code but still the same, deconz log shows this: |
And you have the reverse when using "on=true" instead of "on=false" ? Something you can do, is enabling/disabling the device yourself using "manual mode". You will see tuya return (with "info"), perhaps need to use another dpid. |
22:55:58:959 SC tick --> StateCallFunction this is the log when i turn it on and off at HA, no response at the device, but when i turn it on and off at deconz page or at the device physical button, the log didnt show up anything about that but the device did work |
You know how to do that on deconz ? using the tuya cluster ?
Not good, when you use it manualy, the device need to make a return to say his state have moved ..... Edit: Have set a bind for cluster 0x0006 but no reporting (hoping it was native like lot of Aqara device), and a 24h refresh for poll, for deconz don't poll the battery device. |
|
this works! thanks alot |
Hi, Because as you previously said, for me with this DDF, in deconz the fingerbot is displayed as a light, and in home assistant when you activate the fingerbot, it stays on, and do not go back to off (you have to activate it again so it goes off). |
yes the last one he provided, now at the phoscon app it shows as light, but at ha it shows as switch. The situation that stays on is no response, not work at all, it happens at prevoius ddf but at the last ddf, it works |
|
On the last DDF the device is reconised as "TYPE_ON_OFF_OUTPUT", so it's not realy a light for me, third app can display it as they want. |
|
Any idea on how to customize the up and down positions, and the sustain time with deconz ? |
|
For the sustain time can try But from that I m reading this device use raw mode, and it's not implemented in deconz (I have see another issue with the same problem today), 0x2b is for s32 value. Can make a try, I can update the c++ code if needed but I need you (with a linux machine with full OS) to make test. |
|
No, the code below does not work for the sustain time (i tried 3 and 10 as values, no change on the sustain time) I am OK with the test, I have a debian test machine available, but I will not have access to the fingerbot in 2 days for some time. |
|
I m with another user that have a device that use raw value, but for him it's sure #7151 (comment) If you have the GUI, can you try to take a look in logs with flag "info" and "ddf" and try the "config/delay" request ? |
|
OK, I am not familiar with the use of the REST API so maybe I have done it wrong. I sent the following command through the terminal after hot reloading the updated DDF (with the delay parameter) : the following error was returned in the terminal : |
|
How have you updated the DDF ? (not something easy on HA) Else for me your request is fine. |
|
There is so much stuff than can be controlled for this device : Koenkk/zigbee2mqtt#17841 (comment) ;-) |
|
Hi all, Can any one shortly guide me (and for sure others in the near future) on how to make it work? Thank you all!! |
|
Hello, have you installed the DDF, what is your OS ? |
|
Hello, @Smanar, As said, I can see it in the deConz application, but i can't see it anywhere else :(
Trying to connect to it scanning new devices, I've managed to "pair" it with other devices (as can be seen in the image above with the green line), but it does'nt appear anywhere. Hope this helps and thank you very much for your help, |
|
You need a DDF to use this device, and as the support is not yet official you need to put the DDF yourself. |
|
Can you try this DDF (if you are using the one in this post for the "_TZ3210_dse8ogfy") You will have a "config/mode" fiel with 3 possibles values
|
|
Thank you ! I updated the DDF by your DDF with deCONZ VNC GUI, but now how to change the mode in homebridge/homekit ? 😅 |
|
Lol, depend of OS, if you have edited the one in the folder /usr/share/deCONZ/devices/ it will be replaced the next time you will update deconz, so no danger to make test with it. No need to re-include the device. If you take a look in the API, for exemple with phoscon/help/debug view/sensor, you will found the new field on the ZHAbattery sensor. To change the value, it depend of third app, IDK if you have a direct access to all fields, else you will need to use command line.
https://dresden-elektronik.github.io/deconz-rest-doc/getting_started/ |
|
Thank you for this valuable information. I made the changes but I have errors. I'm sorry I'm that guy who's not very comfortable with all this. To sum up, I use unRAID. To use your JSON file. I would connect with deCONZ VNC, locate the Fingerbot sensor > Edit DDF > load JSON file and finally I did a Hot Reload. Then I ran the command in the deCONZ container terminal: I thought maybe I'd done the procedure wrong, so I went straight to updating the json file with the help of this message: That's where I'm at. |
You probably have done a typo in the file
You are sure you are using the good ID ? You can check direcy in your browser |
|
Okay, I've started the procedure again. I removed the Fingebot from DeCONZ VNC, stopped the deCONZ container and unplugged the Conbee stick for a few minutes. I added the Fingerbot on Phoscon. I edited the file with nano, this is the start of the file (I write out the file of course): I connected to deCONZ VNC for Hot Reload. Now, If I check directly in my browser, it displays : If I check the DDF in deCONZ VNC, it doesn't seem to use the version I edited: I'm sure this is the right sensor, I have only one with "ZHABattery" and an uncommon name "Battery 44": I don't dare restart the deCONZ container. What should I do? |
You are using docker ? So it's not the same thing. What is your OS ? And BTW, don't use the editor, you can use it to see something, but not not to edit, too much problem. |
|
Yes I'm using docker on unRAID OS. By editor, you mean the DDF Editor in deCONZ GUI ? This was just to show you the json wasn't updated. I went through nano on terminal to edit the file. I restarted the deCONZ container and checked what JSON file was used, this is the correct JSON you provided (preview): Checked API, no config mode: Once again after this restart, the Fingerbot has disappeared from the Phoscon interface, but still presents in the API and deCONZ GUI. On my iPhone the accessory isn't a light switch anymore but returns an accessory with an error "not supported":
|
|
So dockers have special working mode, all is virtual, I think you are using the official deconz docker image ? |
I'm using the official one yes:
I have one file in the folder (the one I uploaded to access through deCONZ VNC GUI) Update: no change |
|
Strange the file is called "fingerbot1.json" but on the editor (on the window title) its the file "_TZ3210_dse8ogfy_fingerbot.json" that is used, and the one on the "opt" folder need to be prioritary. |
These are not the same files.
And to make it even more difficult to understand, here is what is displayed after the restart of deCONZ container: |
|
Your last picture is like deconz don't found DDF at all. For me the better DDF you have is "fingerbot1.json" the one you have in the "opt" folder, but why this one is not picked by deconz ? You can try to load it using the editor, perhaps there is a typo ? |
|
A dumb question, it's possibile to set the fingerbot's arm lenght and timing, just like can be done by Tuya? |
|
Can add a delay with for exemple With value from 0 to 10. For the lenght you are talking about the min/max ? And here I have a new problem, I don't see which one fild to use, can create a config/min and config/max, but I think it will cause problems with existing fields. |
|
Hello, i got a question regarding the way the Fingerbot works. I have a Raspberry with Docker running the official deconz Container and a ConBee II. With the Informations found here and the DDF found there i managed to get my brand new Zigbee Fingerbot to pair. Whatever I klick (On / Off / Toggle ) in the deconz GUI as in my Home Automation Software (FHEM), it works always the way "PowerOn - Auto PowerOff". In the actual DDF is that delay-snippet included already, right? I modified the default value from 1 to 5, expecting that would cause the Fingerbot to stay longer (5 Seconds) in the On Position before returning to off, but it hast no effect. I use it for the DoorOpener of my old Intercom. It works for me, but not for Visitors, as the On-Time is very short. To explain, what I want is a zzzzzzzzzzzzzzzzzzzzzt instead of a zzt - you all know that sound :) This could be accomplished either by a on-for-timer Function (if on would move the Arm down an off would move it up again) of my smarthome, or with a slower return of the Fingerarm. For me it doesnt matter wich way of the two. How would you do that? Thanks in advance! Great Infos and Support here! |
Here we have a problem ^^. It's the "sustain time", so I think it's exaclty what you want ? |
|
Thanks for your reply! Yes I wonder why i am the only one. Pretty sure, the Probleme is in front of screen... :) To be honest, i had a very old deconz Version. Was suprised that it now know Blinds and Thermostaes... hehe.. I didnd dare to touch it, sorry. Now i have 2.29.1 beta. But the behavior stays same. And im still confused: With the new Version, it recognizes the Device. It does not use my JSON file, but one that comes with the update. named tuy/....fingerbot.json. But that hasnt that ["clic", 0], ["switch", 1], ["program", 2] features included. |
|
Ha you are right, the official one is lighter https://github.com/dresden-elektronik/deconz-rest-plugin/blob/master/devices/tuya/_TZ3210_dse8ogfy_fingerbot.json So we can presume you are using native setting, can you take a look on logs when using the config/delay ? (with flag "DDF" and both "INFO").
So ATM you have your json + the official one+ the one from this issue, what is your OS where have you put the DDF ? If you can edit the official one, it's better having only one, and after a change you need to restart deconz (it load DDF only at start) |
|
Hi, im running Raspian 11 bullseye with Docker (official deconz Image). For further testing, now I renamed the official _TZ3210......json in _TZ3210....bak. So now, deconz should always use my fingerbot3.json in opt/deconz/devices (for persitance). Now i took the content of the official file into that place, only chaning the delay default to 5. Restarted deConz and checked if it uses my json now - it does. Behavior is the same: whatever clicked in Phoscon or the GUI, the arm drives down und immidiatly up again. Here is what the Log says:
And here is my json:
|
|
This is fine for me, but I m hopping an error message when you try to use the config/delay , something like "bad format type". |
|
Hmmm. What do you mean with "when i try to use the config/delay"? I just wrote it to the json, hoping it would use the default? Is that wrong? As far as i can see there are no errors, but for me its is extremely hard to follow up that flood of messages, and check if they are from that device / my clicks on it. :( Smanar, are you working at DD-elektronik? Than i bring you the device, its not far from Laubegast! LOL |
Just use the API to change the value, like you have one for the value "5" before. And no ^^, I don't work for DD |
|
Well, I think the Problem is me, not the Device. I didnt use either a API (wich?) nor the VNC-GUI! As written, I just changed the default value in the DDF file. Is that the mistake? If you mean the deConz GUI, there are some buttons in the on/off Cluster Info. Do you mean this? Sorry for Layer 8 Problems! :) |
|
Haaa, so yes ^^. You need to make API call to change the value.
https://dresden-elektronik.github.io/deconz-rest-doc/getting_started/ |
|
I tried. Read the getting-started-doc. I found the Sensor and the API Key in Phoscon/Help. Using the suggested curl command gave me an error:
Still not knowing what i do I assumed, that duration not exists, because its named delay. So I used delay instead of duration, and it seemed to work, givig me a success message:
(Why 900? is it millisecs? I tried 4000 too to be sure) Phoscon recognizes the change:
The "Event" Tab in Phoscons help says after clicking toggle Button in my smarthomes GUI However, the behavior stays same: Arm gos down and up agin within one second. :( |
|
"Config/delay" take a value from 0 to 10 (in s) |
|
Now im really confused. So what is the suggested 900 for? And, however, I tried 4, 5 400, 900, 4000 .... nothing had any effect. So I think i drive the wrong screw, or a needed prerequisite is missing. After searching the web, for me it seems to be a question of "mode". In a youtube video about the device, its behavior was described as follows: It has modes Click, switch and program. And in the click-mode, it act like mine: whatever you press (on, off or toggle) it just clicks and return arm to off. As the mode parameters was described here before, I tried to change the mode. As the JSON earlyer here did not work for me, i just took the part with the mode and put it in my JSON and restarted deconz. After that, i wanted to set the mode with the curl command mentioned earlyer here, but it responded an error:
Without knowing what i did, i mentioned difference in Phoscons output:
It dos not say mode: 0, it says mode: null. In the Phoscons Event Tab it says unchanged mode: 1:
Does all that says anything helpful? |
|
The "config/duration" = 900 was just a sample from another device ^^
You probably miss this part The "config/delay" is working on the "clic" mode, so you have the good one, with a 1s delay the device need to return back after 1s, else can be 10s. |
|
You were right, I missed that part. Now I can set the modes clic, switch and program. But that dos not change anything. Whatever mode, whatever delay, Arm moves on and off in a second. After one week try and error and watching lots of Youtube Videos about Zigbee and Fingerbot im little frustrated. Think I will buy sonoff stick and give mqtt2zigbee a try, as i do not have an idea what else to try next. :( However, thank you very much for your help! |
i first add new switch in phoscon, then press pair in device, no response for 3 mins, but when i go to decoz, it appear as 0xXXX, i click on it i can control the on off, but not appear at phoscon so also not in HA.
The text was updated successfully, but these errors were encountered: