Hi guys,
I am having problems with BLE Fingerbot - it integrates smoothly but then it is not possible to control it (even from 1,5m distance). I am getting these messages:
Any idea how to fix it?
Many thanks
J.
You could try sending the log. Open the app settings page and select the Log tab and set the log level to Detailed Information.
Then try and control the bot and wait for at least 30 seconds. Then go back to the app setting page and an send the log. I will check if anything is not correct but to be honest, Homeys BLE is not good.
Just sent the log. If anything else is needed please let me know. Many thanks for your kind help. J.
It looks like Homey is having problems. I will send the information to Athom as they need to know just how bad Homey BLE is.
One thing you could try is rebooting Homey.
I have tried this. Does not help at all… 
Same problem here
All I can suggest is to either get a SwitchBot hub or try the ESP32 integration mentioned in the first post of this topic as basically this is a Homey hardware or firmware issue.
I am experiencing issues with the Switch-Bot plugin on Homey. It seems that the status changes of my K10+ vacuum are not working properly as a trigger.
To test, I created a flow that increments a variable by +1 every time the status of the K10+ changes. This allows me to check how often the trigger actually activates. What I notice is that this trigger only works occasionally and not with every status change, as I would expect.
Additionally, I see that the translation to Dutch also gives different tags for the trigger and the “And” condition. Could this be related to the problem?
I am using the K10+ vacuum in combination with a Hub Mini 7E.
HP2023(Version 12.1.2) - Switch-Bot plugin (Version 2.0.4).
Could you open the app settings page and select the Log tab. Then set the log level to Webhook and monitor the changes in there. The K10+ should send a webhook message each time the status changes.
It’s possible the tag value is the value reported by the K10, whereas the trigger list translates the id to a language specific text.
1 Like
Update: connecting mini hub (for around €10) solved all the issues, even 10m distance is not an issue. Guess Homey ble is a yeti 
1 Like
I fully agree. The BLE-solution inside the Homey is close to not usable. In my house I have 3 of these ESP32-hubs from @Adrian_Rockall and the “pain” has gone. It works great.
2 Likes
It’s clear that BLE solutions with Homey Pro are almost useless. I’ve had my share of problems with BLE sensors.
I had my eye on SwitchBot Blind Tilt controller, so the question is anybody using these and how are they working and secondly is there any way to use them through Homey without using BLE?
I have 3 of them in my kitchen and they work well. I use them with my ESP32 modules, but they also work well with the SwitchBot hubs.
Thank you for the answer. Have to order one and test it out 
1 Like
Looks like this is working again!
1 Like
@Adrian_Rockall could you take a brief look at this request, maybe it makes my remote less useless;)
Hi Adrian
Thank for the great app. I have curtains, hub, the meter and tracker card running via your app.
I also have the remote. I know you looked at it and did not see much value yet.
After playing around with it, the following idea popped up. Is it possible to make next to a “then” card also a “if” card for scenes?
This way we can couple the remote to homey.
Remote triggers scene. Scene triggers flow. Flow triggers device. (If scene xxx then lamp on)
Not the most efficient way but maybe something to consider?
Greets Gijs
1 Like
Unfortunately scenes don’t send notifications, so there’s no way to know when they are run.
But that doesn’t come through the API.
A check thanks!
