ESP32 with Internal BLE for iBeacon #11601

oliver-koch · 2021-04-05T22:10:39Z

oliver-koch
Apr 5, 2021

Dear all,

i try to set up my ESP32 (Lolin32 v1.0.0) with Tasmota (development 9.3.1.2 - self compiled) to detect my iBeacon devices.
I pulled the latest version from Github and compiled it using VSCode.
Firmware is build without errors, and i can upload FW successfully to my ESP32.

I have added the folliwing content to my user_config_override.h as described here:

#ifdef ESP32
  #define USE_IBEACON_ESP32    // Use internal ESP32 Bluetooth module
#endif // ESP32

When ESP starts, it connects to Wifi, reports even iBeacon devices, but then crashes with panic message:

[00:07:21]ets Jun  8 2016 00:22:57
[00:07:21]
[00:07:21]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[00:07:21]configsip: 0, SPIWP:0xee
[00:07:21]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[00:07:21]mode:DOUT, clock div:2
[00:07:21]load:0x3fff0018,len:4
[00:07:21]load:0x3fff001c,len:1044
[00:07:21]load:0x40078000,len:10124
[00:07:21]load:0x40080400,len:5828
[00:07:21]entry 0x400806a8
[00:07:22]
[00:07:22]00:00:00.041 UFS: FlashFS mounted with 48 kB free
[00:07:22]00:00:00.107 CFG: Loaded from File, Count 3
[00:07:22]00:00:00.122 QPC: Count 2
[00:07:22]00:00:00.131 Project tasmota To_be_changed Version 9.3.1.2(tasmota)-1_0_6(2021-04-05T23:51:30)
[00:07:22]00:00:00.159 BRY: Berry initialized, RAM used=4785
[00:07:22]00:00:00.184 BRY: No 'autoexec.be' file
[00:07:23]00:00:00.005 WIF: Connecting to AP1 [SSID] Channel 1 BSSId 38:10:D5:29:EC:E2 in mode 11n as CHANGE_ME-8188-8188...
[00:07:28]00:00:05.710 WIF: Connected
[00:07:29]00:00:06.054 HTP: Web server active on CHANGE_ME-8188-8188 with IP address 10.0.0.162
[00:07:29]00:00:06.058 RSL: INFO1 = {"Module":"ESP32-DevKit","Version":"9.3.1.2(tasmota)","FallbackTopic":"cmnd/DVES_16DFFC_fb/","GroupTopic":"WIN/OG/Default/tasmotas/cmnd/"}
[00:07:29]00:00:06.067 RSL: INFO2 = {"WebServerMode":"Admin","Hostname":"CHANGE_ME-8188-8188","IPAddress":"10.0.0.162"}
[00:07:29]00:00:06.077 RSL: INFO3 = {"RestartReason":"Vbat power on reset"}
[00:07:29]00:00:06.144 RSL: SENSOR = {"Time":"1970-01-01T00:00:06","IBEACON":{"UID":"ED16166DD4DF47BCBFD4B396D27CD89A","MAJOR":"7800","MINOR":"0200","MAC":"16ED1502004C","RSSI":-823,"STATE":"ON"}}
[00:07:29]00:00:06.155 RSL: SENSOR = {"Time":"1970-01-01T00:00:06","IBEACON":{"MAC":"66DE3A9962E7","RSSI":-96,"STATE":"ON"}}
[00:07:29]Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
[00:07:29]Core 0 register dump:
[00:07:29]PC      : 0x40120f24  PS      : 0x00060d30  A0      : 0x80120f94  A1      : 0x3ffe4f90  
[00:07:29]A2      : 0x00000000  A3      : 0x00000009  A4      : 0x00000000  A5      : 0x00000000  
[00:07:29]A6      : 0x00000006  A7      : 0xb7220220  A8      : 0xc0000000  A9      : 0x13377f29  
[00:07:29]A10     : 0x000000a7  A11     : 0x00000001  A12     : 0x00000007  A13     : 0x3f412af4  
[00:07:29]A14     : 0x13377f29  A15     : 0x00000000  SAR     : 0x00000018  EXCCAUSE: 0x0000001c  
[00:07:29]EXCVADDR: 0x13377f29  LBEG    : 0x4000c428  LEND    : 0x4000c42d  LCOUNT  : 0x00000000  
[00:07:29]
[00:07:29]ELF file SHA256: 0000000000000000
[00:07:29]
[00:07:29]Backtrace: 0x40120f24:0x3ffe4f90 0x40120f91:0x3ffe4fb0 0x400f92a9:0x3ffe4fd0 0x40121a01:0x3ffe5160 0x40124b36:0x3ffe51a0 0x40129b11:0x3ffe5210 0x401298ab:0x3ffe5250 0x40129e10:0x3ffe5270 0x40128185:0x3ffe5290 0x4012f832:0x3ffe52b0 0x401212bf:0x3ffe52d0 0x400938b6:0x3ffe52f0
[00:07:29]
[00:07:29]Rebooting...

Has anyone an idea what I am doing wrong?
Thank you very much for any assistance.

Kind Regards
Oliver

Answered by btsimonh

Apr 6, 2021

@oliver-koch - use the command 'iBeacon 1' to enable the iBeacon functionality. It's disabled by default so that we could have it compiled in, but many people don't want it's messages. You may also like to use 'BLEAlias MAC=Name' to name your beacons, and 'iBeaconOnlyAliased 1' - then you would only get iBeacon messages for devices which you Actually want to hear....
These commands can be put into an 'autoexec.bat' uploaded to the filesystem.
The discord chat on BLE is a good place to get help on the internal BLE....
Please report on your usage :). We've not heard many stories about iBeacon usage yet....

View full answer

barbudor · 2021-04-06T05:33:00Z

barbudor
Apr 6, 2021

You should also define USE_BLE_ESP32
You may want also to try the latest pre-built tasmota32-bluetooth.bin from http://ota.tasmota.com/tasmota32

0 replies

oliver-koch · 2021-04-06T07:22:45Z

oliver-koch
Apr 6, 2021
Author

With adding the mentioned #define USE_BLE_ESP32 to my user_config_override.h ESP32 does display iBeacon as BLEDevices, but iBeacon info (UUID, Major, Minor) is not displayed. The iBeacon (UUID, Major, Minor) information is what i want to use via MQTT.

// Enable internal iBeacon for ESP32
#ifdef ESP32
  #define USE_BLE_ESP32
  #define USE_IBEACON_ESP32    // Use internal ESP32 Bluetooth module
#endif // ESP32

If i use latest precompiled tasmota32-bluetooth build the beacons are detected as BLE devices,
but iBeacon info (UUID; Major, Minor) is also not displayed.

[09:11:03]08:11:03.130 MQT: tele/tasmota_16DFFC/INFO1 = {"Module":"ESP32-DevKit","Version":"9.3.1.2(bluetooth)","FallbackTopic":"cmnd/DVES_16DFFC_fb/","GroupTopic":"cmnd/tasmotas/"}
[09:11:03]08:11:03.139 MQT: tele/tasmota_16DFFC/INFO2 = {"WebServerMode":"Admin","Hostname":"tasmota_16DFFC-8188","IPAddress":"10.0.0.162"}
[09:11:03]08:11:03.150 MQT: tele/tasmota_16DFFC/INFO3 = {"RestartReason":"Software reset CPU"}
[09:11:08]08:11:08.770 MQT: tele/tasmota_16DFFC/STATE = {"Time":"2021-04-06T08:11:08","Uptime":"0T00:00:14","UptimeSec":14,"Heap":125,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":264,"MqttCount":1,"Wifi":{"AP":1,"SSId":"5ecf0ada.node.prism.nsa.gov","BSSId":"38:10:D5:29:EC:E2","Channel":1,"RSSI":100,"Signal":-41,"LinkCount":1,"Downtime":"0T00:00:07"}}
[09:11:08]08:11:08.798 MQT: tele/tasmota_16DFFC/BLE = {"Time":"2021-04-06T08:11:08","BLEDevices":{"total":2,"AC233F66AF89":{"i":0,"r":-78},"AC233F692814":{"i":1,"r":-63}}}
[09:11:08]08:11:08.810 MQT: tele/tasmota_16DFFC/BLE = {"Time":"2021-04-06T08:11:08","BLE":{"scans":0,"adverts":31,"devices":2,"resets":0}}

0 replies

Jason2866 · 2021-04-06T08:16:16Z

Jason2866
Apr 6, 2021
Collaborator

I think you enabled the previous (old) iBeacon implementation. This variant is not active maintained anymore. Since there are a lot of changes in the now used Arduino core and the actual NimBLE version it is no surprise it is not working anymore. Since issues in older Arduino Core the old iBeacon never worked reliable over a longer period (days).

0 replies

oliver-koch · 2021-04-06T08:41:23Z

oliver-koch
Apr 6, 2021
Author

@Jason2866: With "old iBeacon implementation" you mean USE_IBEACON as described in Tasmota Docs?

Detecting iBeacon's with ESP32 internal BLE via Tasmota would be a pretty cool feature.

So i need to wait until someone is going to get it work again. Unfortunately I am not able to do this. :)

1 reply

Jason2866 Apr 6, 2021
Collaborator

No the one you mentioned is only for a extern module. Not for the included BT of the ESP32.
The old one for ESP32 is enabled with

#ifdef ESP32
  #define USE_IBEACON_ESP32    // Use internal ESP32 Bluetooth module
#endif // ESP32

as you described in your first post

Jason2866 · 2021-04-06T10:25:07Z

Jason2866
Apr 6, 2021
Collaborator

According to this https://btsimonh.github.io/docs/ble/Bluetooth-Esp32/
there should be the possibility to enable major / minor output,
@btsimonh can you help?

0 replies

btsimonh · 2021-04-06T10:43:15Z

btsimonh
Apr 6, 2021

@oliver-koch - use the command 'iBeacon 1' to enable the iBeacon functionality. It's disabled by default so that we could have it compiled in, but many people don't want it's messages. You may also like to use 'BLEAlias MAC=Name' to name your beacons, and 'iBeaconOnlyAliased 1' - then you would only get iBeacon messages for devices which you Actually want to hear....
These commands can be put into an 'autoexec.bat' uploaded to the filesystem.
The discord chat on BLE is a good place to get help on the internal BLE....
Please report on your usage :). We've not heard many stories about iBeacon usage yet....

0 replies

oliver-koch · 2021-04-06T12:32:14Z

oliver-koch
Apr 6, 2021
Author

Thank you very much @Jason2866 and @btsimonh!
This is really really cool.

Got it work when adding #define USE_BLE_ESP32to my user_config_override.h and enter iBeacon 1 on the Tasmota Console.

[14:19:27]13:19:28.049 MQT: WIN/OG/Default/CHANGE_ME-8188/tele/SENSOR = {"Time":"2021-04-06T13:19:28","IBEACON":{"UID":"ED16166DD4DF47BCBFD4B396D27CD89A","MAJOR":"7800","MINOR":"0100","MAC":"AC233F692814","RSSI":-62,"STATE":"ON","PERSEC":0}}
[14:19:29]13:19:30.729 MQT: WIN/OG/Default/CHANGE_ME-8188/tele/SENSOR = {"Time":"2021-04-06T13:19:30","IBEACON":{"MAC":"AC233F58A4D0","RSSI":-64,"STATE":"ON","PERSEC":0}}
[14:19:32]13:19:33.401 MQT: WIN/OG/Default/CHANGE_ME-8188/tele/SENSOR = {"Time":"2021-04-06T13:19:33","IBEACON":{"MAC":"AC233F66AF89","RSSI":-58,"STATE":"ON","PERSEC":0}}

@btsimonh: As you can see in the output only one of my iBeacons UID is reported in Tasmota, but i have ~15 different.

My iBeacon configuration is the following: I have ~15 iBeacon Devices using all the same UID, but different Major and Minor values.

UUID is ED16166DD4DF47BCBFD4B396D27CD89A wich represents my Home location
Major is representing floors: 1.floor,2.floor,garden,balcony,...
Minor is representing rooms: kichen, livingroom, masterbedroom,bath,...
When i swich of the current listed iBeacon, Tasmota reports another availible UUID,Major,Minor combination, but still only one.

I am not sure, if i use the concept of UUID,Major,Minor in a correct way, but i would be cool, that i can see all my iBeacons in Tasmota using same UID and displaying different Major and Minor IDs. Maybe this can be adapted?
Or do i use the UUID,Major,Minor IDs in a wrong way?

12 replies

btsimonh Apr 6, 2021

I'm considering a display overhaul for the MI sensors at the moment - so it fits with that; I have little time at the moment, but keep an eye over the coming weeks for a PR on the main TAS repo.

oliver-koch Apr 6, 2021
Author

For me its fine like this. Thanks to all for your great and fast support! I am really impressed. :)
Display on Webinterface is not on my focus. More a nice to have. MQTT messages are absolutly perfect for me.

joba-1 Apr 6, 2021

Thanks barbudor, for the source. So I would have to ask apple - they also don't elaborate why they need 2 more fields to make a unique id even more unique: nobody forces you to use the same uuid for different beacons - no idea why apple suggests that.
Oliver, I understand your usecase, thought about something like that myself. But it would also work if every beacon had a unique uuid and no additional major/minor. That's why I asked. But no problem. I was just curious.

barbudor Apr 6, 2021

Think about what is the intention of iBeacon and why Apple designed that
When you have the App of a retail shop in your iDevice, it registers itself to iOS based on the UUID which define the app/shop
An given App will register only 1 UUID. 1 UUID for Tesco, 1 UUID for Walmart, 1 UUID for HEMA, 1 UUID for XXXX or YYYY (pu the name of your favorite retail chain).
So when the iDevice enters the vincinity of an iBeacon for this retailler network, iOS wakes the App, providing the optional details of which exact shop, floor, section with Major and Minor, so it can provide you with local info, discounts, etc...

Any other usage is a derivative of Apple's original goal & application

pmknowles May 12, 2021

@btsimonh the 'more details' link from the Tasmota EQ-3 goes to a 404 page. You may want to update the link.

Jason2866 · 2021-04-06T18:17:42Z

Jason2866
Apr 6, 2021
Collaborator

Thx barbudor for detailed infos about. With this knowledge imho a PR to change this in Tasmota would be a good thing. The changes are minimal what i have seen in the special build from btsimonh.
@btsimonh can you provide a PR?

13 replies

btsimonh Apr 8, 2021

I have put in a pull request to (un)swap the bytes. @oliver-koch - you will need to change your interpretation....

oliver-koch Apr 8, 2021
Author

Hex is ok for me. :)

btsimonh Apr 9, 2021

@oliver-koch - can you test
https://github.com/btsimonh/Tasmota/tree/ibeaconUUIDMAJORMINOR
this recognises true iBeacons by UUID+MAJOR+MINOR, and if the mac changes, changes the MAC rather than creating a new beacon and letting the old timeout. (reason: we have had a report of use of phones sending iBeacon messages, and their macs change every 5 minutes. So the change we made to make it only by MAC for you messed up their use case! - however, it may be a sue case that you would like too....).
Also adds :major:minor to the web ui.

Hopefully this can be a final PR..... on your approval. let me know.

oliver-koch Apr 9, 2021
Author

I have exact the same usecase :). I have different hardware beacons sending same UUID+MAJ+MIN.
i will comile it this afternoon and report my test results.

oliver-koch Apr 9, 2021
Author

@btsimonh: i have checked it and it works as expected. MAC toggles now between two MAC's:
(UID+MAJOR+MINOR are equal)

11:32:55.386 MQT: WIN/OG/Default/SCANNER-8188/tele/SENSOR = {"Time":"2021-04-09T11:32:55","IBEACON":{"UID":"ED16166DD4DF47BCBFD4B396D27CD89A","MAJOR":"0078","MINOR":"0001","MAC":"AC233F692814","RSSI":-48,"STATE":"ON","PERSEC":0}}
11:33:05.383 MQT: WIN/OG/Default/SCANNER-8188/tele/SENSOR = {"Time":"2021-04-09T11:33:05","IBEACON":{"UID":"ED16166DD4DF47BCBFD4B396D27CD89A","MAJOR":"0078","MINOR":"0001","MAC":"AC233F692817","RSSI":-50,"STATE":"ON","PERSEC":0}}
11:33:16.292 MQT: WIN/OG/Default/SCANNER-8188/tele/SENSOR = {"Time":"2021-04-09T11:33:16","IBEACON":{"UID":"ED16166DD4DF47BCBFD4B396D27CD89A","MAJOR":"0078","MINOR":"0001","MAC":"AC233F692814","RSSI":-48,"STATE":"ON","PERSEC":1}}
11:33:26.151 MQT: WIN/OG/Default/SCANNER-8188/tele/SENSOR = {"Time":"2021-04-09T11:33:26","IBEACON":{"UID":"ED16166DD4DF47BCBFD4B396D27CD89A","MAJOR":"0078","MINOR":"0001","MAC":"AC233F692817","RSSI":-57,"STATE":"ON","PERSEC":1}}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ESP32 with Internal BLE for iBeacon #11601

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 8 comments 26 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

ESP32 with Internal BLE for iBeacon #11601

Replies: 8 comments · 26 replies

oliver-koch Apr 6, 2021 Author

Jason2866 Apr 6, 2021 Collaborator

oliver-koch Apr 6, 2021 Author

Jason2866 Apr 6, 2021 Collaborator

Jason2866 Apr 6, 2021 Collaborator

oliver-koch Apr 6, 2021 Author

oliver-koch Apr 6, 2021 Author

Jason2866 Apr 6, 2021 Collaborator

oliver-koch Apr 8, 2021 Author

oliver-koch Apr 9, 2021 Author

oliver-koch Apr 9, 2021 Author

Replies: 8 comments 26 replies

oliver-koch
Apr 6, 2021
Author

Jason2866
Apr 6, 2021
Collaborator

oliver-koch
Apr 6, 2021
Author

Jason2866 Apr 6, 2021
Collaborator

Jason2866
Apr 6, 2021
Collaborator

oliver-koch
Apr 6, 2021
Author

oliver-koch Apr 6, 2021
Author

Jason2866
Apr 6, 2021
Collaborator

oliver-koch Apr 8, 2021
Author

oliver-koch Apr 9, 2021
Author

oliver-koch Apr 9, 2021
Author