To apply that fix we need to manually download these files
And replace them in custom_components->ble_monitor
Is that correct?
That is what I did. Kinda. I just copied and pasted the content of these files from the fix to those I already had in the “custom components” but I am sure that just replacing them with the fix would work also.
I got the same problem now. Worked to begin with, then it ran out of battery, went offline and I’m not able to reconnect now. Found any solution to your problem?
Hello, I have come this far because I recently acquired a cubetouch, the model that is supported, and my question is the following, would it be feasible to be able to control this without having Bluetooth on the machine?
I have the machine in a storage room and I do not have bluetooth, what I do have are several bluetooth proxies with Esp32, is it viable to make it work this way? There is some documentation about it.
Thank’s
Has anyone experienced this while trying to install TUYA BLE?
Config flow could not be loaded: {“message”:“Invalid handler specified”}
I experienced that issue and solved it as described here:
This does not work for me on last HA version, do you know how to fix it? it find the device but says the device is not registered.
after you did the registration and it complained about “device is not registered.” did you still get a non working device added?
if so this is what worked for me to get it to work just follow the instructions here to get the local key (on the bottom of the page)
https://community.home-assistant.io/t/get-local-key-tuya-since-june-2022/436399
and then open .storage\core.config_entries
find this and change out the local_key for the one you just collected
` {
"entry_id": "9b6a42446d74608d93f5698aeb3e90fb",
"version": 1,
"minor_version": 1,
"domain": "tuya_ble",
"title": "door unlock",
"data": {
"address": "DC:23:50:24:86:0E"
},
"options": {
"endpoint": "https://openapi.tuyaeu.com",
"auth_type": 0,
"access_id": "xxxx",
"access_secret": "xxxxx",
"username": "xxxxx",
"password": "xxxxx",
"country_code": "46",
"tuya_app_type": "smartlife",
"address": "DC:23:50:24:86:0E",
"uuid": "51e6434394xxx",
"local_key": "V>`O*xxxxxxxx",
"device_id": "bf2f9065dd1523xxxx",
"category": "szjqr",
"product_id": "xhf790if",
"device_name": "door unlock",
"product_model": "CBTB3002",
"product_name": "CUBETOUCH II"
},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "bluetooth",
"unique_id": "DC:23:50:24:86:0E",
"disabled_by": null
},`
after that it just worked for me best of luck.
Hi everyone,
Using your wonderful job, I managed to have my cubetouch working, using a “esp32 BLE Proxy”.
First of all, thanks a LOT for this.
A question remain, I don’t know how I could have a “direct” button to activate them…
When trying to add them to my dashboard I have this :
So, I use “add to dashboard”. Home assistant suggestion is :
The only way I found to activate my cube is clicking on the button , the “log journal” appear :
and then I can activate my cube with the “push” button (appuyer) on the right.
Any chance to have a direct bouton?
Hope I explained it right… I’m french, as you can see. 
Thanks
Hello @fff41,
Your message is perfectly easy to read, I’m french too (from Quebec).
You need to get the Push entity ID. Click on your Push entity:
Click on the gear icon to see below:
My Push entity is called button.fingerbot_vrc_push, copy yours in your pastebin
Then you can go to one of your dashboards, modify it, add a new button, and paste your entity ID
Is it working?
It worked ! thanks a lot 
1 Like
How do you factory reset the device?
I am curious how you had / have this working “not locally”. I have two fingerbots that work fine from the Smart Life app on my phone. I can connect them to Home Assistant via the (cloud) Tuya integration but they show up as ‘unavailable’. I am not surprised because they connect via Bluetooth, not WiFi like my other Smart Life devices. So how are you connecting to them? Is Tuya somehow using your phone’s Bluetooth?
I abandoned it some time ago so i dont remember details. I managed to add them to home assistant and it was working but as i said i abandoned all.
You can try zigbee finger bot. It does work but battery consumption is high. Also abandoned and looking for another solution.
I do have an alternative solution: Switchbot fingerbots. They are easily set up in HA using the SwitchBot integration.
However, I still have two Cubetouch fingerbots and it is frustrating that they work perfectly well from Smart Life but I cannot get them to work with HA.
I think i got them working using tuya integration. They were connected to some tuya hub i bought who knows when for who knows what.
One burned out, another broke so i bought zigbee version. But frequent unresponives and high battery consumption made me to abandon all.
I used it only for fireing up dishwasher and washing machine.
Dishwasher will very likely be replaced with wifi one and washing machine have no future plans for now.
1 Like
Ah! That answers my question, but I don’t have one. I want to use ESP32 Bluetooth Proxies.
I tried to do something with bluetooth but didnt make it work. I managed to get some data out of it but it is just too much work and hassle.
If you have some other alternative better try that than fingerbot. It will work for a year maybe two at the most if you using it regulary and then you can trash it. At least that was in my case.
1 Like
EDIT: Nvm someone already figured this out before me: Device is not registered in Tuya cloud · Issue #119 · PlusPlus-ua/ha_tuya_ble · GitHub
For anyone still getting Device is not registered in Tuya cloud:
I tracked down the problem and seems like Tuya changed something about the API endpoint getting the device MAC address, which is critical for Home Assistant to associate the physical device with the local key from the Tuya Development Platform. The author of ha_tuya_ble has borrowed the code from tuya-local-key-extractor, which currently has the same problem.
I have updated the two repos to adapt the change. After this I was able to add the BLE device and it’s functional.
1 Like
Hi,
Is it possible to set up different automation to have different “press” time?
I would like one script to press 1 sec, and another one to press 3 sec.
How can I do this?
Thanks a lot.