
If you expand the size of the firmware, you may run into other issues when you load it. What you want to do is probably going to require a pretty thorough understanding of the ARM architecture and how it interfaces with the BlueCore chip (which is described in the LEGO Bluetooth Developer Kit). You can edit them using any C editor, including the Kickstart version of the IAR Embedded Workbench for ARM (which won't allow you to build the firmware, but will allow you to compile it and at least check for compile errors). Update: I switched to the “regular” release (did not uninstall the dev version, just stopped it and installed the regular one alongside it then started it) and the compile works now.Most of the files you want to play with are \AT91SAM9DS256\Source\*_bt.*.

I’m thinking perhaps it was simply overlooked? Ideally the dev version would have support for this, too. I would uninstall the ESPHome addon and reinstall a non-dev version but don’t want to screw up my ESPHome configuration. However, I am running “ESPHome (dev)”, which (since it is the dev version) should have all the latest stuff… right? The change log linked from the add-on page even mentions it. I HAVE updated to HA 2022.9.1, it is a regular ESP32 device, etc, and I’ve included esp32_ble_tracker: as well (with no other configuration for either). I am trying to set this up (I want also to see if it works for pairing Matter devices, btw) but I’m getting the following when I try to compile anything in ESPHome: Component not found: bluetooth_proxy.Īnd the editor also complains about the bluetooth_proxy: in the configuration file. Any suggestions on how to add a tracker sensor for an iBeacon UUID? 07:57:10.426 DEBUG (MainThread) esp32-bluetooth-proxy-3b6e28: 4A:E2:3F:70:87:83 AdvertisementData(manufacturer_data=) connectable: False match: set() rssi: -98 The scan shows devices nearby and RSSI info, but not UUID.

So I watched the video, turned on debug logger on and yes, data from the Bluetooth Proxy starts getting into home-assistant.log.
