-
Notifications
You must be signed in to change notification settings - Fork 185
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.
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
Support for Bluetooth Mesh #445
Comments
Checking a random selection of operating systems it does not appear that either Android or Windows support Bluetooth Mesh, which means that it will be difficult for browsers to implement support for it if it were specified by Web Bluetooth. Example code for these operating systems utilize the GATT portions of the Bluetooth Mesh specification (provisioning and proxy nodes) and these services should be accessible with Web Bluetooth without changes to the specification. Leaving this issue open to track future support for Bluetooth Mesh's other transport layers as support begins to appear in operating systems. |
Sounds good, thank you, reillyeon. |
Web Bluetooth does not currently support broadcasting advertisements. If you're asking how to do that with the Android SDK that is off-topic for this issue tracker. |
Advertising aside, I think the rest could be implemented on top of Web Bluetooth I believe @bluetooth-mdw was looking into what was missing from the current implementation. |
This is a video of a Web Bluetooth application controlling a Bluetooth mesh network via a proxy node: https://youtu.be/1rxgY1EnmJw?t=1293 I had to cut some corners though, due to limitations regarding Web Bluetooth and the degree to which it is currently implemented in browsers. There are two interpretations of the question regarding "support for Bluetooth mesh" because there are two ways this could be approached.
There are several issues (that I know of):
In this interpretation / approach, developers would be able to work directly with mesh models, messages, states and so on, per the Bluetooth mesh specifications and without using a mesh proxy node. This would require implementation of APIs that use what is known as the "advertising bearer". This involves unconnectable advertising packets being used as the bearer for mesh messages and scanning being used to receive them. Web Bluetooth could provide Bluetooth mesh APIs built on this bearer (and the other layers of the Bluetooth mesh stack which sit on top of the bearer layer) but only if the native platform has support for everything required. This would not be a small undertaking. It would be significantly easier if the underlying platform has comprehensive Bluetooth mesh APIs, of course. I would recommend focusing on (1). Proxy nodes were created for this purpose anyway and on the face of it, the list of issues is not too big. Caveat: the above represents my personal opinion and does not form an 'official' position of the Bluetooth SIG, nor is it necessarily 100% complete. The mesh specifications should be consulted for details. An educational resource which explains and gives hands-on experience of proxy nodes and the proxy protocol, using Web Bluetooth is available from here: https://www.bluetooth.com/bluetooth-resources/?types=study-guide&categories=&tags=mesh&keyword= |
Hi, I have a small question related to what @bluetooth-mdw said.
Does it means that GATT must be implemented on a mesh proxy node to be able to read messages from a mesh network ? I have been trying to read Mesh Proxy Data Out on several applications (nrfConnect, the web bluetooth server from the mesh proxy study kit), and I did not managed to read it. Thanks for your response. |
Hi, I think we're going off topic here. The best place for questions about the Bluetooth specifications themselves, is at bluetooth.com (navigate to Contact Us and you'll find Ask a Question in there). But.... yes. However, Mesh Proxy Data Out does not support READ. It supports NOTIFY only. See 7.2.3 of the Mesh Profile specification. Cheers Martin |
Sorry, for going off topic, I'll go on bluetooth.com. And thanks for your response. |
No problem! I'm probably guilty of having coaxed things in that direction :-) |
It would be great if it does or there's a plan on it.
The text was updated successfully, but these errors were encountered: