Yet…it should be implemented in the future, let’s hope it will happen in 2025 
It’s not about the surface size, it’s rather about direct distance to the Homey and eg. direct visibility. In case of Homey 2019, it was working for me flawlesly in distances of 5-8 meters, even behind the wall/glass doors. Now with Homey 2023, the bluetooth is broken but I saw it’s still working for some users.
Not yet…
But it’s OT for this thread, unfortunately 40 EUR for plant sensor, that’s little bit too much.
Yes, lets hope so. Sadly im a rather impatient human being. So I won’t wait on that. 
Yes there always be something blocking the signal.
Yes that’s true. In this case I also paid around 40 euro for Xiaomi Max (which is secretely the cheaper one). So that doesnt make much different with the Elho.
But I need 5 or 6 of them if want to cover all big plants, so that’s a bit out of line. On the other side, buying new plants caused by neglecting them isnt cheap also.
I’ve contacted support to ask for a status regarding the BT issues. I’ve got their reply:
Me and alot of other users and the app developer from the Xiaomi Mi flora App and or sensors are waiting so long now for a fix. The issue persist for almost 2 years now.
Developer Koktail cannot help people with non responding sensors because it’s stack related.
Is this issue still investigated?
I have alot of these sensors but they are useless for Homey. The developer has put alot effort in the app. Even made widgets. But it can’t be used because Homey is failing to much.
[APP][Pro] Xiaomi mi flora sensor/ropot app - #767 by HomeAut
Sep 2024
Homey BLE stack gives an error:
“Method “Connect” with signature “” on interface “org.bluez.Device1” doesn’t exist”
I have no influence on that unfortunately.
I hope you can give me and the other users a status update.
Thanks
The reply I got from support got 8 weeks later:
Hi David,
Thank you for contacting support.
We are aware of the under performance of BLE. Unfortunately this is an issue form the Raspberry PI and we couldn’t change this. I’m sorry for the inconvenience.
Have a nice day!
Best regards,
Daphne
So it looks like it is not going to be solved.
I think it is unfair to still sell it with BT support if the whole thing doesnt work…
Hmm, I don’t recall Raspberry selling CM4 with * at the Bluetooth* functionality with comment :
*Beware, it’s not working as it should, but you will pay for it anyway
Anyway, thanks for sharing ! If that’s the case, I would probably not be so patient last year waiting for some solution.
Did you have any contact about this issue from a developers perspective?
Can you ask him or her again for an update ?
Sounds strange to me if this is just left for what it is.
Hi all
widget is not showing anything. Could someone help?
@Koktail thanks for listening !! 
Finally getting some data after quite a long time
Version 4.4.0 — Add app settings option to update sensor values based on advertised service data
Nice! What exactly does “Add app settings option to update sensor values based on advertised service data” mean? Is it working stable in Homey 2023 now?
If you don’t check it, then the app/Homey tries to connect back to Flora sensor - so really establishing connections, which require “better” signal while in case of “waiting for advertising” , Homey just wait if any Flora device advertises it’s state and then process the signal. So in first case, it’s initiated by Homey, in 2nd it’s dependent on the advertisement made by Flora device itself.
I would say it’s temporary / partial workaround, which might help for some - anyway, you can revert back even for now seems that the Conductivity data I’m getting are slighly different.
Cheers for the answer! 
Great news!
I’ve just published a new test release to the store:
This experimental feature is created to increase the amount of updates to the homey characteristics (temperature/luminance/moisture/nutrition/battery) by reading that information from the advertising data.
Note that this feature requires the latest update from your sensors and that this is an opt in in the device settings. When enabled the sensor data is still being actively pulled from the devices based on the update interval.
Hi @Koktail, I hope you can shed some light on the following.
I am using a flow to check whether sensor values are below their threshold. It uses the flow card that fires when a sensor value is below its threshold and then checks which sensors it regards for further processing (e.g. a timeline message).
Currently my plant is both low on moisture and nutrients. This is also displayed as such in the plant’s widget (both items have an alarm/exclamation mark).
However this flow seems to only catch the moister alarm, not the nutrients alarm. I don’t onderstand why.
Either the WHEN card is only triggered once and hence only addresses the first sensor, or something changed in the Dutch sensor names (and I am using the incorrect name). Perhaps the latter is a result of my prior post: [APP][Pro] Xiaomi mi flora sensor/ropot app - #815 by SunBeech. Or maybe it is something else…
Have you got any idea what is going wrong / what I am missing?
To answer my own question: my flow did not recognize the out-of-bound nutrition cases anymore, as the sensor name has changed: from voedingwaarde (without an ‘s’) to voedingswaarde (with an ‘s’).
I did note something else: when I enable the new option to have Homey update the sensor values based on BLE advertisements, the above flow (and also a similar flow that is triggered by sensor values that are above the threshold) is deactivated by Homey, as the flow is triggered too often (device_sensor_threshold_min_exceeds). Within 1 second it gives me approx 15-20 of the same sensor notifications. Note that my plant sensor is on firmware 3.3.6; the latest available.
I fixed that in 4.4.4, the update interval was set to debugging values.
There is a new firmware with bluetooth changes:
BLE
Fixes an issue that could cause Homey Pro to crash due to receiving a malformed BLE message.
Fixed a problem where Homey could accidentally disconnect from devices.
Improved how Homey handles devices that are no longer available.
BLE
Fixes a problem where Homey could get stuck in a discovery state.
My sensor working now a lot better
This indeed seems like really good news! I’m too afraid to migrade my 50 sensors back to Homey from HA yet though. But will listen in closely on if the fixes corrects the prior faults. Might transfer some sensors from HA just to try hmmmm..
Cheers for the news!
The new feature that listens to BLE advertisements to retrieve sensor data works great. Updates are more frequent, and it significantly improves battery life on the sensors. The Home Assistant integration for these sensors work in the same way.
