[Feature Request] Add BTHome support to default tasmota32-bluetooth driver

[AleXSR700]

Hi everyone,
@Staars recently added BTHome support to the esp32_mi BLE driver and I was wondering if this could be added to the "normal" bluetooth driver loaded when building using tasmota32-bluetooth config?

Problem is that my ESP32 is being used as a BLE to wifi hub for TRVs and I lose the ability to use any other BLE devices when switching to the BTHome supporting driver.

Would be really cool if it could be added to the normal BLE driver. No problem to custom build of course as long as the driver continues to work with all other BLE devices :)

Thank you for considering.

Alex

EDIT for reference:
#20625

[AleXSR700]

Maybe as an additional pro:
pvvx support will be deprecated so the current implementation of mijia support in tasmota32-bluetooth will stop working.

[AleXSR700]

Anybody here who could and would help with this?

[AleXSR700]

Just fyi because I had linked the initial PR earlier, I just read the release notes for the latest tasmota stable release and it seems Staars updated his initial BTHome implementation in #20989

Please, let me know if you need a tester for BTHome devices. I have a bunch and am happy to flash an esp32 with a test version in case you don't have any BTHome devices (or would simply like a beta tester:) ).

[AleXSR700]

Just wanted to check in and see if there is any way I can be of assistance this week? :)

[AleXSR700]

Hello barbudor,
did you by any chance have time to take a look at the BTHome implementation? :)

[AleXSR700]

Just my keep-alive hoping BTHome support will be added to the tasmota32-bluetooth firmware 🙏

[AleXSR700]

👋

[AleXSR700]

Push :)

[DJVirus1980]

What about add BTHome v2 support?

[g6094199]

will be ignored like the reqeusts before....

[Jason2866]

Not ignored. Open Source Software is not where you can make wishes and this wishes will be statisfied.
So maybe someone is someday coding this feature and adds it. The idea is open and pushing it every month will not change anything on this.

[AleXSR700]

I was just pushing because barbudor commented that he was swamped but would look into it when he had time. Since I cannot expect him to have it on his todo, it is my job to follow up :)

[Hypfer]

@AleXSR700 No, it is not "your job" to "follow up".

You were told clearly and unmistakably by a member of the project that you are to cease the spam because that's not how it works.
That barbudor user is not a member of the project. If you feel like you are obliged to ping them, go send them an email. The address is on their profile.

[AleXSR700]

I was not disagreeing nor saying that I would continue to do so. I was simply explaining why ;)

[barbudor]

Sorry @AleXSR700 I too bury down in work these time, I don't have much time for tasmota and also the BLE stuff is quite compilcated. Not even sure I would succeed.
Let asks to @btsimonh to have a look into.

[DJVirus1980]

Hello, has anything changed with the addition of the BTHome protocol?

[AleXSR700]

I just saw that all other formats will be dropped with version 6 of ATC Mi thermometer firmware. Is there anybody who wants to try ro implement BTHome with me? If not, all I can do is feed Staars' code into Claude and CoPilot and hope it will be able to implement it for me 🙈

[g6094199]

as u can see this config is way old, but since its working flawlessly there was no need to adapt.....

its was simple as that:

esphome:

name: esp32-bluetooth-proxy
friendly_name: Bluetooth Proxy
min_version: 2024.6.0
name_add_mac_suffix: true

esp32:
board: esp32dev
framework:
type: esp-idf

logger:

esp32_ble_tracker:
scan_parameters:
# We currently use the defaults to ensure Bluetooth
# can co-exist with WiFi In the future we may be able to
# enable the built-in coexistence logic in ESP-IDF
active: true

bluetooth_proxy:
active: true

button:

• platform: safe_mode
  id: button_safe_mode
  name: Safe Mode Boot

• platform: factory_reset
  id: factory_reset_btn
  name: Factory reset

Enable Home Assistant API

api:
encryption:
key: "dWw="

ota:

• platform: esphome
  password: "b8"

wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password

Enable fallback hotspot (captive portal) in case wifi connection fails

ap:
ssid: "Ble-Gw Fallback Hotspot"
password: "B"

[AleXSR700]

@g6094199:
Wait, so you are not sending the ble data to mqtt? You are just bridging between bluetooth device and HA?
If so, then ESPHome is not doing anything with the data and the format becomes irrelevant as long as HA knows it.
ESPHome is essentially nothing more than a repeater.

If that is the case, then that is a completely different use case. In my use case, the esp32 "decodes" the incoming ble data and converts it to a define syntax. The esp32 already breaks it down into devices and entities automatically. Essentially, the esp32 does what the BTHome integration in HA does for you.

@pkkrusty :
Seems like a similar problem in your case. Rather than ESPHome actually doing the decoding itself, you are doing that manually and then forwarding the reformatted information. Again, not what tasmota does.

Maybe this screenshot of the tasmota WebUI frontend clears things up:

Tasmota identifies Xiaomi Mijia TH devices automatically (without me telling it anything) and identifies the device and its entities and knows what they represent. It decodes the incoming information and makes it user readable.

That is what "support BTHome v2 format on pvvx firmware devices" means. :)

[pkkrusty]

I'm with you. I looked to tasmota to do the job at first also, since I prefer the ecosystem. But in the absence of bthomev2 support, I am using ESPHome to manually create a compatible json structure so I can ingest data into influxdb using telegraf.

[AleXSR700]

Yeah, giving up on alternatives because none currently support BTHome with Mijia devices.

Tried using Claude.ai and CoPilot to implement it into the xsns 62 driver but no luck so far.

[pkkrusty]

Maybe worth trying again with Opus 4.6...it's pretty smart.

[Jason2866]

Had a look at openmqttgateway. Since the BLE part is maintained from h2zero (the author of the NimBLE libs) it is probably not a bad choice ;-) The list of supported BLE devices is long.

[DJVirus1980]

Whith custom xsns_62_esp32_mi_ble.ino

[g6094199]

custom xsns_62_esp32_mi_ble.ino

hi,
is there a github link?

[DJVirus1980]

Now testing.

[AleXSR700]

Now testing.

Any update? Did you figure it out?

[DJVirus1980]

no, its works. link xsns_62_esp32_mi_ble.zip

[DJVirus1980]

xsns_62_esp32_mi_ble.zip
Testing in dev 15.3.0.3

[DJVirus1980]

It works 3 months. may be add to project?

[pkkrusty]

Works for me in initial testing. However I note in the driver that you only implemented a few of the sensor types. Do you plan on adding the rest or do you want me to continue?

When I say me, I mean Claude.

[AleXSR700]

Would be nice to add to official repo. If I, and by I I also mean Claude or GPT, can help, let me know. But it seems to work, so maybe open a PR?

[pkkrusty]

I should clarify, BTHome v2 protocol defines about 25 different sensor types, including binary sensors. In my case the BTH-01 temp/humidity sensor can upload a different firmware from pvvx which has support for binary sensor on an exposed pad, which in my case I put on a reed switch so it can act as a door sensor as well. But it doesn't show up on the tasmota GUI even though it is transmitting the hex header. Home Assistant picks it up correctly via bluetooth.

[arendst]

Pls try latest dev branch which includes BTHome support for some sensors and possibly your binary sensor too.

[arendst]

I've merged the changes from the .zip file in latest dev xsns_62_esp32_mi_ble.ino.

I hoped to be able to decode my IoTorero WS01 BTHome V2 button but all I see is:

15:12:48.030 M32: BTHome: encrypted packets not yet supported (41E47BC3077EAAB05C922A3A4D2141273C160000806CBE96)
15:12:48.055 M32: BTHome: encrypted packets not yet supported (41E47BC3077EAAB05C922A3A4D2141273C160000806CBE96)
15:12:48.111 M32: BTHome: encrypted packets not yet supported (41E47BC3077EAAB05C922A3A4D2141273C160000806CBE96)

Pity.

[arendst]

And now with decryption:

18:08:48.131 M32: BTHome: MAC `0C3D5E54C3E9` encrypted packet (41EE37ABF296FA3E5574285CAC6A3D47C81800006DC52D24)
18:08:48.134 M32: E9C3545E3D0C: Searching key
18:08:48.145 M32: E9C3545E3D0C: Decryption key found
18:08:48.146 M32: E9C3545E3D0C: Decrypted 635F97030063C3580100638BAEAC00
18:08:48.148 M32: BTHome: decrypted packet (41635F97030063C3580100638BAEAC00)
18:08:48.161 M32: 0C3D5E54C3E9: Payload decrypted
18:08:48.162 M32: 0C3D5E54C3E9: Frame 0, last 0
18:08:48.163 M32: BTHome: unknown obj 0x63 - stopping
18:08:48.174 M32: BTHome: 0C3D5E54C3E9 slot 0

TBC...

[arendst]

BTHome button decoding works too:

12:50:15.249 MQT: stat/atomlite2/SENSOR = {"Time":"2026-08-04T12:50:15","BTHome54c3e9":{"mac":"0c3d5e54c3e9","Btn":1,"Battery":72,"RSSI":-57}}

[DJVirus1980]

Hi, It works.