Yep, that worked, HA found it & created a new device:
And I see the volt sensor entity too:
So (to my untrained eye) all things are pointing to the ESP32 not sending those messages to the broker. We know the BM2 itself is working, as I can see the values in the android app, so it has to be the ESP32 module
Iirc from the docs, it says something about sensors might not send data if they’re paired. So I’ve made sure to remove the device from the android app, however when I flash the module I do see this on my Mac:
I wonder if it really means paired?
I also installed a BLE scanner on my phone, & saw it thinks it’s an iBeacon device:
I’m not sure if it means anything specifically, however I see the iBeacon Tracker integration in HA, but there are no devices or entities associated with it, & nothing to configure
Lastly (for now) when I look in the home/OpenMQTTGateway_Garage/SYStoMQTT topic, I see this about the module:
{
"uptime":2144,
"version":"v1.5.1",
"discovery":true,
"env":"esp32-olimex-gtw-ble-wifi",
"freemem":102236,
"mqttport":"1883",
"mqttsecure":false,
"tempc":57.22222,
"freestack":1760,
"rssi":-46,
"SSID":"DF_MESH",
"BSSID":"D8:32:14:D7:23:A2",
"ip":"192.168.0.180",
"mac":"24:4C:AB:05:26:80",
"lowpowermode":-1,
"interval":55555,
"intervalcnct":2280000,
"scnct":31,
"modules":[
"BT"
]
}
Is "lowpowermode":-1
correct?
Maybe the message format is different to what’s being checked for? Would it help if I pushed the messages to a public Mosquitto broker so you can see everything first hand?