Tuya BLE integration, includes fingerbot

Hi, thanks for this
Is there a different version of this lock or are they generally the same one ( MQC2HEVY? I’m looking at this one
As for programming/managing the fingerprint and passcode, I would still need to use the tuya app?

hi! do you have a list of everything that needs updated to support other locks? below is my device info (mac, udid and local key deleted for privacy):

{

"address": "",

"uuid": "",

"local_key": "",

"device_id": "ebe6edxsbv4eevaa",

"category": "jtmspro",

"product_id": "lssvih8b",

"device_name": "EC_C02",

"product_model": "C02",

"product_name": "EC_C02"
}

and these are some values i see in tuya device control query. there are many other values, but i’m not sure which ones would be needed:

{
        "code": "unlock_ble",
        "custom_name": "",
        "dp_id": 19,
        "time": 1748152861000,
        "type": "value",
        "value": 1
},

additionally, i am using esphome ble proxy. where does the following go?

bluetooth_proxy:
  active: true

@Eugene-Musika hi, is there a way to add a lock? https://aliexpress.ru/item/1005002476108470.html ? I can provide all the data
“product_id”: “hc7n0urm”,
“device_name”: “A1 Ultra”,
“product_model”: “AT1”,
“product_name”: “A1 Ultra-JM”

Hi, I’ve tried many tuya ble integrations, some works with one devices, some with other… so for now I use silvanfischer/tuya_sensors: HomeAssistant Integration for TuyaCloud Sensors (also unsupported ones) , yes its cloud based, but its work for example with Petoneer Smart Odor Eliminator-Pro (agwu93lr), and Arm Blood Pressure Monitor (ptbvoydj), The only thing I regret is that chip from Petoneer smart Dot was dismantled too early to test with this component.

Hi! I believe the product IDs for these locks may vary from model to model, but they generally share the same functionality. To confirm, you’ll need to obtain your lock’s product ID from the Tuya cloud. Additionally, if you ensure compatibility, you can share your product ID with me so that I can add it to the integration, which will reduce the workload for others.

My lock supports offline fingerprint and password adding, but I’m not sure about yours. To add a password or fingerprint, press 1, then #, and enter your admin fingerprint or password to confirm. The first password and fingerprint added are by default admin. After that, you can add new ones. However, if you want more features like adding temporary, scheduled, or one-time passwords, you’ll need the Tuya app. I haven’t figured out how to manage these types of features through HA integration.

If you have a lock with the same model as mine, you can quickly test it by replacing my product ID (MQC2HEVY) with yours in all the integration places. However, if it’s a different type of lock, I’m sorry, but I can’t assist you with that.

IIf you’re already using the ESP Home ble proxy, you might not need to edit anything. However, if you have custom functionality on your ESP board that’s not just a ble proxy and you encounter some issues, I recommend visiting the ESP Home website and reading the documentation about the ble proxy mod. I’m not an expert user, so I occasionally add some ESP boards and read the documentation each time.

Hi!

Short answer: No.
Long answer:
That’s quite a different lock. It has a physical rotation mechanism. I could attempt to add support for integration, but it would be a significant undertaking with numerous iterations. If I had this lock personally, it would be much easier to implement and I would have more motivation to do it😅

Good evening, can we write to you in a telegram? I’m from Russia, I can send you a lock for testing.

Hi,

have the Lock to be in any Bluetooth Paring Mode to get discovered by HassIO or is it accessible automatically?

I get the message “No unconfigured devices found.”

Is it not possible to configure the device manually by hand? I have all needed parameters from TUYA Cloud.

Your hint to use IoT Core => Device Control => Query Properties was a game changer at all. But i am not able to unlock the device from IoT. Do you know how we can unlock the device via IoT Core - Device Control?

This command does not what i want it does.

Hi!

I’m not sure but better switch it to parring mode by unlocking it with fingerprint or password. Also better to disable bluetooth at prev paired device like your phone or tablet.

No, you can’t unlock it from IoT. Only from directly paired device. It’s some sort of security measure.

@Eugene-Musika Bro, will you answer in person?

Sorry, I live in another country and can’t help you

Sorry, but where is my misunderstanding?

On my TUYA Smart App i am able to do unlocking from everywhere with my BLE Cloud Gateway.

So it must be possible to issue a command to the TUYA Cloud, to send the open-command to the BLE-Device (Lock) ?

Or does the App directly communicate with the BLE-Gateway?

Hi, I try to get a new “Switch Robot” (SB02 (4ctjfrzq) ) to work.

I got it imported via Tuya BLE integration.

What do I need to debug where to find out how to kick the switch? Should be similar as fingerbot, right?

these are the results of api explorer device details:
{
“result”: {
“active_time”: 1752573727,
“bind_space_id”: “163197435”,
“category”: “kg”,
“create_time”: 1752572147,
“custom_name”: “”,
“icon”: “smart/icon/ay1550298204274iXb1I/07eaeb7d9e251a6d36292410c021bbb8.png”,
“id”: “bf9554wbyhstanfz”,
“ip”: “”,
“is_online”: false,
“lat”: “50.13”,
“local_key”: xxxxx
“lon”: “8.71”,
“model”: “SB02”,
“name”: “Switch Robot 2”,
“product_id”: “4ctjfrzq”,
“product_name”: “开关机器人”,
“sub”: false,
“time_zone”: “+02:00”,
“update_time”: 1752573728,
“uuid”: “uuidedf0b2f2f0e9”
},
“success”: true,
“t”: 1752584625104,
“tid”: xxxx
}

Hi guys,

Can someone provide me some hint? I consider myself experienced user but I am not able to make the FingerBot Touch work. Not passing through adding the device.

I can see the BLE device in HASS, it is even recognized by the integration.
I created the developer account, link with Smart App and got the value.

But failing to pass with and “Invalid flow specified” error.

I am getting out of the idea, I found nothing usefull in HASS log.

okay, got it to work for the switch robot (product id 4ctjfrzq ) . it was similar to fingerbot plus.
What I learned:

  • Tuya is a mess.
  • I don’t need an ESP32 bridge or something similar.
  • I already had a bluetooth dongle on my home assistant installation (due to some other bluetooth sensors that were easy to integrate). So Xiaomi is easy and tuya complicated.
  • zwave and zigbee are always easier to integrate if you have the first of them running.
  • put it into your tuya smart app first. then it will be found locally and can be spoken to locally.
  • it seems like thie tuya BLE disturbs some other components that are without this integration running fine. This is in my opinion a big no-no.
  • Learn how to use the api portal / developer portal of tuya and you can find all the DP ids that you need to understand how your device works internally.

It is a little tricky. I can help you with that.
Just go to Tuya Smart Developer Center and open your cloud project (if it exists)
For me it says:
Industry : Smart Home

Creation Time : 2023-08-09 16:20:18

Data Center : Central Europe Data Center

Authorization Key

Access ID/Client ID: eiroqwiort4e9wocvmzpc8

Access Secret/Client Secret: ********************************

Project Code: p1691589657563rt77xw

and your account data is the stuff you put into your tuya smart app (not the one of the cloud platform login!)

I managed yesterday evening to connect.
The problem was not Tuya portal but somehow the Bluetooth connection. I let the device for a while off charge just on battery, then connect again to USB and it passed.
So now I can see the Fingerbot Touch in HA but of course only signal strength as the device is not supported.

Once I have some time I will try fork the repo and maybe I will find a way how to add it.

you will manage. Basically it is just about adding the product id to everywhere, where another device uses the same dp_ids. Then you see the entities and can pivot from there.

Let’s see :slight_smile: But earliest in two weeks.

The difference is that the Touch has two buttons/switches not just one as other Fingerbots.

Btw, do you have some recommendation which fork to use, some to be most up to date? The original one is not much maintained.

1 Like