Page 1 of 1
smp_br_connect_callback is called on unexpected transport 2
Posted: Fri Jan 06, 2017 1:59 am
by TESTTHISONE
Hello,
the following warning occurs when gatt client connects with gatt server.
Gatt Client:
>> BT: smp_br_connect_callback is called on unexpected transport 2
>> BT: esp_gattc_cb, event = 2
>> BT: ESP_GATTC_OPEN_EVT
>> BT: ESP_GATTC_OPEN_EVT conn_id 4, if 4, status 0
Gatt Server:
BT: smp_br_connect_callback is called on unexpected transport 2
BT: SERVICE_START_EVT, conn_id 4, gatt_if 4, is_conn 1
what does this warning - smp_br_connect_callback is called on unexpected transport 2 - mean?
regards,
Re: smp_br_connect_callback is called on unexpected transport 2
Posted: Fri Jan 06, 2017 3:49 am
by WiFive
https://github.com/espressif/esp-idf/bl ... l2c.c#L237
Well it looks like the connection is BLE and the callback is expecting a regular BR or EDR connection.
Re: smp_br_connect_callback is called on unexpected transport 2
Posted: Fri Jan 06, 2017 8:13 am
by TESTTHISONE
thanks!
do you also know where this warning comes from?
>> BT: bta_to_btc_uuid UUID len is invalid 0
regards,
Re: smp_br_connect_callback is called on unexpected transport 2
Posted: Fri Mar 17, 2017 3:34 pm
by madscientist_42
I'm sure that nobody's figured out what the issue was that caused this message- because while the message is in smp_br_connect_callback, under BLE, you're not even supposed to be calling this function. gatt_init() sets the hook in the exec table for the L2CAP functionality to a GAP/GATT specific form that is
different and what's intended (There's a reason I keep saying BlueDroid's craptastic... REALLY??!?
) This means if you're seeing this in your log, your callbacks table has never been GATT initialized or if it was, the incomplete BT Classic stuff got stomped onto your table...
I've fell upon this sword and I'm trying to figure out direct cause- if it's me, I'll document it. If it's a bug, I'll report the issue and any workarounds I find.
Re: smp_br_connect_callback is called on unexpected transport 2
Posted: Fri Mar 17, 2017 3:47 pm
by madscientist_42
Well, it looks like this is getting called against the SMP path regardless of what else you might be configuring.
Looks like there MIGHT be a bug if you're in SMP mode wherein GATT services aren't available. Since I'm using PlatformIO for my IDE, I'll have to see what I need to do to turn off SMP and see if it builds "right" without the mode on.
Re: smp_br_connect_callback is called on unexpected transport 2
Posted: Tue Apr 11, 2017 11:33 pm
by jkhax0r
Did you ever figure this out?
I'm getting this message on connect:
Code: Select all
BT: smp_br_connect_callback is called on unexpected transport 2
and this on every notify event
Code: Select all
BT: bta_to_btc_uuid UUID len is invalid 0
I'm having lots of issues with BT and wonder if this is somehow related or if these error messages are just expected. I'm connecting to a 3rd party device.
Thanks in advance!
Re: smp_br_connect_callback is called on unexpected transport 2
Posted: Mon May 22, 2017 1:04 am
by geertroumen
I'm having exactly the same problems, both the
"BT: smp_br_connect_callback is called on unexpected transport 2" -> On a LEGO wedo2.0 device
and
"BT: bta_to_btc_uuid UUID len is invalid 0" When trying to add a notifier to it.
I'm using Arduino as the IDE and using modified code from
https://developer.ibm.com/recipes/tutor ... nd-watson/
(Connecting works perfectly fine, but adding notifications is still not working)