I’m curious about the status of this. I was able to integrate the same fingerbot as @ddaniel in 30 sec in the tuya smart life app, Home assistant sees it but… its shows as unavailable…
Try to pair it again. Or check it in tuya iot. Ha is getting data from tuya iot. If there is fingerbot unavailable the same thing will be with ha.
I think it becomes unavailable because it is Bluetooth and goes to sleep somehow.
I purchased the aquara mini switch (which is a button switch) and I use it to activate the Fingerbot. I had it working for a while but the problem I find is that even if you try to readd the device, the old entities remain in HA.
Also, because the Fingerbot shows as unavailable in Tuya until I actually open up the device’s settings in Tuya (ie: if I’m scrolling through my devices in Smart Life, it will show offline but then if I click on its device settings, it takes a moment or so but then it comes back online once it is awoken), the aquara switch often doesn’t work, even though the automation in HA will show it was successfully triggered.
These fingerbots need a workaround. I have four of them, all different brands, and none work properly or stably.
1 Like
I don’t have that experience. I have two tuya fingerbot switches and they are working perfectly fine. They are always available in smart life app. If they are not available in smart life app than something is wrong with your config. Maybe tuya gateway is loosing connection or have weak connection. Or connection between gateway and fingerbot is weak.
Someone did manage to make a local way to control it here.
https://www.reddit.com/r/homeassistant/comments/10ogtbt/tuyaadaprox_fingerbot_to_home_assistant/
wonder if someone could make an addon to make it easier
1 Like
Has anyone with a Fingerbot already tried this recent custom component?
Thanks in advance for providing feedback.
I guess it’s just a matter of retrieving device ID and encryption key. Anyone had success with that?
Yep - working - with no hub 
1 Like
How did you retrieved device IDs and encryption keys?
So basically steps goes as follow?
- Install Tuya Integration (I already had the Tuya integration running)
- Install the custom component ha_tuya_ble (GitHub - PlusPlus-ua/ha_tuya_ble: Home Assistant support for Tuya BLE devices)
- Add the fingerbot
Are there missing steps here?
Official Tuya Integration is optional.
My integration just uses the same set of credentials as Official Tuya and can import credentials from there.
Good to know! I will order a couple fingerbots now that the ha_tuya_ble pugin is working!
So basically with ha_tuya_ble you don’t need to go through a script to extract device_id , uuid , local_key , mac_address with tuya-local-key-extractor ?
Just install the custom component ha_tuya_ble and fingerbots will be able to work without hub?
Yes, exactly.
Devices must be added to Tuya cloud, but it could be done without hub, just by direct Bluetooth connection from the mobile.
You have also pay attention to stability of connection between the device and your Bluetooth adapter.
The Tuya BLE integration can also work via Bluetooth Proxy, I’ve tested it with ESP32 one ESPHome Bluetooth Proxy
1 Like
Ah, brilliant!
I’ve also set up the ESP32 ESPHome Bluetooth Proxy, but it’s not clear to me what and where I need to configure, or if the devices are visible on the proxy. It’s only been added to Home Assistant, and I don’t think it’s doing anything. By the way, it’s located 1 metre away from the Fingerbot, while my Raspberry Pi 3 is 5 metres away.
The process of flashing ESPHome for the proxy was agonising on Windows. Not at all simple - actually, quite the opposite. It can’t be done in WSL2 because it doesn’t support USB, and the flash must be done via USB, etc, etc.
Also, now, the ESPHome OTA firmware update on Home Assistant is always a 30-minute ordeal.
I don’t know what your experiences are like and what does your ESPHome config file look like?
Mine looks like this:
esphome:
name: esp32-bt-proxy
esp32:
board: esp32dev
framework:
type: esp-idf
# Enable logging
logger:
# Enable Home Assistant API
api:
password: ""
ota:
password: ""
wifi:
ssid: "---"
password: "---"
esp32_ble_tracker:
scan_parameters:
interval: 1100ms
window: 1100ms
bluetooth_proxy:
active: true
It would mean a lot if you could check your .yaml file for BTProxy and tell me where I’m making mistake.
It’s been 2 months, and the ESPHome just sits there doing nothing.
When I look at its log, it definitely doesn’t detect any BLE devices…
I’ve just flashed my ESP32 using the site, no modification or tuning. I don’t know how HA Bluetooth subsystem chose a way to connect the device.
My HA runs on an old AMD x64 based mini-PC with built-in Bluetooth adapter. When I setup soil moisture sensor which is in 15 meters from PC and in 5 meters from ESP32 proxy, HA connects it via proxy.
I have the same problem. I have BTProxy setup and running without issues but it doesn’t seem to actually do anything.
In my case I have builtin bluetooth on the PC running Home Assistant but it isn’t detected at all by Hassio (likely a bluetooth driver issue) PLUS the BTProxy (which is running fine).
I wonder if we need to have a working BT dongle besides the BTProxy for it to actually work?
As far as I know - no. During development of the integration, sometime the virtual computer with HA wasn’t connected to the BT adapter, but a device connected via proxy continued to work properly.