I want to set up a Mi Flora sensor, connecting with my HA install through BT proxy.
I’ve flashed my ESP32-WROOM-32 (AZDelivery) with ESPHome, with the following config:
I do see some messages about discovered devices, but none of them are from my MiFlora sensor.
The sensor is working, when I place it near my HA Pi4, its detected instantly, I can also pair it with my phone. (for now, its not paired).
I’ve also tried using an OpenMQTTgateway on another (same model) ESP32, this unit also does not see the BT messages from the sensor.
I suggest you use a static address for the BT Proxy. This is my config that detects Mi flora:
substitutions:
name: "esp32-bt-proxy-4bfc5c-kontor"
packages:
esphome.bluetooth-proxy: github://esphome/bluetooth-proxies/esp32-generic.yaml@main
esphome:
name: ${name}
name_add_mac_suffix: false
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
manual_ip:
# Set this to the IP of the ESP
static_ip: 192.168.0.120
# Set this to the IP address of the router. Often ends with .1
gateway: 192.168.0.1
# The subnet of the network. 255.255.255.0 works for most home networks.
subnet: 255.255.255.0
hello.
I flash the esp32 with esp32dev-ble-datatest
Put the esp32 near of my 2 miflora devices with firmware 3.3.6 and 1 with 3.3.5
I open mqttexplorer in windows and look for “home/OpenMQTTGateway_ESP32_BLE/BTtoMQTT”
and i can see some devices. one of them is the miflora with firmware 3.3.5
BUT i cant see any of the 2 devices with firmware 3.3.6
yes!
i can see in nRF Connect:
the red boxes are the devices with firmware 3.3.6. this i can connect to esphome
the green boxe is the device with firmware 3.3.5 this apears perfectly in HA with bt proxy
both of them i can see in HHCC app and obtain data
Thanks, so the 3.3.6 is seen with null values by ESPHome, doesn’t appear with BT Proxy, nor OMG if I get it, but you see them with nRF.
From nRF Connect, could you click on them and share a screenshot of the service data, please?
hello
sorry i forget your reply.
I have one esp32 with bluetooth proxy thant detects perfectly a myflora with firmware 3.3.5 working perfectly with home assistant.
this esp32 have enabled the esp-idf (i flashed with the cable following a tutorial)
This esp32 detect the 2 myflora with firmware 3.3.6 in home assistant. but not data
the test that i send to @1technophile was done with other esp32 with the firmware that he say to me in the other post.
i think the problem is this new 3.3.6 firmware, thant maybe is too new o maybe the cut functionality
after 10 minutes, not apears in mqttexplorer. i will wait more…
Nop.
Apears a lot of Mac address like the other myflora, ble keychains, tvs, etc… But not the conflictive myflora.
The ble is at 50cm of the myfloras
Today i go out home for 5 days. When i return i Will make more test.
Thanks!!!
I have an issue like @DAVIZINHO with BLE proxies and thus I am interrested to any progress on this issue:
I use a ESP32 (AZ delivery one) programmed with the tuto found here:
And when I test it, it works great with many blutooth devices (such as oral-b toothbrushes) but does not work with my mi-flora sensor (despite beeing located at approx 1m).
It seems that my mi-flora is only detected by the bluetooth of my Rpi 3B+ located approx 20m away in the laundry room and no more detected when I de-activate bluetooth on the Rpi.
I do not know the firmware level of this sensor (bought and updated in november last year) thus cannot confirm if it is 3.3.6… And I have only one sensor.
It is an issue for me as I am close to migrate my Pi to a better unit and will thus lose the Bluetooth… and my mi-flora if BLE proxy does not take over…
On top of it, I tried to edit the config of BLE proxy using ESP Home, but this is a little bit too much for my Rpi and I do not manage to compile… Thus I am stuck with the All in one plug & play version of the ESP Home BLE proxy.
Could you try again with the suggested firmware esp32dev-ble-datatest and unplug any other esp32 that could be in range of the non working mi floras?
Also don’t connect to them with your smartphone as it may prevent them from broadcasting.