You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=Nonecreated_at=<Date2015-09-10.13:51:56.964>labels= ['type-feature', 'library']
title='no support for Bluetooth LE in socket'updated_at=<Date2015-09-10.13:51:56.964>user='https://bugs.python.org/TimTisdall'
When Bluetooth LE support was added to Bluez they expanded sockaddr_l2 (the struct for making L2CAP connections) to include a l2_bdaddr_type. Since the existing code initializes the struct with 0's the type is set to regular Bluetooth (BDADDR_BREDR). An additional optional argument is needed to allow it to also be set to BDADDR_LE_PUBLIC or BDADDR_LE_RANDOM which indicate it's a LE connection to be made.
There hasn't been any comments in 7 years and no patch was provided so closing. If there is any interest a new issue targeting main branch should be created.
Activity
TimTisdall commentedon Sep 10, 2015
When Bluetooth LE support was added to Bluez they expanded sockaddr_l2 (the struct for making L2CAP connections) to include a l2_bdaddr_type. Since the existing code initializes the struct with 0's the type is set to regular Bluetooth (BDADDR_BREDR). An additional optional argument is needed to allow it to also be set to BDADDR_LE_PUBLIC or BDADDR_LE_RANDOM which indicate it's a LE connection to be made.
kumaraditya303 commentedon Sep 4, 2022
There hasn't been any comments in 7 years and no patch was provided so closing. If there is any interest a new issue targeting main branch should be created.