Tuya BLE integration, includes fingerbot

Third party integrations
184

I have to say, I failed.
I used this fork : GitHub - ha-tuya-ble/ha_tuya_ble: Home Assistant support for Tuya BLE devices, attempting to consolidate all of the active forks. Unstable quality

It already contained Fingerbot Touch ID even if just as another Fingerbot.
I was able to add the device but the switch control was all the time unavailable.

I tried to fork myself, modify a bit the exposed things and dp_ids, but the result was the same. Switch unavailable :frowning_face:

So I made a complete step aside :wink:
I bought for 8 dollars super cheap Tuya bluetooth-only gateway. Connect the Fingerbot to it, disable internet connection at firewall and via LocalTuya integration (GitHub - xZetsubou/hass-localtuya: 🔹 A Home Assistant integration to handle Tuya devices locally "fork from localtuya") it works perfectly fine, both buttons :slight_smile:

185

You could have also just bought a zigbee fingerbot. They are also cheap and independent of any cloud. But of course it depends if you already have any zigbee infrastructure running.
In my case there was no other option because these switch robots only exist with bluetooth. Believe me, I have searched for 1 year.

186

Well, unfortunately not. I tried but did not found a Fingerbot Touch in Zigbee version. I need the touch version.

187

Not necesaarily quick delivery but isn’t this Amazon item Zigbee Fingerbot?

188

Sure.

But still, not the Touch version.
This one:
https://www.aliexpress.com/item/1005009650743374.html?spm=a2g0o.productlist.main.3.1b7d10240X9tdN&algo_pvid=16b2929d-1f84-4526-92aa-752a3334015e&pdp_ext_f={"order"%3A"-1"%2C"eval"%3A"1"}&utparam-url=scene%3Asearch|query_from%3A|x_object_id%3A1005009650743374|_p_origin_prod%3A

2 Likes
189

Hey. I got the exact same switch. Can you please describe in more detail what exactly did you do? I only get connection data in HA, can’t control it. I read all your comment but I still don’t quite get it. Thanks!

190

Nvm, solved. tldr: just add the id “4ctjfrzq” into ‘kg’ section in devices.py, switch.py, sensor.py, number.py, and select.py. For current version (I used GitHub - garnser/ha_tuya_ble) it goes below “riecov42”. That’s it. It basically works out of the box, just need to add the device id to that integration, controls are the same as for other fingerbots. You don’t need a tuya BLE gateway, or a bluetooth enabled in HA (I use bluetooth proxies, they connect just fine).

I spent some time tinkering with the api, turns out I didn’t even need to, since controls are the same. Tuya’s api platform is a mess btw.

1 Like
191

Yeah, found out the same. I had to disable some of the code though, so that auto-reconnect is disabled due to some reoccuring disconnection of the device (“2025-09-02 11:13:14.983 WARNING (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] DCxxx2: Device unexpectedly disconnected; RSSI: -102”. I don’t want it to “stay online” (which has the backdraw that you don’t know the state always. But I don’t care, for me it is more important that I don’t pair every 30 seconds just to loose the connection again.

Did you experience the same issue with disconnection?

192

Kind of. It does disconnect sometimes, but I didn’t debug it yet. I figured that my bluetooth proxy drops connection to the fingerbot sometimes for some reason. Before I saw your message I thought that the problem is in bluetooth proxy.

I moved the fingerbot to be close to the proxy, it works flawlessly since (which might be a coincidence, since I didn’t use it for long enough to see if it really is fixed now), I didn’t need to modify anything else in the code. I never had to re-pair it etc, it just works.

1 Like
193

If you enable debug you see that it happens very regularly. That’s why I decided to do something against it and I was not able to fix it in a good way. So I removed the whole “re-pair-on-disconnect” logic. Which is okay, if you just want to turn it on and off sometimes.
I have no issues with that and this will be fine for me.
At the moment I added some functionality in an automation to check if the state was changed or if the connection was broken. If it breaks I want to automatically send me a message or something as this is a crucial automation in my home.

194

I can’t get the component to add, did you need to do anything special? It always tells me the username/password is wrong despite I just used it to login

195

I just followed the manual, it worked

196

Still cant get it to work; created a new project, changed my password; nothing works…

Is there a way I can extract the details from the existing tuya integration>

197

thanks Eugene! I totally forgot about this thread. I will give it another go and see if I can get it to work.

Sorry for the late reply.

199

I have updated the dp_id to match my lock, replaced the product_id with my one but when i try to add the integration, it just shows no unconfigured devices found.
is there anything else I am missing? I am using ESP32 bluetooth proxy and there is one right next to the lock. My phone has bluetooth disabled.

maybe i need to put the lock into pairing mode? my lock (dead lock replacement) only has a finger print reader on one side and there is a physical lock/unlock button on the other side of the lock. Not sure how to put the device into pairing mode.

I was able to pair it to my phone when i initially installed the lock as it went into pairing mode automatically when the batteries got put in.

200

Do I understand it correctly that these tuya ble device work natively over esphome proxies?

201

@Eugene-Musika
I have adopted your changes from Github for HA 2025.12.x
So Tuya BLE starts on my Home-Assistant. After I setup the login details Tuya BLE found my device TY 2D750C but I always gor “Divice is not registered in Tuya cloud”. In the Tuya Developer account I can see this device. So were iI did wrong? It’s a MOES hummidity temperature and light sensor.

202

Sorry, I’ve only added support for specific ble lock. Probably you should ask the author of original extension

203

@Eugene-Musika Hiya mate I’ve just installed your fork as a custom repo onto my HA and managed to link my lock. However my clicking the motor state doesnt do anything. It doesnt unlock the door. You can find screenshots below:

image
image1481×834 98.4 KB

My DP ID:

{
        "code": "bluetooth_unlock",
        "custom_name": "",
        "dp_id": 6,
        "time": 1766223671589,
        "type": "raw",
        "value": "AQE="
      }

Tuya Dev Account Details:

### Device Information

Product Name: smart lock
Device ID: bfce4fybk39fiam7
Product Category: ms
Device Status: Offline

I use an esp32 ble proxy that is placed 1m away from my lock. My signal strength varies from -74 dBm to -83 dBm

I’ve noticed that it reports the battery correctly and changing the lock volume also works correctly. It’s just the unlocking part that isnt working.

Any help would be greatly appreciated :pray:

204

@avigrinberg In Add support for Gimdow A1 Pro Max smart lock (experimental) by google-labs-jules[bot] · Pull Request #93 · ha-tuya-ble/ha_tuya_ble · GitHub I have added basic support for rlyxv7pe; but untested with an actual device. If you have the time to trial that and see if its mapped right or provide DPs on the relevant github issue, may be able to get that working for you.