Things you should know about Bluetooth mesh

RE: Things you should know about Bluetooth mesh

bhargav i — Tue, 23 Oct 2018 11:59:02 GMT

Informative one.

RE: Things you should know about Bluetooth mesh

Eirik Midttun — Wed, 30 Aug 2017 09:52:42 GMT

@Mark: Yes, I definitely think Bluetooth mesh is worth the consideration. Scalability is largely a question about the use case. For what you describe it is the number of sensors, and how often they report that will decide how well the mesh scales.

If the nodes are far apart you could also limit the number of relaying nodes to avoid congesting the advertising channels. It should also be possible to add routing algorithms in a addition to the stack, and it should still be interoperable.

RE: Things you should know about Bluetooth mesh

Mark Nowell — Wed, 30 Aug 2017 09:44:18 GMT

Eirik thanks for this post - clarified some aspects of BT mesh for me. I also came across a recent post of yours promoting BT mesh for applications based around industrial lighting but nowhere can I find any suggestions as to how this is going to scale. If we're looking at applications with 1000+ sensors plus similar numbers of powered lighting/relay nodes across large industrial sites is BT mesh worth looking at or is it going to grind to a halt at a few hundred nodes or less perhaps?

RE: Things you should know about Bluetooth mesh

Marius Heil — Fri, 11 Aug 2017 07:22:07 GMT

With a little optimization you'll get it down to 16kb, if you want to get it even lower it's going to get hard. Not impossible probably, but very hard.

RE: Things you should know about Bluetooth mesh

Tabish — Thu, 10 Aug 2017 16:26:27 GMT

@Calin M I think FruityMesh also needs at least 16kb RAM. github.com/.../Developers

RE: Things you should know about Bluetooth mesh

Calin M — Thu, 10 Aug 2017 16:15:40 GMT

Could a fruitymesh application fit on a 51822/QFAA chip, or will it require a 51822 / QFAC?

RE: Things you should know about Bluetooth mesh

Marius Heil — Wed, 09 Aug 2017 07:26:44 GMT

Take a look at the Wiki on GitHub. Mesh Connections are built using a spanning tree and no flooding is used. Because of that, it is possible to do on batteries for a long time. There's standard AES128 security but there are not standard profiles such as lighting and stuff, these are more or less custom at the time, but it is planned to add some of the profiles that match the standard defined ones.

RE: Things you should know about Bluetooth mesh

Tabish — Tue, 08 Aug 2017 21:43:43 GMT

@Marius Heil Curious how your FruityMesh implementation compares to the recent NRF5 mesh sdk?

RE: Things you should know about Bluetooth mesh

Marius Heil — Tue, 08 Aug 2017 11:23:49 GMT

May I use this very nice Blogpost to promote my FruityMesh implementation again? :-) If anybode needs a mesh network that can fully work on batteries, my implementation is available on GitHub: github.com/.../fruitymesh

It relies on connections rather than on flooding. It's still actively developed, but the process of publishing to GitHub sometimes gets stuck, sorry for that. There's some big updates waiting in my private repository that need to be cleaned up.

RE: Things you should know about Bluetooth mesh

Tabish — Tue, 08 Aug 2017 06:19:02 GMT

Very good write up, thanks!