Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bluetooth LE support for the Gateway #69

Open
icraggs opened this issue Jul 16, 2017 · 10 comments
Open

Bluetooth LE support for the Gateway #69

icraggs opened this issue Jul 16, 2017 · 10 comments
Assignees
@ty4tw
Labels
enhancement

Comments

@icraggs
Copy link
Collaborator

icraggs commented Jul 16, 2017

To allow this scenario https://blog.benjamin-cabe.com/2017/01/16/using-mqtt-sn-over-ble-with-the-bbc-microbit to work better.
@icraggs icraggs self-assigned this Jul 16, 2017
@MichalFoksa
Copy link

MichalFoksa commented Aug 20, 2017 •
edited
Loading

Hi Ian,

It requires having somewhere MQTT-SN Forwarder encapsulation (#27) on each end, right?

I believe it should be added into the gateway.

Michal

@icraggs
Copy link
Collaborator Author

icraggs commented Sep 13, 2017

Hi Michal,

I don't know if it requires encapsulation. I must admit to not understanding when encapsulation is needed - I probably haven't thought about it enough.

@ty4tw
Copy link
Contributor

ty4tw commented Sep 14, 2017

I'm going to study about BLE UARTService from Nordic.
I think the Gateway can directory connect to the BLE networks. so, there's no chance to use encapsulation message. the purpose of the encapsulation message is forwarding the message to the gateway which can not directly connect to the client's network.

@ty4tw
Copy link
Contributor

ty4tw commented Sep 17, 2017 •
edited
Loading

Latest version of Bluez library was released this September. http://www.bluez.org/download/
It supports the BLE meshnetwork https://www.bluetooth.com/specifications/mesh-specifications.

As a gateway, it is better to adopt this Mesh network without forcing the UARTService which is lacking in function. I thought of a power technique to wait for L2CAP sockets with select () in order to realize 1: N communication, but I think that adopting Mesh network will solve this problem. The micro: bit will support BLE Mesh network either, I will decide to go on a royal road. Any help would be appreciated.

@ty4tw
Copy link
Contributor

ty4tw commented Jul 27, 2018

I implemented a Forwarder encapsulation message (#27).

ty4tw added a commit that referenced this issue Jul 27, 2018
@ty4tw
Add The forwarder Encapsulation mesage #27 #69
aa22a4d 
Signed-off-by: tomoaki <[email protected]>
ty4tw added a commit that referenced this issue Jul 28, 2018
@ty4tw
Add The forwarder Encapsulation mesage #27 #69
d7390c5 
Signed-off-by: tomoaki <[email protected]>
ty4tw added a commit that referenced this issue Jul 28, 2018
@ty4tw
Add The forwarder Encapsulation mesage #27 #69
9940aad 
Signed-off-by: tomoaki <[email protected]>
@arekmd
Copy link

arekmd commented Jul 30, 2018

I added Serial port Forwarder encapsulated frames support in my fork here: arekmd@5f9c82f

It was implemented as new SensorNetwork module.

I was not aware, that Tomoaki is working on similar enhancement. Anyway, I decided to not create 'pull request' because those changes are not compatible.

ty4tw added a commit that referenced this issue Jul 30, 2018
@ty4tw
QoS-1 PUBLISH is available #34
4932d2d 
BugFix of #69

Signed-off-by: tomoaki <[email protected]>
@ty4tw
Copy link
Contributor

ty4tw commented Jul 30, 2018

Hi Arek,

Thank you for your information.
I thought the gateway should support Forwarders and Clients simultaneously.
So, I decided to add Forwarder class to the gateway. and also ClientProxy class for QoS-1. #34
More than one Forwarder can connect to the gateway.
I have implemented all the functions specified in the specification, I think.

@ty4tw ty4tw assigned ty4tw and unassigned icraggs May 23, 2021
@ty4tw
Copy link
Contributor

ty4tw commented May 26, 2021

The BLE implementation I'm coding requires bluetooth / bluetooth.h and libbluetooth.
It can run only on Linux.

@ty4tw
Copy link
Contributor

ty4tw commented Jun 2, 2021 •
edited
Loading

RFCOMM of Bluetooth classic is implemented. I don't know how to connect a BLE RFCOMM.
Can anyone help me?
I will push it as a future branch.

ty4tw added a commit that referenced this issue Jun 2, 2021
@ty4tw
Add Bluetooth classic　as a sensor network #69, #195, #90
44afcef 
I think the architecture of the ble sensor network, which does not use
threads per socket, can be applied to DTLS.

Known bug:
Occasionally a timeout error occurs when connecting to RFCOMM.
BLE is not supported yet. I need help to do it.



Signed-off-by: tomoaki <[email protected]>
ty4tw added a commit that referenced this issue Jun 2, 2021
@ty4tw
Add Bluetooth classic　as a sensor network #69, #195, #90
55128f0 
I think the architecture of the ble sensor network, which does not use
threads per socket, can be applied to DTLS.

Known bug:
Occasionally a timeout error occurs when connecting to RFCOMM.
BLE is not supported yet. I need help to do it.


Signed-off-by: tomoaki <[email protected]>
@ty4tw
Copy link
Contributor

ty4tw commented Jun 3, 2021

micro:bits uses Nordic uart service. So, GW needs a GATT NUS running on a linux.
Any information is appreciated.

@ty4tw ty4tw removed the help wanted label Jun 9, 2021
ty4tw added a commit that referenced this issue Jun 11, 2021
@ty4tw
Bugfix check network status after initialization.
83c30d6 
future branch is merged into develop. #69
Change Tab to 4 spaces

Signed-off-by: tomoaki <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ty4tw ty4tw

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@arekmd @ty4tw @MichalFoksa @icraggs